Hour audit: 2026-09-09T11
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-09T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T11:00:00.000067210+00:00 · last event 2026-09-09T11:59:59.999956451+00:00
VOLUME 111,115,459 rows · 1,179,807,018 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 109,815,203 · g: 109,810,927 · e: 109,806,715 · h: 109,752,842 · c: 97,231,401 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 160,628 (0.14%) · g: 27,168 (0.02%) · e: 926,561 (0.83%) · h: 18,065,221 (16.26%) · c: 91,935,881 (82.74%) (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 111,115,459 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 de7e3427c803da92bb4656a7717250da969776deb2de848588d9030d05bd6a8e
the corpus checksum ledger names this file with the same digest
joined 111,121,420 to merged 111,115,459, minus 5,961 (minus 0.0054%)
boundary drops 5,961 · 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:00:28Z 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 9,695,715 109,999,733 0-36 b066b118e7c7234b4be0dc8dd6f92f16e2747901610d364c5e180244f114c676 book 1,296,618 77,829,296 37-41 b94902fe27e3162d3e5b2e6ec494aebacb2ccf6591b4de4fccdffd7c777b5796 last_trade_price 61,487 3,489,981 42-42 41ff51e7d9379afcb906e483a4981a900cd0778863e8c93022011515d80902ab market_resolved 1,132 161,014 43-43 4b4bb1c07ea064b896ae6087e191eabe0f4da18fa2560831fe484561338f1aaa new_market 885 95,709 44-44 68601a96edf7f378f23e0dd18bcf42b1bc2e4ebc85412425642cdd36951e15be price_change 100,056,342 986,849,066 45-426 1b531014aec094f61a04b40b439446b48f905abf770c2715eca7edc6d02c1c42 tick_size_change 3,280 119,133 427-427 840b31ca827f39fb52a9ac77190748dd3fb45d4cb1aa679e3f86eef6e4d71298 EVENT MIX count share price_change 100,056,342 90.05% best_bid_ask 9,695,715 8.73% book 1,296,618 1.17% last_trade_price 61,487 0.06% tick_size_change 3,280 <0.01% market_resolved 1,132 <0.01% new_market 885 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,695,899 9,695,715 184 2,137 FULL book 1,300,734 1,296,618 4,116 191,449 FULL last_trade_price 61,488 61,487 1 194 FULL market_resolved 1,132 1,132 0 117 FULL new_market 885 885 0 0 FULL price_change 100,058,002 100,056,342 1,660 2,030 FULL tick_size_change 3,280 3,280 0 77 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,490,154 8,034,959 5ms 10ms 80ms 2.4s 0 transport_latency_assumed best_bid_ask e 9,694,434 75,871 35ms 42ms 143ms 3.4s 0 transport_latency_assumed best_bid_ask f 9,694,394 12,519 47ms 55ms 164ms 4.4s 0 transport_latency_assumed best_bid_ask g 9,693,860 1,361 85ms 99ms 294ms 8.8s 0 transport_latency_assumed best_bid_ask h 9,695,078 1,571,005 13ms 20ms 104ms 17.6s 0 transport_latency_assumed book c 1,279,158 1,265,924 7.4min 23.4h 31.7d 102.6d 0 book_staleness book e 127,743 2,774 37ms 116ms 2.0s 84.0d 0 book_staleness book f 128,003 1,309 50ms 129ms 2.7s 83.9d 0 book_staleness book g 134,994 4,724 91ms 487ms 12.3h 94.8d 0 book_staleness book h 127,691 21,887 17ms 45ms 2.0s 83.9d 0 book_staleness last_trade_price c 53,280 49,967 10ms 40ms 209ms 5.0s 0 transport_latency_assumed last_trade_price e 61,443 710 41ms 105ms 808ms 5.0s 0 transport_latency_assumed last_trade_price f 61,441 213 54ms 117ms 587ms 5.0s 0 transport_latency_assumed last_trade_price g 61,390 18 96ms 216ms 2.1s 8.0s 0 transport_latency_assumed last_trade_price h 61,423 10,579 19ms 55ms 295ms 9.5s 0 transport_latency_assumed market_resolved c 928 881 5ms 5.1min 10.2min 10.2min 0 transport_latency_assumed market_resolved e 1,000 20 36ms 127ms 439ms 1.0min 0 transport_latency_assumed market_resolved f 1,000 2 48ms 133ms 467ms 1.0min 0 transport_latency_assumed market_resolved g 1,000 not meas. 86ms 251ms 741ms 1.4s 0 transport_latency_assumed market_resolved h 1,000 229 14ms 58ms 264ms 1.0min 0 transport_latency_assumed new_market c 682 358 95ms 3.9min 7.1min 7.2min 0 transport_latency_assumed new_market e 605 117 159ms 14.6s 29.8s 1.2min 0 transport_latency_assumed new_market f 605 52 160ms 15.1s 23.1s 1.1min 0 transport_latency_assumed new_market g 605 77 286ms 21.0s 56.5s 1.1min 0 transport_latency_assumed new_market h 605 281 94ms 15.7s 54.3s 1.1min 0 transport_latency_assumed price_change c 87,404,227 82,580,900 5ms 11ms 88ms 3.7s 0 transport_latency_assumed price_change e 99,918,210 847,041 36ms 45ms 191ms 3.7s 0 transport_latency_assumed price_change f 99,926,480 146,533 47ms 59ms 207ms 4.4s 0 transport_latency_assumed price_change g 99,915,798 20,988 85ms 104ms 392ms 10.2s 0 transport_latency_assumed price_change h 99,863,765 16,460,880 14ms 22ms 123ms 17.7s 0 transport_latency_assumed tick_size_change c 2,972 2,892 5ms 9ms 51ms 152ms 0 transport_latency_assumed tick_size_change e 3,280 28 36ms 45ms 114ms 240ms 0 transport_latency_assumed tick_size_change f 3,280 not meas. 48ms 54ms 126ms 402ms 0 transport_latency_assumed tick_size_change g 3,280 not meas. 83ms 97ms 221ms 254ms 0 transport_latency_assumed tick_size_change h 3,280 360 14ms 25ms 54ms 3.3s 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/11/2026-09-09T11.parquet sha256sum 2026-09-09T11.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.