Hour audit: 2026-09-20T14
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-20T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T14:00:00.000043323+00:00 · last event 2026-09-20T14:59:59.999943840+00:00
VOLUME 134,405,310 rows · 1,514,966,664 bytes (1.41 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 131,193,163 · e: 131,124,026 · g: 121,307,316 · f: 108,984,066 · c: 96,800,212 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 39,001,444 (29.02%) · e: 2,884,938 (2.15%) · g: 355,187 (0.26%) · f: 1,424,035 (1.06%) · c: 90,739,706 (67.51%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 3cf22d3bab52c670d983c0762589c40b259c9a5dcd096b451038eccf51ba95d8
the corpus checksum ledger names this file with the same digest
joined 134,415,823 to merged 134,405,310, minus 10,513 (minus 0.0078%)
boundary drops 10,513 · 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-20T16:39:21Z 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 13,124,966 155,692,168 0-50 9142f80acd373c006fa85b099ae3528c95732f6d442c4fe25dc11e8069775b6c book 3,279,880 123,041,357 51-63 725c20c8615d80cf46884540e933679b5c1627b105288267e0bd73f50990c2b2 last_trade_price 71,792 4,292,636 64-64 d1f42765aac8643ac0f5e1ed05f6796762b54629c741c97687955b3567962bfc market_resolved 3,133 351,306 65-65 69f2f0d0450aaba518f01b3d6770ab3e71f442d01ef4e233a94a60ff3a63f96e new_market 3,857 364,324 66-66 c5eda6b4642beb1ee5715408948ec3b15c41ddf13cd5d6cb122bbef02f48f85d price_change 117,908,850 1,229,229,254 67-516 8cc4a34183e5c2dbe9e4e12771487f4f67be008c8597f0c07ff0b527c0d00e65 tick_size_change 12,832 467,268 517-517 45ded2dcd39b681ad609a06fb24ae1280e34df0cd710b22f8d740d5447a7f4cf EVENT MIX count share price_change 117,908,850 87.73% best_bid_ask 13,124,966 9.77% book 3,279,880 2.44% last_trade_price 71,792 0.05% tick_size_change 12,832 <0.01% new_market 3,857 <0.01% market_resolved 3,133 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,125,209 13,124,966 243 7,176 FULL book 3,287,622 3,279,880 7,742 168,007 FULL last_trade_price 71,792 71,792 0 1,097 FULL market_resolved 3,133 3,133 0 206 FULL new_market 3,857 3,857 0 30 FULL price_change 117,911,378 117,908,850 2,528 4,167 FULL tick_size_change 12,832 12,832 0 1,175 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,362,880 8,811,622 5ms 17ms 159ms 9.1s 0 transport_latency_assumed best_bid_ask e 13,120,502 287,781 43ms 63ms 337ms 22.0s 0 transport_latency_assumed best_bid_ask f 10,797,419 89,979 47ms 71ms 370ms 23.0s 0 transport_latency_assumed best_bid_ask g 12,089,460 8,628 81ms 130ms 798ms 33.1s 0 transport_latency_assumed best_bid_ask h 13,122,344 3,926,956 19ms 41ms 349ms 55.8s 0 transport_latency_assumed book c 2,726,292 2,525,661 5.7min 2.0d 43.0d 113.7d 0 book_staleness book e 156,342 8,423 47ms 1.5s 3.4h 95.2d 0 book_staleness book f 1,166,329 461,384 3.6min 1.9d 39.8d 113.7d 0 book_staleness book g 837,705 239,660 2.9min 1.9d 39.8d 113.7d 0 book_staleness book h 151,084 44,752 24ms 132ms 8.6min 95.2d 0 book_staleness last_trade_price c 51,640 48,059 6ms 28ms 266ms 1.7s 0 transport_latency_assumed last_trade_price e 71,343 1,617 46ms 244ms 5.5s 21.6s 0 transport_latency_assumed last_trade_price f 58,867 601 50ms 253ms 5.0s 22.9s 0 transport_latency_assumed last_trade_price g 65,265 193 88ms 518ms 10.7s 30.1s 0 transport_latency_assumed last_trade_price h 71,542 21,322 20ms 68ms 589ms 41.6s 0 transport_latency_assumed market_resolved c 2,161 1,645 7ms 9.1min 12.8min 14.1min 0 transport_latency_assumed market_resolved e 2,072 42 44ms 134ms 556ms 1.0min 0 transport_latency_assumed market_resolved f 2,526 694 54ms 8.1min 13.1min 14.9min 0 transport_latency_assumed market_resolved g 2,408 143 90ms 8.2min 11.2min 12.8min 0 transport_latency_assumed market_resolved h 2,072 609 20ms 63ms 742ms 1.0min 0 transport_latency_assumed new_market c 2,506 1,573 102ms 4.6min 1.4h 15.6h 0 transport_latency_assumed new_market e 2,261 573 216ms 32.5s 2.1min 28.0min 0 transport_latency_assumed new_market f 2,374 551 236ms 2.6min 1.9h 14.7h 0 transport_latency_assumed new_market g 2,560 322 375ms 5.5min 30.5min 14.7h 0 transport_latency_assumed new_market h 2,261 838 162ms 31.8s 2.0min 7.3h 0 transport_latency_assumed price_change c 84,645,033 79,341,881 6ms 20ms 180ms 15.8s 0 transport_latency_assumed price_change e 117,758,674 2,586,334 43ms 81ms 876ms 22.0s 0 transport_latency_assumed price_change f 96,945,947 870,744 47ms 89ms 881ms 23.1s 0 transport_latency_assumed price_change g 108,297,538 106,232 81ms 176ms 2.6s 33.1s 0 transport_latency_assumed price_change h 117,831,028 35,003,659 19ms 46ms 414ms 57.0s 0 transport_latency_assumed tick_size_change c 9,700 9,265 5ms 12ms 57ms 213ms 0 transport_latency_assumed tick_size_change e 12,832 168 42ms 52ms 251ms 886ms 0 transport_latency_assumed tick_size_change f 10,604 82 47ms 60ms 296ms 990ms 0 transport_latency_assumed tick_size_change g 12,380 9 80ms 103ms 585ms 3.1s 0 transport_latency_assumed tick_size_change h 12,832 3,308 18ms 28ms 218ms 3.4s 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-20/14/2026-09-20T14.parquet sha256sum 2026-09-20T14.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.