Hour audit: 2026-09-04T00
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-04T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T00:00:00.000062834+00:00 · last event 2026-09-04T00:59:59.999873562+00:00
VOLUME 108,190,697 rows · 1,037,108,019 bytes (989.06 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 108,151,076 · h: 77,838,030 · e: 64,665,285 · b: 61,763,264 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 23,239,755 (21.48%) · h: 20,278,357 (18.74%) · e: 64,664,331 (59.77%) · b: 8,254 (0.01%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,190,697 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 58e9a53521b3495f1d2505f4298767bb730694dd3b4824452918ac934deef7d8
the corpus checksum ledger names this file with the same digest
joined 108,192,066 to merged 108,190,697, minus 1,369 (minus 0.0013%)
boundary drops 1,369 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-04T01:51:33Z as bceh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 10,261,301 114,054,715 0-39 b99f67588596a9a4294d31dc3c8467c5cf23c1104bfbfe335534c2cade1d4e04 book 176,285 16,948,047 40-40 313cedb67eb46105db3fa5cc938fbe536c096c9e85a811d4a2f3fe1875cb128a last_trade_price 63,824 3,549,301 41-41 9551719c3821c9b5cd966bdc209d6fe80a75c0f06551b09dff6859228d013c0e market_resolved 532 88,426 42-42 85a49d6645308f1088add767b403fcaf3d225ed5dce2577fddbcc32deae2ad15 new_market 1,639 176,736 43-43 f4966aa46975e36b5b6a2533ab479964419e6e94495b6bc18727f1a13a0b4fde price_change 97,684,252 900,954,825 44-416 6d85db045965d940ad4a83b3544d3d6fe161af55a8b1f58bed113b2e9a3230a9 tick_size_change 2,864 102,596 417-417 2596c3a5a606905e7d480ac3ac7757e62d0e13a119492ad22ade06c5aeb3c2e8 EVENT MIX count share price_change 97,684,252 90.29% best_bid_ask 10,261,301 9.48% book 176,285 0.16% last_trade_price 63,824 0.06% tick_size_change 2,864 <0.01% new_market 1,639 <0.01% market_resolved 532 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,261,406 10,261,301 105 260 FULL book 176,287 176,285 2 16,088 FULL last_trade_price 63,824 63,824 0 0 FULL market_resolved 532 532 0 1 FULL new_market 1,639 1,639 0 0 FULL price_change 97,685,514 97,684,252 1,262 111,004 FULL tick_size_change 2,864 2,864 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,245,855 112 52ms 87ms 752ms 27.2s 0 transport_latency_assumed best_bid_ask c 10,260,393 1,151 7ms 11ms 160ms 3.8s 0 transport_latency_assumed best_bid_ask e 10,243,317 10,243,253 41ms 107ms 1.1s 25.5s 0 transport_latency_assumed best_bid_ask h 10,259,754 16,785 18ms 27ms 260ms 39.5s 0 transport_latency_assumed book b 132,288 7,345 127ms 6.8s 4.3h 78.6d 0 book_staleness book c 159,408 27,202 10ms 2.1min 4.4d 97.1d 0 book_staleness book e 130,817 130,817 108ms 5.9s 1.9h 6.7d 0 book_staleness book h 134,853 10,921 30ms 510ms 47.6s 89.4d 0 book_staleness last_trade_price b 60,125 5 97ms 3.3s 15.4s 27.3s 0 transport_latency_assumed last_trade_price c 63,788 16 13ms 48ms 328ms 4.9s 0 transport_latency_assumed last_trade_price e 59,905 59,905 86ms 3.6s 15.1s 25.6s 0 transport_latency_assumed last_trade_price h 63,784 3,898 29ms 425ms 2.4s 7.4s 0 transport_latency_assumed market_resolved b 532 not meas. 54ms 445ms 772ms 975ms 0 transport_latency_assumed market_resolved c 532 not meas. 7ms 17ms 114ms 1.1s 0 transport_latency_assumed market_resolved e 531 531 41ms 369ms 834ms 920ms 0 transport_latency_assumed market_resolved h 532 1 18ms 141ms 339ms 702ms 0 transport_latency_assumed new_market b 1,170 84 309ms 14.6s 23.7s 1.1min 0 transport_latency_assumed new_market c 1,170 125 63ms 12.2s 26.6s 1.2min 0 transport_latency_assumed new_market e 1,170 1,170 213ms 14.8s 22.4s 1.1min 0 transport_latency_assumed new_market h 1,170 260 144ms 15.6s 34.8s 1.0min 0 transport_latency_assumed price_change b 51,320,430 708 53ms 190ms 6.6s 27.2s 0 transport_latency_assumed price_change c 97,662,921 23,211,261 7ms 12ms 186ms 3.8s 0 transport_latency_assumed price_change e 54,226,681 54,225,791 41ms 220ms 6.4s 25.6s 0 transport_latency_assumed price_change h 67,375,073 20,246,492 18ms 36ms 485ms 39.5s 0 transport_latency_assumed tick_size_change b 2,864 not meas. 52ms 72ms 442ms 919ms 0 transport_latency_assumed tick_size_change c 2,864 not meas. 7ms 12ms 207ms 669ms 0 transport_latency_assumed tick_size_change e 2,864 2,864 41ms 70ms 301ms 1.6s 0 transport_latency_assumed tick_size_change h 2,864 not meas. 18ms 32ms 171ms 2.7s 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-04/00/2026-09-04T00.parquet sha256sum 2026-09-04T00.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.