Hour audit: 2026-09-07T18
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-07T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T18:00:00.000089393+00:00 · last event 2026-09-07T18:59:59.999992975+00:00
VOLUME 110,401,821 rows · 1,192,502,023 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 108,531,562 · f: 108,522,689 · g: 108,439,990 · e: 106,911,094 · c: 88,141,992 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 24,598,663 (22.28%) · f: 438,343 (0.40%) · g: 40,289 (0.04%) · e: 1,262,401 (1.14%) · c: 84,062,125 (76.14%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,401,821 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 947345e5051bb99e66ffaa3c89ad0dae6718712518d35a7e168c116207e6efe1
the corpus checksum ledger names this file with the same digest
joined 110,405,158 to merged 110,401,821, minus 3,337 (minus 0.0030%)
boundary drops 3,337 · 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-07T20:00:13Z 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,642,168 128,746,789 0-44 3f8d8c6964c9e27d95b8b622f2e48c4b9580b9278b230b4ad3931627acf18eca book 1,974,469 84,993,862 45-52 1fdf8acf506586c53669ab24666a2fd8d74e36201fb5ebe6c11a5cdd289a7858 last_trade_price 63,312 3,599,542 53-53 945ab737b2efbbe1f78650118ca16ea7493020ac19b092a4a55f1894ea35e2fc market_resolved 1,450 169,936 54-54 da3415c334a8a054d67a6812af396f54df61e3341a3134f1e343fa22f8f70e14 new_market 3,154 294,379 55-55 2a7f43b885392f7f73830438582d64e8a63dff482dcd26e7162352079f50142d price_change 96,710,904 973,209,597 56-424 b8cd76deca980e721feff91b62e12eb2a521ee6d5a4f71bab2f21058167066a7 tick_size_change 6,364 231,550 425-425 6dd657a11199fb93c9a515dceb9c6e0c6a9028106d6da745eef08e6a18d5fa61 EVENT MIX count share price_change 96,710,904 87.60% best_bid_ask 11,642,168 10.55% book 1,974,469 1.79% last_trade_price 63,312 0.06% tick_size_change 6,364 <0.01% new_market 3,154 <0.01% market_resolved 1,450 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,642,354 11,642,168 186 4,066 FULL book 1,974,479 1,974,469 10 178,479 FULL last_trade_price 63,313 63,312 1 474 FULL market_resolved 1,450 1,450 0 84 FULL new_market 3,154 3,154 0 6 FULL price_change 96,714,044 96,710,904 3,140 3,932 FULL tick_size_change 6,364 6,364 0 416 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,227,102 8,815,092 5ms 12ms 142ms 7.7s 0 transport_latency_assumed best_bid_ask e 11,470,496 133,261 39ms 49ms 255ms 11.5s 0 transport_latency_assumed best_bid_ask f 11,638,456 44,811 45ms 60ms 290ms 12.5s 0 transport_latency_assumed best_bid_ask g 11,635,004 3,213 84ms 119ms 620ms 29.6s 0 transport_latency_assumed best_bid_ask h 11,639,702 2,645,791 17ms 27ms 284ms 57.9s 0 transport_latency_assumed book c 1,940,164 1,929,963 31.7min 12.0h 34.4d 100.9d 0 book_staleness book e 132,457 4,796 42ms 300ms 9.1s 82.3d 0 book_staleness book f 133,355 2,123 49ms 290ms 4.8s 38.5d 0 book_staleness book g 144,181 6,635 95ms 3.8s 11.4h 100.8d 0 book_staleness book h 134,123 30,952 22ms 87ms 11.7s 82.3d 0 book_staleness last_trade_price c 50,333 47,529 10ms 47ms 298ms 5.0s 0 transport_latency_assumed last_trade_price e 62,480 831 46ms 232ms 4.2s 11.5s 0 transport_latency_assumed last_trade_price f 63,290 316 53ms 246ms 3.5s 12.5s 0 transport_latency_assumed last_trade_price g 62,647 50 100ms 414ms 6.1s 29.5s 0 transport_latency_assumed last_trade_price h 63,197 14,586 23ms 78ms 651ms 32.4s 0 transport_latency_assumed market_resolved c 1,201 1,168 7ms 8.6min 13.7min 14.2min 0 transport_latency_assumed market_resolved e 997 30 40ms 203ms 44.8s 2.3min 0 transport_latency_assumed market_resolved f 1,024 2 47ms 223ms 45.0s 1.0min 0 transport_latency_assumed market_resolved g 1,024 not meas. 88ms 378ms 1.1s 2.3s 0 transport_latency_assumed market_resolved h 1,024 250 19ms 88ms 59.0s 59.5s 0 transport_latency_assumed new_market c 2,059 1,393 83ms 4.5min 9.4min 11.4min 0 transport_latency_assumed new_market e 1,864 376 209ms 18.2s 51.2s 1.0min 0 transport_latency_assumed new_market f 1,864 314 231ms 17.4s 27.7s 1.7min 0 transport_latency_assumed new_market g 1,864 273 360ms 14.6s 24.6s 1.0min 0 transport_latency_assumed new_market h 1,864 798 138ms 16.6s 23.7s 1.6min 0 transport_latency_assumed price_change c 76,916,337 73,262,439 5ms 13ms 167ms 7.7s 0 transport_latency_assumed price_change e 95,236,552 1,123,042 40ms 59ms 380ms 11.5s 0 transport_latency_assumed price_change f 96,678,336 390,744 46ms 71ms 402ms 12.6s 0 transport_latency_assumed price_change g 96,588,906 30,118 85ms 149ms 867ms 29.7s 0 transport_latency_assumed price_change h 96,685,292 21,904,561 18ms 31ms 318ms 1.3min 0 transport_latency_assumed tick_size_change c 4,796 4,541 5ms 16ms 174ms 525ms 0 transport_latency_assumed tick_size_change e 6,248 65 39ms 51ms 252ms 545ms 0 transport_latency_assumed tick_size_change f 6,364 33 45ms 68ms 280ms 456ms 0 transport_latency_assumed tick_size_change g 6,364 not meas. 84ms 145ms 493ms 1.5s 0 transport_latency_assumed tick_size_change h 6,360 1,725 18ms 32ms 169ms 805ms 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-07/18/2026-09-07T18.parquet sha256sum 2026-09-07T18.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.