Hour audit: 2026-09-17T00
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-17T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T00:00:00.000165914+00:00 · last event 2026-09-17T00:59:59.999988925+00:00
VOLUME 129,859,954 rows · 1,374,026,189 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 128,551,090 · e: 128,549,106 · f: 123,839,750 · g: 123,448,101 · c: 117,742,275 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 16,569,575 (12.76%) · e: 1,102,510 (0.85%) · f: 308,969 (0.24%) · g: 49,540 (0.04%) · c: 111,829,360 (86.12%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 129,859,954 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 719ce55c3a2c6f5d838db68a5651ab878f227a0923c9d3b7e8fbf01d5fedcd64
the corpus checksum ledger names this file with the same digest
joined 129,868,511 to merged 129,859,954, minus 8,557 (minus 0.0066%)
boundary drops 8,557 · 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-17T02:02:10Z 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 15,024,622 169,417,878 0-57 6ddaddf86f60fa8e43abc74a11bebe641236a596373f37846bb5d86ff10fde9d book 1,282,487 74,906,497 58-62 55bd2138aa7261beeaecc5434aeee8222aeb0a4b57385f3741c377a229312e6d last_trade_price 51,133 2,916,307 63-63 a6c6e6da80fb37983b3d9e6f794657ac80731fe8bc448e0bc293b8442d5c4137 market_resolved 581 79,724 64-64 89522abd5282907f5a18cce721eed38cf69c8d187b7fd0dd6494e6db34bce88c new_market 687 75,149 65-65 fa269595c1b36a6f13dcf0d94b03d42782f20f784685696935a4f261426e09a9 price_change 113,497,664 1,125,053,392 66-498 48b6ae3ec03e8add11357d027c50db0e25de4e6e3dfd43e0a04267e53906e5e6 tick_size_change 2,780 102,789 499-499 d8dad8da0969f79608538d9d79678bf24f8c3b1260d243c268920ccefe7c8727 EVENT MIX count share price_change 113,497,664 87.40% best_bid_ask 15,024,622 11.57% book 1,282,487 0.99% last_trade_price 51,133 0.04% tick_size_change 2,780 <0.01% new_market 687 <0.01% market_resolved 581 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,024,894 15,024,622 272 1,567 FULL book 1,289,025 1,282,487 6,538 176,132 FULL last_trade_price 51,134 51,133 1 202 FULL market_resolved 581 581 0 0 FULL new_market 687 687 0 10 FULL price_change 113,499,410 113,497,664 1,746 408 FULL tick_size_change 2,780 2,780 0 66 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,618,534 12,991,501 5ms 11ms 74ms 3.8s 0 transport_latency_assumed best_bid_ask e 15,022,633 124,798 40ms 50ms 163ms 4.5s 0 transport_latency_assumed best_bid_ask f 14,433,590 25,065 46ms 56ms 153ms 5.3s 0 transport_latency_assumed best_bid_ask g 14,399,100 1,899 80ms 98ms 251ms 20.0s 0 transport_latency_assumed best_bid_ask h 15,022,106 1,881,359 17ms 26ms 88ms 8.7s 0 transport_latency_assumed book c 1,164,954 1,150,336 4.0min 2.4d 38.4d 110.1d 0 book_staleness book e 124,058 14,511 44ms 1.5min 7.7d 110.1d 0 book_staleness book f 475,410 68,447 1.7min 13.9h 35.2d 110.1d 0 book_staleness book g 479,140 27,658 1.7min 14.9h 35.4d 110.1d 0 book_staleness book h 112,476 21,535 21ms 81ms 33.6min 91.6d 0 book_staleness last_trade_price c 45,418 42,343 10ms 47ms 210ms 4.9s 0 transport_latency_assumed last_trade_price e 51,001 563 50ms 167ms 1.3s 4.9s 0 transport_latency_assumed last_trade_price f 48,827 181 56ms 161ms 2.1s 4.9s 0 transport_latency_assumed last_trade_price g 48,499 36 94ms 286ms 4.2s 20.1s 0 transport_latency_assumed last_trade_price h 50,940 8,010 23ms 66ms 272ms 6.6s 0 transport_latency_assumed market_resolved c 545 528 6ms 5.3min 9.8min 10.0min 0 transport_latency_assumed market_resolved e 479 1 110ms 227ms 514ms 759ms 0 transport_latency_assumed market_resolved f 479 3 116ms 260ms 3.5min 4.4min 0 transport_latency_assumed market_resolved g 491 not meas. 202ms 434ms 5.5min 5.5min 0 transport_latency_assumed market_resolved h 479 49 33ms 69ms 193ms 4.9s 0 transport_latency_assumed new_market c 515 346 52ms 1.0min 6.0min 6.0min 0 transport_latency_assumed new_market e 464 77 127ms 12.4s 19.1s 1.3min 0 transport_latency_assumed new_market f 464 63 157ms 14.7s 1.0min 3.8min 0 transport_latency_assumed new_market g 464 45 206ms 12.6s 57.9s 40.1min 0 transport_latency_assumed new_market h 464 156 60ms 344ms 22.4s 54.7s 0 transport_latency_assumed price_change c 102,909,777 97,641,910 5ms 13ms 88ms 4.6s 0 transport_latency_assumed price_change e 113,347,691 962,536 40ms 57ms 257ms 6.6s 0 transport_latency_assumed price_change f 108,878,312 215,210 46ms 63ms 296ms 6.1s 0 transport_latency_assumed price_change g 108,517,743 19,902 80ms 104ms 542ms 20.1s 0 transport_latency_assumed price_change h 113,361,845 14,658,106 18ms 29ms 112ms 8.7s 0 transport_latency_assumed tick_size_change c 2,532 2,396 5ms 9ms 54ms 258ms 0 transport_latency_assumed tick_size_change e 2,780 24 40ms 46ms 114ms 196ms 0 transport_latency_assumed tick_size_change f 2,668 not meas. 46ms 65ms 196ms 277ms 0 transport_latency_assumed tick_size_change g 2,664 not meas. 79ms 100ms 450ms 584ms 0 transport_latency_assumed tick_size_change h 2,780 360 17ms 27ms 54ms 79ms 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-17/00/2026-09-17T00.parquet sha256sum 2026-09-17T00.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.