Hour audit: 2026-09-10T21
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-10T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T21:00:00.000033402+00:00 · last event 2026-09-10T21:59:59.999995528+00:00
VOLUME 106,914,057 rows · 1,142,857,853 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 105,929,200 · f: 105,607,270 · h: 105,503,060 · e: 105,489,752 · c: 97,057,012 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 204,468 (0.19%) · f: 651,863 (0.61%) · h: 13,400,073 (12.53%) · e: 1,161,682 (1.09%) · c: 91,495,971 (85.58%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 106,914,057 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e4c0f12e94ba5fe1e8ade954f0301aa4136f094d6bf44590e1af639dac27b1c8
the corpus checksum ledger names this file with the same digest
joined 106,917,804 to merged 106,914,057, minus 3,747 (minus 0.0035%)
boundary drops 3,747 · 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-10T22:57:52Z as cefgh
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,442,226 118,943,160 0-39 9c2b943748f69efe18bf47bdf8ab178ae60615a87cb8c5d0f47dc383af46edf2 book 1,215,427 79,380,365 40-44 ee42167206bd64081ec26b2c53ee5d04f4f3eb090fb46afc6f4352c27d79745a last_trade_price 48,928 2,825,634 45-45 82c1fcd97eab35ab616f527818713a870ddb061dbede018a1de9a8f2535389f7 market_resolved 1,515 203,797 46-46 028c770c893c7d7ee5031232157723b4b5d85d42755742aef4800d467cb352ab new_market 4,705 447,919 47-47 150325957a2815dc41aba0f4e7d4f3aee88d4f5c82d2d969bac7ebbfaed1dc4b price_change 95,199,072 939,756,918 48-411 f61445d0b4cc29f3bfb3b9a74f06edfb24ad4adc9c9b2bda279ebf2f7887b7e2 tick_size_change 2,184 81,344 412-412 677a3ae1f052ffe3d7e7b3296bbb0c640c60a7b3d2fe163e0b03d64c70a8a218 EVENT MIX count share price_change 95,199,072 89.04% best_bid_ask 10,442,226 9.77% book 1,215,427 1.14% last_trade_price 48,928 0.05% new_market 4,705 <0.01% tick_size_change 2,184 <0.01% market_resolved 1,515 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,442,476 10,442,226 250 1,256 FULL book 1,215,437 1,215,427 10 200,419 FULL last_trade_price 48,929 48,928 1 196 FULL market_resolved 1,515 1,515 0 11 FULL new_market 4,705 4,705 0 0 FULL price_change 95,202,558 95,199,072 3,486 1,084 FULL tick_size_change 2,184 2,184 0 49 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,557,290 9,012,878 5ms 13ms 152ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,437,231 109,413 44ms 60ms 234ms 8.9s 0 transport_latency_assumed best_bid_ask f 10,439,133 58,015 45ms 64ms 234ms 9.3s 0 transport_latency_assumed best_bid_ask g 10,433,973 2,862 83ms 154ms 552ms 42.2s 0 transport_latency_assumed best_bid_ask h 10,440,953 1,259,058 17ms 31ms 246ms 39.5s 0 transport_latency_assumed book c 982,610 963,005 18.0min 1.2d 30.1d 104.0d 0 book_staleness book e 155,725 22,492 127ms 5.5h 8.9d 104.0d 0 book_staleness book f 178,725 30,883 313ms 7.9h 16.2d 104.0d 0 book_staleness book g 511,897 170,963 7.2min 20.5h 26.5d 104.0d 0 book_staleness book h 138,729 28,084 31ms 1.5h 3.5d 104.0d 0 book_staleness last_trade_price c 42,951 40,354 11ms 51ms 242ms 5.0s 0 transport_latency_assumed last_trade_price e 48,350 533 66ms 442ms 3.0s 9.0s 0 transport_latency_assumed last_trade_price f 48,602 434 68ms 411ms 4.1s 9.4s 0 transport_latency_assumed last_trade_price g 48,062 32 119ms 1.4s 15.2s 42.2s 0 transport_latency_assumed last_trade_price h 48,778 7,575 24ms 110ms 568ms 8.0s 0 transport_latency_assumed market_resolved c 1,337 1,284 6ms 4.5min 11.5min 11.5min 0 transport_latency_assumed market_resolved e 1,243 8 47ms 282ms 53.0s 56.0s 0 transport_latency_assumed market_resolved f 1,243 7 48ms 271ms 601ms 1.1min 0 transport_latency_assumed market_resolved g 1,243 2 93ms 413ms 1.1s 2.3min 0 transport_latency_assumed market_resolved h 1,243 214 19ms 119ms 52.0s 54.1s 0 transport_latency_assumed new_market c 3,104 1,868 72ms 1.1min 5.4min 2.2d 0 transport_latency_assumed new_market e 2,965 498 122ms 51.2s 1.5min 2.2d 0 transport_latency_assumed new_market f 2,965 513 135ms 52.5s 1.8min 2.2d 0 transport_latency_assumed new_market g 2,965 373 239ms 52.7s 1.5min 2.2d 0 transport_latency_assumed new_market h 2,965 1,453 79ms 52.3s 1.5min 2.2d 0 transport_latency_assumed price_change c 86,467,732 81,474,675 5ms 14ms 168ms 3.5s 0 transport_latency_assumed price_change e 94,842,054 1,028,726 45ms 73ms 430ms 8.9s 0 transport_latency_assumed price_change f 94,934,418 562,007 46ms 77ms 411ms 9.3s 0 transport_latency_assumed price_change g 94,928,880 30,236 85ms 183ms 1.5s 42.4s 0 transport_latency_assumed price_change h 94,868,208 12,103,428 17ms 35ms 272ms 39.9s 0 transport_latency_assumed tick_size_change c 1,988 1,907 5ms 9ms 103ms 140ms 0 transport_latency_assumed tick_size_change e 2,184 12 44ms 51ms 123ms 1.2s 0 transport_latency_assumed tick_size_change f 2,184 4 45ms 65ms 370ms 438ms 0 transport_latency_assumed tick_size_change g 2,180 not meas. 80ms 127ms 390ms 529ms 0 transport_latency_assumed tick_size_change h 2,184 261 17ms 21ms 87ms 633ms 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-10/21/2026-09-10T21.parquet sha256sum 2026-09-10T21.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.