Hour audit: 2026-09-12T03
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-12T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T03:00:00.000158139+00:00 · last event 2026-09-12T03:59:59.999995712+00:00
VOLUME 121,530,462 rows · 1,295,578,773 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,421,950 · h: 118,376,881 · f: 113,743,067 · g: 113,736,118 · c: 85,269,609 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,460,258 (3.67%) · h: 33,376,014 (27.46%) · f: 536,387 (0.44%) · g: 183,591 (0.15%) · c: 82,974,212 (68.27%) (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 121,530,462 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d9b48e385862db1aa4705bedb3d84ff3496c70e14c64f01707aa0eebeb9d2559
the corpus checksum ledger names this file with the same digest
joined 121,537,772 to merged 121,530,462, minus 7,310 (minus 0.0060%)
boundary drops 7,310 · 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-12T05:36:49Z 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 10,910,939 122,521,863 0-41 0fb441784aca8494bd40738e4c9ec7826c415d65e4ae55a6650e41fa6d871908 book 3,174,378 118,012,988 42-54 8aa6efc10ef2f7eaef048928f2cf060132d9b4eb7fbd970452cc879f6d30df6a last_trade_price 44,848 2,585,383 55-55 e088c672650f8633f5d6daee7fa61ed56698c315ca3128fb666d0f1d003aae05 market_resolved 2,543 284,658 56-56 f079a5a3aedc5966028bec8d23cd61de042920e45a07ebc22b91aad7acfcb3b2 new_market 676 60,728 57-57 372df9cab913e278e4b33ddf2159f2f3620bd528b247c7c6af347c08703d7d2a price_change 107,393,222 1,050,587,617 58-467 d1424233b0af1b3d550f2b5ff972b2b9e39543225db5afb60067dd5c3fc70ec9 tick_size_change 3,856 141,799 468-468 feca6b981c9e5ba8f79b777660c6598bb1719dd0659cf6210be16465041d23a8 EVENT MIX count share price_change 107,393,222 88.37% best_bid_ask 10,910,939 8.98% book 3,174,378 2.61% last_trade_price 44,848 0.04% tick_size_change 3,856 <0.01% market_resolved 2,543 <0.01% new_market 676 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,911,224 10,910,939 285 8,955 FULL book 3,178,622 3,174,378 4,244 207,178 FULL last_trade_price 44,849 44,848 1 676 FULL market_resolved 2,543 2,543 0 220 FULL new_market 676 676 0 10 FULL price_change 107,396,002 107,393,222 2,780 6,856 FULL tick_size_change 3,856 3,856 0 272 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,678,749 7,485,179 5ms 8ms 52ms 2.2s 0 transport_latency_assumed best_bid_ask e 10,909,374 404,111 38ms 42ms 90ms 3.7s 0 transport_latency_assumed best_bid_ask f 10,453,614 31,693 45ms 50ms 121ms 3.6s 0 transport_latency_assumed best_bid_ask g 10,448,824 1,286 84ms 99ms 218ms 9.0s 0 transport_latency_assumed best_bid_ask h 10,909,888 2,988,670 18ms 31ms 92ms 36.0s 0 transport_latency_assumed book c 2,929,891 2,825,745 13.5min 9.9h 31.4d 105.2d 0 book_staleness book e 95,237 5,703 39ms 78ms 11.9min 86.7d 0 book_staleness book f 508,413 149,888 5.9min 9.7h 27.6d 105.2d 0 book_staleness book g 533,157 165,892 5.0min 9.6h 27.7d 105.2d 0 book_staleness book h 94,547 27,150 21ms 59ms 2.0min 86.6d 0 book_staleness last_trade_price c 30,581 29,334 10ms 39ms 191ms 4.9s 0 transport_latency_assumed last_trade_price e 44,697 1,780 44ms 94ms 274ms 5.0s 0 transport_latency_assumed last_trade_price f 42,882 477 52ms 102ms 264ms 5.0s 0 transport_latency_assumed last_trade_price g 42,607 19 96ms 189ms 661ms 5.1s 0 transport_latency_assumed last_trade_price h 44,696 13,238 23ms 67ms 273ms 5.3s 0 transport_latency_assumed market_resolved c 1,683 1,581 10ms 8.9min 17.9min 18.6min 0 transport_latency_assumed market_resolved e 1,710 125 40ms 117ms 248ms 600ms 0 transport_latency_assumed market_resolved f 1,694 27 48ms 125ms 267ms 2.4min 0 transport_latency_assumed market_resolved g 1,710 91 95ms 259ms 4.3min 4.7min 0 transport_latency_assumed market_resolved h 1,710 719 25ms 59ms 104ms 642ms 0 transport_latency_assumed new_market c 509 353 109ms 13.0min 28.2min 42.1min 0 transport_latency_assumed new_market e 364 64 78ms 13.0s 24.3s 10.1min 0 transport_latency_assumed new_market f 364 76 77ms 14.2s 4.3min 16.1min 0 transport_latency_assumed new_market g 376 49 131ms 13.9s 4.7min 17.8min 0 transport_latency_assumed new_market h 364 134 57ms 13.2s 20.7s 46.4min 0 transport_latency_assumed price_change c 74,625,128 72,629,008 5ms 9ms 62ms 2.2s 0 transport_latency_assumed price_change e 107,366,712 4,048,314 38ms 42ms 118ms 4.4s 0 transport_latency_assumed price_change f 102,732,544 354,214 46ms 51ms 146ms 4.3s 0 transport_latency_assumed price_change g 102,705,708 16,254 84ms 100ms 253ms 9.9s 0 transport_latency_assumed price_change h 107,321,820 30,345,432 18ms 33ms 108ms 37.4s 0 transport_latency_assumed tick_size_change c 3,068 3,012 5ms 7ms 63ms 267ms 0 transport_latency_assumed tick_size_change e 3,856 161 38ms 42ms 111ms 250ms 0 transport_latency_assumed tick_size_change f 3,556 12 45ms 49ms 102ms 331ms 0 transport_latency_assumed tick_size_change g 3,736 not meas. 85ms 112ms 581ms 963ms 0 transport_latency_assumed tick_size_change h 3,856 671 18ms 37ms 116ms 246ms 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-12/03/2026-09-12T03.parquet sha256sum 2026-09-12T03.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.