Hour audit: 2026-09-06T16
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-06T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T16:00:00.061455301+00:00 · last event 2026-09-06T16:59:59.999992692+00:00
VOLUME 125,290,008 rows · 1,369,675,280 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 122,236,842 · e: 122,123,138 · f: 118,294,590 · g: 117,967,727 · c: 86,751,895 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 38,229,279 (30.51%) · e: 3,444,755 (2.75%) · f: 984,468 (0.79%) · g: 239,562 (0.19%) · c: 82,391,944 (65.76%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ae3cef90335797c82f447b14e2874f49c9a29e9e14da4b94e1d4be0560219cd1
the corpus checksum ledger names this file with the same digest
joined 125,292,808 to merged 125,290,008, minus 2,800 (minus 0.0022%)
boundary drops 2,800 · 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-06T23:58:40Z 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 11,814,488 136,049,932 0-45 a23de581a79791cdbd5054044d90245cc643d38e0d313d059edc8efe22fcbf4a book 3,007,692 107,435,248 46-57 7392bc75ec8794060c08b6f6e8c3940049b7b068dc597c0574b2616b9f38d24e last_trade_price 71,802 4,167,978 58-58 2c27d94f3fe30636696bf08b62748a92cd4d5375fca0f4da3428b12c1b2d5434 market_resolved 4,062 417,453 59-59 99e5fa1dc838b7096a7476c13741ba3fbb9266e14ad15d8e1007bd75c7c8a1e0 new_market 5,663 488,564 60-60 252f912ffbadd9803ca323512cadb011ab9719e033e1c6f89e2f492ec9e2aa7a price_change 110,377,809 1,119,374,881 61-482 e48ab169c3a338710045951423e1fcaf5551caeaced58cd99c0c642056c66d8c tick_size_change 8,492 313,175 483-483 cbcb17cbe589efa7959f916bebb004f48a373fbb7985407f7817a001feb9d0ee EVENT MIX count share price_change 110,377,809 88.10% best_bid_ask 11,814,488 9.43% book 3,007,692 2.40% last_trade_price 71,802 0.06% tick_size_change 8,492 <0.01% new_market 5,663 <0.01% market_resolved 4,062 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,814,707 11,814,488 219 5,077 FULL book 3,007,738 3,007,692 46 171,294 FULL last_trade_price 71,805 71,802 3 1,013 FULL market_resolved 4,062 4,062 0 309 FULL new_market 5,663 5,663 0 5 FULL price_change 110,380,341 110,377,809 2,532 2,899 FULL tick_size_change 8,492 8,492 0 601 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,084,801 7,715,027 5ms 13ms 173ms 11.6s 0 transport_latency_assumed best_bid_ask e 11,811,425 323,019 39ms 56ms 360ms 15.9s 0 transport_latency_assumed best_bid_ask f 11,375,586 76,454 47ms 64ms 317ms 8.0s 0 transport_latency_assumed best_bid_ask g 11,339,982 6,074 81ms 123ms 691ms 20.6s 0 transport_latency_assumed best_bid_ask h 11,812,368 3,693,914 19ms 37ms 501ms 53.4s 0 transport_latency_assumed book c 2,860,029 2,743,640 4.7min 23.2h 35.2d 99.8d 0 book_staleness book e 152,196 7,312 42ms 212ms 6.2s 16.0s 0 book_staleness book f 498,836 51,539 59.8s 16.2h 29.3d 99.7d 0 book_staleness book g 502,856 158,469 1.0min 16.3h 29.3d 99.8d 0 book_staleness book h 152,408 46,732 23ms 98ms 4.5s 81.1d 0 book_staleness last_trade_price c 49,429 46,918 11ms 46ms 359ms 5.0s 0 transport_latency_assumed last_trade_price e 71,773 1,783 45ms 154ms 4.6s 16.0s 0 transport_latency_assumed last_trade_price f 69,309 509 53ms 153ms 1.3s 8.0s 0 transport_latency_assumed last_trade_price g 68,711 54 94ms 283ms 3.5s 20.7s 0 transport_latency_assumed last_trade_price h 71,766 22,538 25ms 79ms 804ms 52.6s 0 transport_latency_assumed market_resolved c 3,139 2,954 29ms 15.3min 19.5min 19.8min 0 transport_latency_assumed market_resolved e 2,407 114 41ms 188ms 1.0min 1.1min 0 transport_latency_assumed market_resolved f 2,468 27 49ms 292ms 5.6min 5.8min 0 transport_latency_assumed market_resolved g 2,424 143 88ms 389ms 5.0min 5.2min 0 transport_latency_assumed market_resolved h 2,407 824 20ms 65ms 394ms 4.9s 0 transport_latency_assumed new_market c 4,194 2,339 319ms 17.3min 44.4min 7.8h 0 transport_latency_assumed new_market e 2,996 843 242ms 13.9min 15.1min 22.2min 0 transport_latency_assumed new_market f 3,231 778 256ms 17.9min 18.6min 1.0h 0 transport_latency_assumed new_market g 3,002 436 389ms 3.9min 18.0min 2.7h 0 transport_latency_assumed new_market h 2,996 1,267 187ms 14.1min 15.2min 1.6h 0 transport_latency_assumed price_change c 75,744,147 71,875,097 5ms 17ms 208ms 11.6s 0 transport_latency_assumed price_change e 110,073,865 3,111,483 39ms 75ms 418ms 16.1s 0 transport_latency_assumed price_change f 106,336,920 855,119 47ms 78ms 375ms 8.1s 0 transport_latency_assumed price_change g 106,042,460 74,382 82ms 151ms 816ms 20.8s 0 transport_latency_assumed price_change h 110,186,405 34,461,728 19ms 44ms 522ms 53.4s 0 transport_latency_assumed tick_size_change c 6,156 5,969 5ms 10ms 94ms 385ms 0 transport_latency_assumed tick_size_change e 8,476 201 39ms 53ms 422ms 865ms 0 transport_latency_assumed tick_size_change f 8,240 42 47ms 55ms 226ms 532ms 0 transport_latency_assumed tick_size_change g 8,292 4 80ms 100ms 641ms 3.1s 0 transport_latency_assumed tick_size_change h 8,492 2,276 18ms 35ms 416ms 14.6s 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-06/16/2026-09-06T16.parquet sha256sum 2026-09-06T16.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.