Hour audit: 2026-09-09T12
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-09T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T12:00:00.000016683+00:00 · last event 2026-09-09T12:59:59.999950351+00:00
VOLUME 111,829,957 rows · 1,196,381,514 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 110,527,970 · f: 110,491,684 · e: 110,490,146 · g: 110,480,990 · c: 96,264,217 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,599,147 (16.63%) · f: 218,687 (0.20%) · e: 1,788,731 (1.60%) · g: 35,972 (0.03%) · c: 91,187,420 (81.54%) (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 111,829,957 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f8bea22d7079e84daeff08280b67e698b16d49fb4c371ac32baeccab8f0c4b8d
the corpus checksum ledger names this file with the same digest
joined 111,833,569 to merged 111,829,957, minus 3,612 (minus 0.0032%)
boundary drops 3,612 · 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-09T13:59:04Z 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,383,327 117,486,441 0-39 fb75820e3dfd90fb06153e7de5cb7e16e874507242148a27f4d8c33bc3057831 book 1,355,499 82,135,011 40-45 384a742a4a92dc1224fb56bbaa83820949a3220aa7c3dff8e9679a57c4a2fdc6 last_trade_price 70,283 3,911,125 46-46 7573b8343221892db6309591a5f032f02d7c884f0b1d0b1e1bbc0d817b013fd2 market_resolved 1,130 152,152 47-47 73d7281efe923df7cf4237db9ef5df0c8922d9656dc84f5cf536ff55041fbf89 new_market 766 85,543 48-48 3814041d399ac8d3d901a0c3d2f15e9915cdd92d257334a7ffe9b3c21e5c05f4 price_change 100,015,320 991,204,470 49-430 3c515bfbd752901ce4cca9805b1b5efc625ecdb10cd6c889ec5ba2ad82956d00 tick_size_change 3,632 131,805 431-431 f2a9671bf5208c92860a0ee9c0e18bd37d02b0ca2eab6b5e56c8a582d489338f EVENT MIX count share price_change 100,015,320 89.44% best_bid_ask 10,383,327 9.28% book 1,355,499 1.21% last_trade_price 70,283 0.06% tick_size_change 3,632 <0.01% market_resolved 1,130 <0.01% new_market 766 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,383,522 10,383,327 195 2,774 FULL book 1,355,505 1,355,499 6 190,848 FULL last_trade_price 70,284 70,283 1 300 FULL market_resolved 1,130 1,130 0 27 FULL new_market 766 766 0 0 FULL price_change 100,018,730 100,015,320 3,410 2,870 FULL tick_size_change 3,632 3,632 0 97 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,915,696 8,467,846 5ms 11ms 94ms 3.6s 0 transport_latency_assumed best_bid_ask e 10,381,652 161,422 38ms 46ms 167ms 6.5s 0 transport_latency_assumed best_bid_ask f 10,381,524 17,301 48ms 59ms 195ms 3.0s 0 transport_latency_assumed best_bid_ask g 10,380,758 2,098 85ms 100ms 322ms 24.0s 0 transport_latency_assumed best_bid_ask h 10,381,983 1,734,660 15ms 24ms 120ms 15.2s 0 transport_latency_assumed book c 1,291,964 1,269,044 9.2min 22.6h 31.6d 102.6d 0 book_staleness book e 146,494 4,832 41ms 165ms 1.6min 83.9d 0 book_staleness book f 146,540 1,750 51ms 168ms 2.9min 102.6d 0 book_staleness book g 161,040 8,626 92ms 7.9s 1.2d 102.6d 0 book_staleness book h 236,765 71,247 37ms 4.1h 15.9d 102.6d 0 book_staleness last_trade_price c 58,967 54,920 10ms 42ms 250ms 5.0s 0 transport_latency_assumed last_trade_price e 70,182 1,274 44ms 141ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price f 70,095 187 54ms 142ms 987ms 5.0s 0 transport_latency_assumed last_trade_price g 70,086 70 96ms 265ms 4.4s 24.1s 0 transport_latency_assumed last_trade_price h 70,161 13,832 20ms 63ms 320ms 7.1s 0 transport_latency_assumed market_resolved c 961 925 6ms 4.8min 9.9min 10.7min 0 transport_latency_assumed market_resolved e 922 22 40ms 219ms 57.6s 57.7s 0 transport_latency_assumed market_resolved f 922 2 49ms 216ms 57.7s 57.7s 0 transport_latency_assumed market_resolved g 922 1 85ms 325ms 870ms 1.2s 0 transport_latency_assumed market_resolved h 922 180 16ms 118ms 57.6s 57.6s 0 transport_latency_assumed new_market c 608 363 88ms 56.4s 5.8min 6.8min 0 transport_latency_assumed new_market e 549 100 167ms 10.5s 49.4s 1.2min 0 transport_latency_assumed new_market f 549 48 163ms 677ms 19.9s 1.0min 0 transport_latency_assumed new_market g 549 17 309ms 11.5s 21.7s 1.5min 0 transport_latency_assumed new_market h 549 238 106ms 11.3s 20.0s 1.7min 0 transport_latency_assumed price_change c 85,992,777 81,391,239 5ms 12ms 114ms 4.7s 0 transport_latency_assumed price_change e 99,886,715 1,621,017 38ms 51ms 255ms 7.3s 0 transport_latency_assumed price_change f 99,888,422 199,399 48ms 65ms 278ms 4.6s 0 transport_latency_assumed price_change g 99,864,003 25,160 85ms 111ms 479ms 24.1s 0 transport_latency_assumed price_change h 99,833,958 16,778,505 15ms 28ms 158ms 15.9s 0 transport_latency_assumed tick_size_change c 3,244 3,083 5ms 11ms 50ms 1.1s 0 transport_latency_assumed tick_size_change e 3,632 64 38ms 60ms 155ms 440ms 0 transport_latency_assumed tick_size_change f 3,632 not meas. 48ms 72ms 134ms 398ms 0 transport_latency_assumed tick_size_change g 3,632 not meas. 85ms 110ms 251ms 387ms 0 transport_latency_assumed tick_size_change h 3,632 485 15ms 29ms 71ms 260ms 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/12/2026-09-09T12.parquet sha256sum 2026-09-09T12.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.