Hour audit: 2026-09-09T21
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-09T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T21:00:00.000020459+00:00 · last event 2026-09-09T21:59:59.999984885+00:00
VOLUME 106,143,475 rows · 1,105,152,937 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 105,505,553 · e: 105,493,129 · f: 105,474,031 · g: 105,415,598 · c: 101,082,985 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,936,688 (7.48%) · e: 678,122 (0.64%) · f: 315,939 (0.30%) · g: 96,593 (0.09%) · c: 97,116,133 (91.50%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,143,475 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4c9edccfd7f159bfad6b2da1355d8e331cce5d5f38342ba4e0424bd67d2a1fd8
the corpus checksum ledger names this file with the same digest
joined 106,147,982 to merged 106,143,475, minus 4,507 (minus 0.0042%)
boundary drops 4,507 · 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-09T23:01:50Z 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,478,232 106,833,302 0-36 208f9977a20a1c8c3dedd541048191990fb1fdcdbe3b4596698bf39a872e539a book 867,964 70,786,065 37-40 6f6ce87e4898256c6d650be7656ba7fc44d0f46fe3de39eda4112a6320ed5a35 last_trade_price 56,949 3,240,762 41-41 aba5f28143b3aa58a0e467307e994df6869d1b1fb85f0fbb14ba81a53a843c22 market_resolved 1,811 294,672 42-42 151024b5f72ac204f360bdb7f732f8ae73b8d521114cccc11ded73fc0b3afc66 new_market 1,113 125,293 43-43 57f3bb2df566fad00c41d73b2727a19f64953d31ee663558ff24be09c3294f7b price_change 95,734,326 922,547,404 44-409 623aed9070ad8e05436a9673c8934c94389fa92465571b56766b29247556eb29 tick_size_change 3,080 112,491 410-410 46bf98a9ae7ab3d6d2da423374898b0c391ed375a0ffa3e721627fec3c1a324f EVENT MIX count share price_change 95,734,326 90.19% best_bid_ask 9,478,232 8.93% book 867,964 0.82% last_trade_price 56,949 0.05% tick_size_change 3,080 <0.01% market_resolved 1,811 <0.01% new_market 1,113 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,478,430 9,478,232 198 737 FULL book 868,510 867,964 546 198,931 FULL last_trade_price 56,950 56,949 1 118 FULL market_resolved 1,811 1,811 0 20 FULL new_market 1,113 1,113 0 0 FULL price_change 95,738,088 95,734,326 3,762 700 FULL tick_size_change 3,080 3,080 0 16 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,026,548 8,708,591 5ms 10ms 98ms 3.7s 0 transport_latency_assumed best_bid_ask e 9,475,771 47,543 41ms 49ms 185ms 7.3s 0 transport_latency_assumed best_bid_ask f 9,475,763 17,130 46ms 57ms 219ms 11.8s 0 transport_latency_assumed best_bid_ask g 9,474,553 2,952 81ms 98ms 299ms 16.9s 0 transport_latency_assumed best_bid_ask h 9,476,602 702,016 18ms 24ms 128ms 7.6s 0 transport_latency_assumed book c 659,298 559,886 7.7min 16.2h 29.1d 103.0d 0 book_staleness book e 260,560 86,127 10.7s 9.5h 18.3d 103.0d 0 book_staleness book f 247,586 78,117 4.5s 9.3h 18.3d 103.0d 0 book_staleness book g 213,066 41,460 236ms 7.2h 18.3d 103.0d 0 book_staleness book h 255,910 102,374 7.6s 9.4h 18.3d 103.0d 0 book_staleness last_trade_price c 54,137 52,031 10ms 41ms 206ms 5.0s 0 transport_latency_assumed last_trade_price e 56,853 360 52ms 224ms 3.5s 7.4s 0 transport_latency_assumed last_trade_price f 56,911 171 62ms 315ms 4.1s 11.9s 0 transport_latency_assumed last_trade_price g 56,750 152 97ms 228ms 2.9s 16.9s 0 transport_latency_assumed last_trade_price h 56,781 4,235 24ms 109ms 582ms 5.0s 0 transport_latency_assumed market_resolved c 1,767 1,692 5ms 11ms 246ms 5.5min 0 transport_latency_assumed market_resolved e 1,785 16 44ms 138ms 515ms 1.0min 0 transport_latency_assumed market_resolved f 1,785 1 49ms 164ms 434ms 889ms 0 transport_latency_assumed market_resolved g 1,785 not meas. 91ms 247ms 632ms 1.5s 0 transport_latency_assumed market_resolved h 1,785 102 19ms 59ms 242ms 1.0min 0 transport_latency_assumed new_market c 795 434 69ms 27.9s 4.4min 4.7min 0 transport_latency_assumed new_market e 795 108 124ms 10.5s 1.3min 1.8min 0 transport_latency_assumed new_market f 795 114 136ms 518ms 1.3min 2.0min 0 transport_latency_assumed new_market g 795 55 214ms 12.6s 1.6min 5.7min 0 transport_latency_assumed new_market h 795 402 76ms 12.5s 1.6min 5.5min 0 transport_latency_assumed price_change c 91,337,424 87,790,579 5ms 11ms 145ms 3.7s 0 transport_latency_assumed price_change e 95,694,285 543,968 41ms 57ms 356ms 7.3s 0 transport_latency_assumed price_change f 95,688,111 220,406 46ms 66ms 436ms 11.9s 0 transport_latency_assumed price_change g 95,665,569 51,974 82ms 105ms 427ms 16.9s 0 transport_latency_assumed price_change h 95,710,600 7,127,399 18ms 28ms 221ms 7.6s 0 transport_latency_assumed tick_size_change c 3,016 2,920 5ms 9ms 53ms 242ms 0 transport_latency_assumed tick_size_change e 3,080 not meas. 41ms 46ms 131ms 379ms 0 transport_latency_assumed tick_size_change f 3,080 not meas. 46ms 55ms 146ms 349ms 0 transport_latency_assumed tick_size_change g 3,080 not meas. 81ms 101ms 279ms 322ms 0 transport_latency_assumed tick_size_change h 3,080 160 18ms 25ms 136ms 728ms 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/21/2026-09-09T21.parquet sha256sum 2026-09-09T21.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.