Hour audit: 2026-09-23T23
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-23T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T23:00:00.000031197+00:00 · last event 2026-09-23T23:59:59.999987944+00:00
VOLUME 116,974,823 rows · 1,247,074,847 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 114,942,022 · i: 114,938,202 · h: 114,896,322 · g: 114,786,800 · c: 91,796,327 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 28,425,602 (24.30%) · i: 1,265,437 (1.08%) · h: 2,601,151 (2.22%) · g: 25,356 (0.02%) · c: 84,657,277 (72.37%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,974,823 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 433caed441b73d82c84e5429ad0b8578f7039783fd38c7077213fd8a80c727eb
the corpus checksum ledger names this file with the same digest
joined 116,980,474 to merged 116,974,823, minus 5,651 (minus 0.0048%)
boundary drops 5,651 · 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-24T06:30:14Z 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 11,399,850 131,487,509 0-43 18ea301c74a6a8203672b981791b628dd5b74faf9bcfc51945ed327b55ed02e2 book 2,109,773 84,224,786 44-52 1b38aa5941cc828b701c018cc9651b21b94de5ed3fc495daa317791ab88b940b last_trade_price 50,911 2,855,313 53-53 f9991ed24a236b03819fc3bb75aacaf9c7e136df73addb2f088adf4a4fbd74e9 market_resolved 1,256 170,803 54-54 2bb1c1ac73bf57a1a29e6c10ca3261146315464061760f758dfefbfb46c83d90 new_market 1,047 109,377 55-55 11e800d2ad7419e11b42ad8c8c83e4f1d0017ad650a453755031fadbeeab19df price_change 103,409,458 1,026,799,163 56-450 07b5d8f761919a154fe2569151baf017cd11481be936be675bc0b6fc751c0792 tick_size_change 2,528 93,782 451-451 a8ae1096f3c6a3dc9492fe72d8e40c46bee54f9834e3e924ac3dad35bf46a812 EVENT MIX count share price_change 103,409,458 88.40% best_bid_ask 11,399,850 9.75% book 2,109,773 1.80% last_trade_price 50,911 0.04% tick_size_change 2,528 <0.01% market_resolved 1,256 <0.01% new_market 1,047 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,400,382 11,399,850 532 3,370 FULL book 2,109,799 2,109,773 26 196,715 FULL last_trade_price 50,912 50,911 1 312 FULL market_resolved 1,256 1,256 0 178 FULL new_market 1,047 1,047 0 0 FULL price_change 103,414,550 103,409,458 5,092 2,146 FULL tick_size_change 2,528 2,528 0 117 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,935,268 8,281,638 5ms 12ms 102ms 7.2s 0 transport_latency_assumed best_bid_ask g 11,394,544 888 82ms 105ms 345ms 13.9s 0 transport_latency_assumed best_bid_ask h 11,397,355 245,169 18ms 29ms 145ms 38.8s 0 transport_latency_assumed best_bid_ask i 11,397,940 117,715 23ms 31ms 114ms 6.3s 0 transport_latency_assumed best_bid_ask k 11,397,794 2,754,440 12ms 19ms 93ms 27.4s 0 transport_latency_assumed book c 2,070,492 2,050,272 11.3min 4.4d 43.2d 117.1d 0 book_staleness book g 104,892 2,400 87ms 961ms 17.7h 98.5d 0 book_staleness book h 122,191 15,454 24ms 4.0min 15.2d 117.0d 0 book_staleness book i 111,194 5,459 27ms 767ms 2.2d 98.6d 0 book_staleness book k 120,342 36,188 16ms 2.3min 12.2d 98.6d 0 book_staleness last_trade_price c 39,128 34,922 6ms 27ms 226ms 1.1s 0 transport_latency_assumed last_trade_price g 49,652 124 87ms 364ms 7.7s 13.7s 0 transport_latency_assumed last_trade_price h 50,486 1,179 20ms 116ms 498ms 11.3s 0 transport_latency_assumed last_trade_price i 50,658 735 26ms 171ms 1.0s 4.5s 0 transport_latency_assumed last_trade_price k 50,631 13,951 14ms 41ms 269ms 2.8s 0 transport_latency_assumed market_resolved c 932 849 5ms 4.4min 9.4min 11.3min 0 transport_latency_assumed market_resolved g 1,040 not meas. 84ms 395ms 48.1s 1.0min 0 transport_latency_assumed market_resolved h 1,040 24 19ms 26.3s 56.8s 59.3s 0 transport_latency_assumed market_resolved i 1,040 144 23ms 25.5s 56.4s 59.5s 0 transport_latency_assumed market_resolved k 1,040 239 13ms 66ms 45.8s 1.0min 0 transport_latency_assumed new_market c 778 399 68ms 4.3min 6.2min 6.4min 0 transport_latency_assumed new_market g 695 88 239ms 15.8s 1.4min 1.7min 0 transport_latency_assumed new_market h 695 164 93ms 7.6s 49.0s 1.7min 0 transport_latency_assumed new_market i 695 254 58ms 9.9s 1.1min 1.8min 0 transport_latency_assumed new_market k 695 142 115ms 9.0s 1.1min 1.6min 0 transport_latency_assumed price_change c 80,747,669 74,287,267 5ms 14ms 117ms 9.9s 0 transport_latency_assumed price_change g 103,233,449 21,856 82ms 122ms 831ms 14.0s 0 transport_latency_assumed price_change h 103,322,027 2,339,132 18ms 35ms 220ms 40.0s 0 transport_latency_assumed price_change i 103,374,147 1,141,126 23ms 37ms 205ms 6.5s 0 transport_latency_assumed price_change k 103,368,992 25,620,077 13ms 21ms 110ms 27.7s 0 transport_latency_assumed tick_size_change c 2,060 1,930 5ms 10ms 36ms 121ms 0 transport_latency_assumed tick_size_change g 2,528 not meas. 82ms 98ms 216ms 482ms 0 transport_latency_assumed tick_size_change h 2,528 29 18ms 27ms 65ms 261ms 0 transport_latency_assumed tick_size_change i 2,528 4 23ms 32ms 89ms 2.6s 0 transport_latency_assumed tick_size_change k 2,528 565 12ms 17ms 75ms 126ms 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-23/23/2026-09-23T23.parquet sha256sum 2026-09-23T23.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.