Hour audit: 2026-09-24T10
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-24T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T10:00:00.000017296+00:00 · last event 2026-09-24T10:59:59.999858764+00:00
VOLUME 126,295,632 rows · 1,388,614,814 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 124,631,715 · i: 119,882,073 · g: 119,467,985 · k: 115,025,230 · c: 109,703,714 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,973,615 (6.31%) · i: 3,186,758 (2.52%) · g: 288,230 (0.23%) · k: 15,520,666 (12.29%) · c: 99,326,363 (78.65%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 eb2eb7d9e4cc15466c55003d08234822cbfd20264f7d32a2918ac057f2754e3f
the corpus checksum ledger names this file with the same digest
joined 126,304,513 to merged 126,295,632, minus 8,881 (minus 0.0070%)
boundary drops 8,881 · 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-24T12:47:33Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 12,917,972 151,473,779 0-49 2686b048306008c9ea3e2fd93f0a3b4017fcca79404410e183fb10470d47e759 book 1,885,215 93,659,401 50-57 60df7ae55c7ea59604f67b8366eee7f31909d0c0ac58a18a2d000f1af3ec4e21 last_trade_price 56,827 3,254,723 58-58 3728ea269ed60a2bcf87d21668b86f3fa2224ee9db53507314837146c25f3640 market_resolved 974 116,949 59-59 e88538f5f25982b369088ce6631ee192c6edb8a7a2f06efe6f523b21074c3150 new_market 658 71,347 60-60 217b300d4067a5cdb8289940ca40a97499627a3a9347c8286d87970db3b1d3cf price_change 111,430,298 1,138,462,640 61-486 f0139b8e50a4432c0bd74121ab43d3160e7d763b94fb9f08421980c96633f31e tick_size_change 3,688 136,258 487-487 94206724ef97b66ea331de1678e6fcfe209f87451ab866502c1afacd08b1cefc EVENT MIX count share price_change 111,430,298 88.23% best_bid_ask 12,917,972 10.23% book 1,885,215 1.49% last_trade_price 56,827 0.04% tick_size_change 3,688 <0.01% market_resolved 974 <0.01% new_market 658 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,918,900 12,917,972 928 1,880 FULL book 1,885,859 1,885,215 644 119,630 FULL last_trade_price 56,836 56,827 9 313 FULL market_resolved 974 974 0 15 FULL new_market 658 658 0 0 FULL price_change 111,437,598 111,430,298 7,300 385 FULL tick_size_change 3,688 3,688 0 196 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,217,256 10,275,019 5ms 14ms 107ms 9.5s 0 transport_latency_assumed best_bid_ask g 12,368,195 4,005 80ms 104ms 358ms 22.0s 0 transport_latency_assumed best_bid_ask h 12,915,408 826,453 19ms 36ms 142ms 48.4s 0 transport_latency_assumed best_bid_ask i 12,370,439 301,737 22ms 32ms 121ms 4.7s 0 transport_latency_assumed best_bid_ask k 11,824,823 1,510,758 13ms 20ms 84ms 2.7s 0 transport_latency_assumed book c 1,353,507 653,653 10.1min 4.8d 42.8d 117.5d 0 book_staleness book g 641,885 237,409 5.7min 3.6d 39.8d 117.5d 0 book_staleness book h 289,328 108,895 35.0s 2.6d 32.9d 117.5d 0 book_staleness book i 563,918 180,444 5.1min 2.8d 38.6d 117.5d 0 book_staleness book k 994,981 704,814 8.2min 3.8d 42.7d 117.5d 0 book_staleness last_trade_price c 50,101 44,541 6ms 29ms 273ms 2.6s 0 transport_latency_assumed last_trade_price g 52,992 34 89ms 836ms 9.4s 22.0s 0 transport_latency_assumed last_trade_price h 56,572 3,461 21ms 120ms 999ms 14.9s 0 transport_latency_assumed last_trade_price i 53,941 1,429 25ms 159ms 1.7s 4.7s 0 transport_latency_assumed last_trade_price k 52,156 7,362 14ms 40ms 227ms 1.3s 0 transport_latency_assumed market_resolved c 832 545 8ms 7.6min 10.9min 12.2min 0 transport_latency_assumed market_resolved g 697 26 88ms 50.7s 5.8min 5.8min 0 transport_latency_assumed market_resolved h 696 111 21ms 32.3s 53.1s 53.1s 0 transport_latency_assumed market_resolved i 696 101 24ms 1.8min 4.9min 5.2min 0 transport_latency_assumed market_resolved k 795 191 14ms 7.9min 9.8min 11.0min 0 transport_latency_assumed new_market c 494 244 73ms 38.4s 6.0min 6.0min 0 transport_latency_assumed new_market g 473 56 237ms 10.4s 6.3min 6.3min 0 transport_latency_assumed new_market h 459 88 76ms 12.7s 18.5s 1.3min 0 transport_latency_assumed new_market i 459 85 84ms 13.4s 21.4s 1.7min 0 transport_latency_assumed new_market k 478 185 60ms 15.9s 5.0min 5.1min 0 transport_latency_assumed price_change c 97,078,136 88,349,270 5ms 17ms 127ms 9.6s 0 transport_latency_assumed price_change g 106,400,391 46,696 81ms 133ms 1.7s 22.1s 0 transport_latency_assumed price_change h 111,365,564 7,034,447 19ms 42ms 221ms 48.5s 0 transport_latency_assumed price_change i 106,889,112 2,702,844 22ms 39ms 226ms 4.8s 0 transport_latency_assumed price_change k 102,148,633 13,297,041 13ms 23ms 103ms 4.0s 0 transport_latency_assumed tick_size_change c 3,388 3,091 5ms 13ms 76ms 205ms 0 transport_latency_assumed tick_size_change g 3,352 4 80ms 95ms 254ms 369ms 0 transport_latency_assumed tick_size_change h 3,688 160 19ms 41ms 127ms 384ms 0 transport_latency_assumed tick_size_change i 3,508 118 21ms 26ms 71ms 332ms 0 transport_latency_assumed tick_size_change k 3,364 315 12ms 18ms 49ms 129ms 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-24/10/2026-09-24T10.parquet sha256sum 2026-09-24T10.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.