Hour audit: 2026-09-20T13
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-20T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T13:00:00.000013651+00:00 · last event 2026-09-20T13:59:59.999671656+00:00
VOLUME 132,423,295 rows · 1,482,471,222 bytes (1.38 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 130,271,620 · e: 130,242,992 · g: 125,096,019 · f: 115,991,911 · c: 107,556,003 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 28,090,953 (21.21%) · e: 2,077,697 (1.57%) · g: 214,537 (0.16%) · f: 1,611,821 (1.22%) · c: 100,428,287 (75.84%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 18bdb48d5d58a579bde1afd1c4ff1789beab423cd38d245e86afcf5cc14f6fb8
the corpus checksum ledger names this file with the same digest
joined 132,426,707 to merged 132,423,295, minus 3,412 (minus 0.0026%)
boundary drops 3,412 · 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-20T15:39:31Z 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 12,554,354 148,720,366 0-47 d759f328a1c192a080d670583a22eaa33ba8d6ef3e683daf7924aa42b754fb93 book 2,231,845 103,712,003 48-56 8767b981bd0f8e41a5e2f01b22efee04e1364f7a8e048c536f5a6042c9d214ec last_trade_price 69,539 4,068,508 57-57 12a99f00ab2cbbf3f88eab36711d7c3e38e6e096bde4053339656545bcb93e3c market_resolved 2,218 260,790 58-58 0378ed4ec4e508d02f4d0a098807089e2245d70d7dbc6d4b1d13c3c12f1e8339 new_market 1,975 178,263 59-59 ac9479b1c6f03cc133b1f7ab9dfdd2ae112eed7c32534baaa5824348e77d5d95 price_change 117,553,272 1,223,665,839 60-508 1c082fd57c1810f3b10379eb766b6098f8928313366c15d5dc5509cb9ddc75e1 tick_size_change 10,092 360,478 509-509 60b3232e83750531a334571192eef4fee296fad9038960a515742f3b3c80c457 EVENT MIX count share price_change 117,553,272 88.77% best_bid_ask 12,554,354 9.48% book 2,231,845 1.69% last_trade_price 69,539 0.05% tick_size_change 10,092 <0.01% market_resolved 2,218 <0.01% new_market 1,975 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,554,594 12,554,354 240 3,897 FULL book 2,232,995 2,231,845 1,150 168,612 FULL last_trade_price 69,541 69,539 2 707 FULL market_resolved 2,218 2,218 0 214 FULL new_market 1,975 1,975 0 2 FULL price_change 117,555,292 117,553,272 2,020 2,135 FULL tick_size_change 10,092 10,092 0 539 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,156,854 9,562,032 5ms 17ms 127ms 9.8s 0 transport_latency_assumed best_bid_ask e 12,551,090 198,220 45ms 60ms 224ms 14.6s 0 transport_latency_assumed best_bid_ask f 11,094,751 63,135 47ms 64ms 229ms 15.8s 0 transport_latency_assumed best_bid_ask g 12,013,126 3,422 80ms 105ms 448ms 27.3s 0 transport_latency_assumed best_bid_ask h 12,552,430 2,727,545 19ms 39ms 153ms 49.6s 0 transport_latency_assumed book c 1,682,884 1,162,554 5.2min 1.9d 42.6d 113.7d 0 book_staleness book e 146,839 6,026 49ms 349ms 29.8min 95.1d 0 book_staleness book f 1,163,802 871,643 4.0min 1.9d 39.8d 113.6d 0 book_staleness book g 488,119 159,648 1.6min 23.7h 36.2d 113.6d 0 book_staleness book h 143,519 31,974 23ms 80ms 2.3min 95.1d 0 book_staleness last_trade_price c 56,299 52,177 6ms 27ms 238ms 2.4s 0 transport_latency_assumed last_trade_price e 69,285 1,311 48ms 182ms 2.3s 14.5s 0 transport_latency_assumed last_trade_price f 61,683 548 50ms 210ms 3.4s 15.8s 0 transport_latency_assumed last_trade_price g 66,021 106 87ms 312ms 4.4s 27.4s 0 transport_latency_assumed last_trade_price h 69,461 15,397 20ms 60ms 342ms 9.9s 0 transport_latency_assumed market_resolved c 1,604 1,418 6ms 7.4min 8.9min 9.0min 0 transport_latency_assumed market_resolved e 1,558 37 46ms 123ms 51.1s 1.0min 0 transport_latency_assumed market_resolved f 1,628 255 49ms 3.6min 11.6min 13.1min 0 transport_latency_assumed market_resolved g 1,561 43 82ms 221ms 3.5min 4.4min 0 transport_latency_assumed market_resolved h 1,558 465 19ms 56ms 48.6s 1.0min 0 transport_latency_assumed new_market c 1,131 788 87ms 22.3s 2.5h 10.8h 0 transport_latency_assumed new_market e 1,114 177 188ms 22.4s 33.9s 7.2h 0 transport_latency_assumed new_market f 1,353 411 245ms 8.5min 2.5h 14.3h 0 transport_latency_assumed new_market g 1,114 80 292ms 21.4s 47.5s 10.7h 0 transport_latency_assumed new_market h 1,114 519 119ms 20.5s 30.1s 6.9h 0 transport_latency_assumed price_change c 95,648,527 89,641,217 5ms 20ms 153ms 9.9s 0 transport_latency_assumed price_change e 117,463,014 1,871,801 46ms 71ms 441ms 14.6s 0 transport_latency_assumed price_change f 103,659,678 675,801 48ms 76ms 471ms 15.9s 0 transport_latency_assumed price_change g 112,516,322 51,234 81ms 127ms 924ms 27.4s 0 transport_latency_assumed price_change h 117,493,450 25,313,219 19ms 44ms 204ms 49.6s 0 transport_latency_assumed tick_size_change c 8,704 8,101 5ms 17ms 238ms 1.4s 0 transport_latency_assumed tick_size_change e 10,092 125 45ms 59ms 285ms 3.4s 0 transport_latency_assumed tick_size_change f 9,016 28 47ms 65ms 300ms 843ms 0 transport_latency_assumed tick_size_change g 9,756 4 80ms 106ms 926ms 2.2s 0 transport_latency_assumed tick_size_change h 10,088 1,834 19ms 35ms 265ms 5.0s 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/13/2026-09-20T13.parquet sha256sum 2026-09-20T13.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.