Hour audit: 2026-09-09T08
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-09T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T08:00:00.000196198+00:00 · last event 2026-09-09T08:59:59.999472287+00:00
VOLUME 102,805,714 rows · 1,059,444,851 bytes (1010.37 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 102,301,200 · f: 102,246,505 · e: 102,224,904 · h: 102,191,117 · c: 98,482,960 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 46,282 (0.05%) · f: 109,967 (0.11%) · e: 365,866 (0.36%) · h: 8,901,553 (8.66%) · c: 93,382,046 (90.83%) (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 102,805,714 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 244f68eeebf0f0313934e87f371b6a6a941482596005f239008bb89c703bd2d1
the corpus checksum ledger names this file with the same digest
joined 102,809,225 to merged 102,805,714, minus 3,511 (minus 0.0034%)
boundary drops 3,511 · 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-09T09:57:24Z 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 8,952,922 99,103,623 0-34 76f673a00f96f1210888c14f0137cc1621d69f174400f5b5c8715209959b041c book 537,271 58,009,096 35-37 3b0d065b8a34951d765d8eefaf57265952c312a35edca1a27c8a725c33143712 last_trade_price 61,740 3,449,559 38-38 b4fc7aa33ccf4f6ce7f1f8c7327b2e89fbedcb9732f753d4af32c4530059c0df market_resolved 669 100,879 39-39 3657aabb5aefed4a07259add61174a00f0fce39a539919b98f2415152df36bc5 new_market 908 101,742 40-40 d0734e0a75da1fe6fbfd2bad1d58578404420221cc658343553a955861c6d889 price_change 93,249,912 897,420,395 41-396 cdc6ec5a321ad5ac46d17fa358dd162b6dbacff62f6c79bcea35c241e4c16715 tick_size_change 2,292 84,917 397-397 8aa5a6c269db115df287abb087a60fa36c6a1a94d0b0935a7d5e3012f21aa63c EVENT MIX count share price_change 93,249,912 90.70% best_bid_ask 8,952,922 8.71% book 537,271 0.52% last_trade_price 61,740 0.06% tick_size_change 2,292 <0.01% new_market 908 <0.01% market_resolved 669 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,953,140 8,952,922 218 665 FULL book 537,273 537,271 2 191,928 FULL last_trade_price 61,741 61,740 1 75 FULL market_resolved 669 669 0 49 FULL new_market 908 908 0 0 FULL price_change 93,253,202 93,249,912 3,290 991 FULL tick_size_change 2,292 2,292 0 16 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,581,600 8,155,124 5ms 10ms 91ms 4.1s 0 transport_latency_assumed best_bid_ask e 8,951,278 28,565 35ms 41ms 150ms 5.3s 0 transport_latency_assumed best_bid_ask f 8,951,362 7,674 46ms 54ms 168ms 7.2s 0 transport_latency_assumed best_bid_ask g 8,950,652 693 85ms 99ms 321ms 26.7s 0 transport_latency_assumed best_bid_ask h 8,952,418 760,866 14ms 20ms 107ms 8.4s 0 transport_latency_assumed book c 514,126 490,480 4.5min 19.1h 27.6d 102.4d 0 book_staleness book e 131,884 4,438 38ms 180ms 3.2h 83.9d 0 book_staleness book f 129,900 1,987 49ms 177ms 3.8min 83.9d 0 book_staleness book g 169,939 28,185 98ms 2.4h 3.8d 83.9d 0 book_staleness book h 128,916 12,181 18ms 63ms 2.5s 38.5d 0 book_staleness last_trade_price c 59,354 55,937 10ms 42ms 217ms 5.0s 0 transport_latency_assumed last_trade_price e 61,672 306 41ms 135ms 986ms 5.3s 0 transport_latency_assumed last_trade_price f 61,685 109 53ms 152ms 1.2s 7.2s 0 transport_latency_assumed last_trade_price g 61,677 16 97ms 310ms 3.2s 26.7s 0 transport_latency_assumed last_trade_price h 61,664 5,372 20ms 66ms 370ms 5.0s 0 transport_latency_assumed market_resolved c 617 586 5ms 55ms 6.0min 6.0min 0 transport_latency_assumed market_resolved e 621 1 36ms 192ms 502ms 1.0s 0 transport_latency_assumed market_resolved f 621 not meas. 47ms 208ms 616ms 1.1s 0 transport_latency_assumed market_resolved g 621 not meas. 86ms 380ms 856ms 1.6s 0 transport_latency_assumed market_resolved h 621 82 15ms 83ms 234ms 373ms 0 transport_latency_assumed new_market c 699 405 72ms 24.1s 5.2min 5.2min 0 transport_latency_assumed new_market e 663 64 135ms 11.0s 39.6s 1.2min 0 transport_latency_assumed new_market f 663 63 150ms 503ms 32.2s 1.1min 0 transport_latency_assumed new_market g 663 51 255ms 11.0s 33.3s 1.0min 0 transport_latency_assumed new_market h 663 325 74ms 12.7s 37.2s 1.2min 0 transport_latency_assumed price_change c 89,324,336 84,677,388 5ms 11ms 100ms 4.1s 0 transport_latency_assumed price_change e 93,076,494 332,482 36ms 46ms 204ms 5.3s 0 transport_latency_assumed price_change f 93,099,982 100,134 46ms 59ms 223ms 7.2s 0 transport_latency_assumed price_change g 93,115,356 17,334 85ms 108ms 454ms 26.7s 0 transport_latency_assumed price_change h 93,044,543 8,122,574 14ms 22ms 130ms 8.4s 0 transport_latency_assumed tick_size_change c 2,228 2,126 5ms 10ms 229ms 378ms 0 transport_latency_assumed tick_size_change e 2,292 10 36ms 44ms 120ms 381ms 0 transport_latency_assumed tick_size_change f 2,292 not meas. 47ms 61ms 160ms 227ms 0 transport_latency_assumed tick_size_change g 2,292 3 85ms 99ms 290ms 604ms 0 transport_latency_assumed tick_size_change h 2,292 153 14ms 26ms 60ms 308ms 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-09/08/2026-09-09T08.parquet sha256sum 2026-09-09T08.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.