Hour audit: 2026-09-11T16
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-11T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T16:00:00.000057103+00:00 · last event 2026-09-11T16:59:59.999995458+00:00
VOLUME 73,157,491 rows · 830,788,594 bytes (792.30 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 71,046,046 · h: 70,991,523 · g: 65,754,266 · f: 65,726,948 · c: 50,729,653 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,677,170 (2.29%) · h: 22,746,318 (31.09%) · g: 247,224 (0.34%) · f: 625,238 (0.85%) · c: 47,861,541 (65.42%) (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 73,157,491 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b631e8b44b76044daf9a802a1f7c2dc07f2967d0bab7de707883dae1fd187861
the corpus checksum ledger names this file with the same digest
joined 73,159,732 to merged 73,157,491, minus 2,241 (minus 0.0031%)
boundary drops 2,241 · 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-11T17:54:56Z 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 an incident recorded by the venue intersects this hour: Trading degraded for forty-one minutes, 2026-09-11T16:22Z to 2026-09-11T17:02ZThe 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 6,983,940 84,556,682 0-26 20a1e9a19150b9f0da88fb4244964356043076145f18132473b7707cb2d5e3be book 2,277,051 100,772,867 27-35 8d50bbf9b7f2a9c48870d79de3568de6e0efdf2f9bfb73240e5d637d17dd90c3 last_trade_price 39,602 2,326,639 36-36 6ef3f34fc7829a5f385e674379c0cbf6c471f4f61466ee394bdacf8b51232990 market_resolved 2,500 259,799 37-37 c387b6cc8a3c4d242a5fdb1956e0acf6cd2a90c1b05ddae97b42b232929adc95 new_market 2,442 235,188 38-38 d7ca4c182e03a2c2b777470c2fc3724e1fac49a3d7dbf6a667f27f1a4f985c1f price_change 63,849,300 641,701,243 39-282 c80a06f9961a4d9ab565823cf9fd271c686ee1a2d679e742ec656fb908aa7379 tick_size_change 2,656 97,047 283-283 2c2e39b0f8a4194f57d1db7c0feaf72520e151d1da3fd6f61074c2b60753dcfb EVENT MIX count share price_change 63,849,300 87.28% best_bid_ask 6,983,940 9.55% book 2,277,051 3.11% last_trade_price 39,602 0.05% tick_size_change 2,656 <0.01% market_resolved 2,500 <0.01% new_market 2,442 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,984,167 6,983,940 227 5,244 FULL book 2,277,125 2,277,051 74 197,822 FULL last_trade_price 39,602 39,602 0 550 FULL market_resolved 2,500 2,500 0 13 FULL new_market 2,442 2,442 0 0 FULL price_change 63,851,240 63,849,300 1,940 11,259 FULL tick_size_change 2,656 2,656 0 151 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 4,917,804 4,692,478 5ms 12ms 133ms 3.7s 0 transport_latency_assumed best_bid_ask e 6,982,468 138,353 40ms 48ms 176ms 7.1s 0 transport_latency_assumed best_bid_ask f 6,476,670 25,014 45ms 57ms 228ms 6.1s 0 transport_latency_assumed best_bid_ask g 6,491,363 2,836 80ms 105ms 352ms 14.4s 0 transport_latency_assumed best_bid_ask h 6,982,876 2,125,259 18ms 30ms 131ms 6.7s 0 transport_latency_assumed book c 1,867,850 1,669,431 8.1min 1.4d 30.9d 104.8d 0 book_staleness book e 196,377 71,305 33.1s 26.8min 20.1d 104.8d 0 book_staleness book f 629,429 282,532 4.9min 1.1d 29.9d 104.8d 0 book_staleness book g 637,771 191,064 5.0min 1.1d 29.9d 104.8d 0 book_staleness book h 143,440 62,719 46ms 8.4min 14.2d 104.8d 0 book_staleness last_trade_price c 28,434 27,240 10ms 40ms 192ms 5.0s 0 transport_latency_assumed last_trade_price e 39,542 735 49ms 134ms 1.1s 7.2s 0 transport_latency_assumed last_trade_price f 35,397 177 54ms 143ms 1.0s 6.1s 0 transport_latency_assumed last_trade_price g 35,563 13 95ms 259ms 3.0s 14.4s 0 transport_latency_assumed last_trade_price h 39,508 11,437 24ms 66ms 261ms 5.0s 0 transport_latency_assumed market_resolved c 2,161 2,078 7ms 12.2min 21.8min 21.9min 0 transport_latency_assumed market_resolved e 1,550 38 41ms 115ms 364ms 997ms 0 transport_latency_assumed market_resolved f 1,550 27 45ms 120ms 596ms 5.0min 0 transport_latency_assumed market_resolved g 1,541 8 81ms 234ms 3.1min 6.1min 0 transport_latency_assumed market_resolved h 1,550 349 19ms 58ms 52.2s 59.8s 0 transport_latency_assumed new_market c 1,607 945 164ms 45.7s 12.0min 16.8min 0 transport_latency_assumed new_market e 1,487 277 180ms 20.5s 47.1s 1.9min 0 transport_latency_assumed new_market f 1,487 382 197ms 26.4s 1.3min 4.9min 0 transport_latency_assumed new_market g 1,497 203 292ms 23.6s 52.0s 5.9min 0 transport_latency_assumed new_market h 1,487 635 150ms 24.6s 47.5s 3.3min 0 transport_latency_assumed price_change c 43,909,745 41,467,381 5ms 16ms 341ms 5.0s 0 transport_latency_assumed price_change e 63,821,966 1,466,452 41ms 57ms 475ms 7.1s 0 transport_latency_assumed price_change f 58,579,819 317,102 45ms 68ms 544ms 6.1s 0 transport_latency_assumed price_change g 58,583,979 53,100 81ms 128ms 818ms 14.4s 0 transport_latency_assumed price_change h 63,820,006 20,545,265 18ms 36ms 262ms 6.8s 0 transport_latency_assumed tick_size_change c 2,052 1,988 5ms 9ms 50ms 72ms 0 transport_latency_assumed tick_size_change e 2,656 10 41ms 46ms 106ms 456ms 0 transport_latency_assumed tick_size_change f 2,596 4 45ms 57ms 124ms 278ms 0 transport_latency_assumed tick_size_change g 2,552 not meas. 80ms 107ms 215ms 662ms 0 transport_latency_assumed tick_size_change h 2,656 654 18ms 27ms 66ms 312ms 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-11/16/2026-09-11T16.parquet sha256sum 2026-09-11T16.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.