Hour audit: 2026-09-19T11
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-19T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T11:00:00.002945042+00:00 · last event 2026-09-19T11:59:59.999996314+00:00
VOLUME 128,215,994 rows · 1,398,801,127 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 126,863,402 · e: 126,837,718 · g: 126,819,464 · f: 117,230,404 · c: 115,302,376 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 16,159,376 (12.60%) · e: 1,321,726 (1.03%) · g: 59,575 (0.05%) · f: 825,528 (0.64%) · c: 109,849,789 (85.68%) (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 128,215,994 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ec578d047fb3a2434ba373e41cca9ee694407f5b47d61b3d8736f28b69b8c88c
the corpus checksum ledger names this file with the same digest
joined 128,218,464 to merged 128,215,994, minus 2,470 (minus 0.0019%)
boundary drops 2,470 · 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-19T13:09:18Z 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,523,236 155,136,130 0-51 f21c28a66a7cec4ccb34b26b4807ae11ff1e724ba30e0adcd62a17cffd2a65d4 book 1,414,180 92,491,953 52-57 5d13ecf0c656fc2a0f3a3cdd2d582035ec6b349b654399d91b373b2add2fa4e6 last_trade_price 60,725 3,690,838 58-58 04f084ac3cf9381f41296486a448e1d56a4f5d4adab09b13ad2356b71438ebb9 market_resolved 1,316 187,367 59-59 580d020f883fa26fe75401d3ee96427d3531d389edd68477454ebf984b779ba2 new_market 855 89,963 60-60 447cb129f403cd990543daabcadf01a086d4a0f60139a743d6299956a2002a8e price_change 113,208,418 1,145,485,775 61-492 e972096a29a4389920a78d36ddc52e74d6c79227d839354581b63646afddbe07 tick_size_change 7,264 260,994 493-493 9d7e7af44a7c6ff1a3a16d537eac7841e50202c872073a0ff655461d077015f4 EVENT MIX count share price_change 113,208,418 88.30% best_bid_ask 13,523,236 10.55% book 1,414,180 1.10% last_trade_price 60,725 0.05% tick_size_change 7,264 <0.01% market_resolved 1,316 <0.01% new_market 855 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,523,532 13,523,236 296 2,092 FULL book 1,414,222 1,414,180 42 203,775 FULL last_trade_price 60,725 60,725 0 1,160 FULL market_resolved 1,316 1,316 0 109 FULL new_market 855 855 0 0 FULL price_change 113,210,522 113,208,418 2,104 459 FULL tick_size_change 7,292 7,264 28 260 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,210,435 11,674,660 5ms 11ms 103ms 6.1s 0 transport_latency_assumed best_bid_ask e 13,521,107 133,198 41ms 48ms 160ms 4.8s 0 transport_latency_assumed best_bid_ask f 12,451,410 32,098 48ms 57ms 184ms 4.5s 0 transport_latency_assumed best_bid_ask g 13,520,828 3,732 77ms 93ms 278ms 14.6s 0 transport_latency_assumed best_bid_ask h 13,521,859 1,679,548 18ms 28ms 128ms 45.8s 0 transport_latency_assumed book c 948,986 916,076 4.3min 18.6h 35.1d 112.6d 0 book_staleness book e 129,680 5,119 43ms 142ms 15.6min 94.0d 0 book_staleness book f 953,141 468,045 4.3min 17.9h 35.1d 112.6d 0 book_staleness book g 131,431 3,312 81ms 276ms 25.6min 94.0d 0 book_staleness book h 128,660 21,628 22ms 61ms 7.3min 94.0d 0 book_staleness last_trade_price c 53,082 49,595 10ms 50ms 323ms 5.0s 0 transport_latency_assumed last_trade_price e 60,426 930 48ms 122ms 707ms 5.0s 0 transport_latency_assumed last_trade_price f 55,325 359 56ms 144ms 850ms 5.0s 0 transport_latency_assumed last_trade_price g 60,404 24 87ms 201ms 1.4s 13.5s 0 transport_latency_assumed last_trade_price h 60,590 9,817 24ms 69ms 413ms 5.7s 0 transport_latency_assumed market_resolved c 1,134 1,099 5ms 13ms 3.4min 5.5min 0 transport_latency_assumed market_resolved e 1,164 22 46ms 201ms 50.9s 1.0min 0 transport_latency_assumed market_resolved f 1,190 124 58ms 5.5min 6.2min 6.4min 0 transport_latency_assumed market_resolved g 1,164 not meas. 89ms 290ms 607ms 972ms 0 transport_latency_assumed market_resolved h 1,164 71 22ms 73ms 178ms 963ms 0 transport_latency_assumed new_market c 604 354 99ms 4.4min 5.3min 5.3min 0 transport_latency_assumed new_market e 565 153 163ms 18.8s 49.0s 1.3min 0 transport_latency_assumed new_market f 568 85 164ms 20.7s 50.4s 1.8min 0 transport_latency_assumed new_market g 565 55 271ms 12.9s 43.5s 1.8min 0 transport_latency_assumed new_market h 565 208 106ms 18.1s 34.4s 1.4min 0 transport_latency_assumed price_change c 102,081,175 97,201,435 5ms 13ms 143ms 6.1s 0 transport_latency_assumed price_change e 113,117,500 1,182,204 41ms 54ms 308ms 12.2s 0 transport_latency_assumed price_change f 103,762,198 324,797 48ms 64ms 344ms 11.8s 0 transport_latency_assumed price_change g 113,097,780 52,448 78ms 100ms 484ms 18.1s 0 transport_latency_assumed price_change h 113,143,292 14,447,534 18ms 31ms 189ms 46.1s 0 transport_latency_assumed tick_size_change c 6,960 6,570 5ms 16ms 98ms 1.1s 0 transport_latency_assumed tick_size_change e 7,276 100 41ms 52ms 158ms 810ms 0 transport_latency_assumed tick_size_change f 6,572 20 48ms 69ms 242ms 1.5s 0 transport_latency_assumed tick_size_change g 7,292 4 78ms 97ms 521ms 1.6s 0 transport_latency_assumed tick_size_change h 7,272 570 19ms 36ms 248ms 2.5s 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-19/11/2026-09-19T11.parquet sha256sum 2026-09-19T11.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.