Hour audit: 2026-09-24T17
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-24T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T17:00:00.000092756+00:00 · last event 2026-09-24T17:59:59.999995438+00:00
VOLUME 127,319,275 rows · 1,412,778,743 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 125,268,699 · h: 120,310,477 · k: 120,166,377 · g: 116,762,637 · c: 96,220,390 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 5,797,577 (4.55%) · h: 3,957,507 (3.11%) · k: 32,848,144 (25.80%) · g: 291,522 (0.23%) · c: 84,424,525 (66.31%) (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 127,319,275 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cc412da6a7c240c8987143548cc993b328b6cf6150beaed109cadeb379e90fe0
the corpus checksum ledger names this file with the same digest
joined 127,323,151 to merged 127,319,275, minus 3,876 (minus 0.0030%)
boundary drops 3,876 · 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-24T20:07:10Z 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,627,160 149,801,715 0-48 fb569730d6a124279d3645c5ac101c83f547df9067e291f957e83cd0bc13d65c book 2,151,974 95,298,310 49-57 dfba64f1406b83bf80723b6863ef0fb8ea237bed1f4a490d81d627f3f120d5d9 last_trade_price 63,939 3,627,870 58-58 890ca1edd3764151d7ebbcff0ad635c6dbf79a4b8dd7d117f39848b496348e33 market_resolved 792 113,274 59-59 4853b2f3992070e176ca246ab1f01b051e31cb9ff5e781926d70238893d0fbea new_market 1,090 116,343 60-60 3e76f2c31cf4256103ac5de53cdeb7848f12cb600a4345e7feea83ee80c4bd79 price_change 112,472,312 1,162,294,541 61-490 ef24ad23ea5c24fb37535ead45d6e73b53e5d0fd969f27b306e5f43f11715496 tick_size_change 2,008 73,327 491-491 f166f3438d5b249eb11683d2554c97c3bc534bf6cdc4eca7088c9b47a307c502 EVENT MIX count share price_change 112,472,312 88.34% best_bid_ask 12,627,160 9.92% book 2,151,974 1.69% last_trade_price 63,939 0.05% tick_size_change 2,008 <0.01% new_market 1,090 <0.01% market_resolved 792 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,627,508 12,627,160 348 3,808 FULL book 2,153,324 2,151,974 1,350 169,397 FULL last_trade_price 63,939 63,939 0 532 FULL market_resolved 792 792 0 41 FULL new_market 1,090 1,090 0 0 FULL price_change 112,474,490 112,472,312 2,178 1,379 FULL tick_size_change 2,008 2,008 0 139 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,572,590 8,458,977 6ms 19ms 142ms 3.7s 0 transport_latency_assumed best_bid_ask g 11,810,937 2,317 82ms 115ms 475ms 29.2s 0 transport_latency_assumed best_bid_ask h 12,102,737 354,264 19ms 47ms 135ms 12.5s 0 transport_latency_assumed best_bid_ask i 12,624,848 552,019 22ms 36ms 131ms 9.0s 0 transport_latency_assumed best_bid_ask k 12,095,142 3,259,583 13ms 22ms 91ms 7.0s 0 transport_latency_assumed book c 1,875,240 1,584,364 9.6min 5.1d 43.9d 117.8d 0 book_staleness book g 601,233 265,924 4.7min 3.1d 40.1d 117.8d 0 book_staleness book h 590,057 147,846 3.7min 3.0d 36.6d 117.8d 0 book_staleness book i 180,010 32,284 42ms 26.2min 19.1d 117.8d 0 book_staleness book k 559,852 121,556 3.2min 2.9d 35.0d 117.8d 0 book_staleness last_trade_price c 48,347 41,897 7ms 32ms 209ms 1.5s 0 transport_latency_assumed last_trade_price g 56,344 24 97ms 4.0s 17.2s 29.2s 0 transport_latency_assumed last_trade_price h 61,088 2,090 21ms 77ms 365ms 8.8s 0 transport_latency_assumed last_trade_price i 63,616 2,929 26ms 143ms 1.1s 9.0s 0 transport_latency_assumed last_trade_price k 61,199 16,999 14ms 44ms 233ms 1.5s 0 transport_latency_assumed market_resolved c 694 561 6ms 4.1min 7.0min 7.0min 0 transport_latency_assumed market_resolved g 700 43 84ms 481ms 6.2min 6.2min 0 transport_latency_assumed market_resolved h 731 19 21ms 366ms 6.7min 6.7min 0 transport_latency_assumed market_resolved i 700 47 24ms 91ms 29.0s 54.9s 0 transport_latency_assumed market_resolved k 700 122 13ms 42ms 3.7min 4.3min 0 transport_latency_assumed new_market c 768 355 79ms 33.7s 6.1min 6.1min 0 transport_latency_assumed new_market g 743 66 300ms 14.4s 4.5min 6.4min 0 transport_latency_assumed new_market h 753 193 99ms 14.1s 3.3min 3.5min 0 transport_latency_assumed new_market i 743 130 112ms 12.2s 1.0min 1.7min 0 transport_latency_assumed new_market k 743 346 71ms 14.1s 1.0min 1.6min 0 transport_latency_assumed price_change c 84,721,287 74,337,035 6ms 22ms 155ms 4.4s 0 transport_latency_assumed price_change g 104,290,748 23,148 83ms 171ms 8.1s 29.2s 0 transport_latency_assumed price_change h 107,553,127 3,453,036 19ms 52ms 175ms 17.4s 0 transport_latency_assumed price_change i 112,396,774 5,210,089 23ms 45ms 238ms 9.0s 0 transport_latency_assumed price_change k 107,446,769 29,449,004 13ms 26ms 110ms 7.1s 0 transport_latency_assumed tick_size_change c 1,464 1,336 6ms 14ms 96ms 182ms 0 transport_latency_assumed tick_size_change g 1,932 not meas. 82ms 115ms 221ms 447ms 0 transport_latency_assumed tick_size_change h 1,984 59 19ms 52ms 130ms 4.7s 0 transport_latency_assumed tick_size_change i 2,008 79 23ms 32ms 103ms 222ms 0 transport_latency_assumed tick_size_change k 1,972 534 13ms 28ms 89ms 225ms 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/17/2026-09-24T17.parquet sha256sum 2026-09-24T17.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.