Hour audit: 2026-09-24T11
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-24T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T11:00:00.000296281+00:00 · last event 2026-09-24T11:59:59.999995766+00:00
VOLUME 122,871,517 rows · 1,331,489,178 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 121,843,149 · i: 121,784,865 · g: 121,487,571 · c: 116,094,487 · k: 111,934,653 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,772,364 (3.88%) · i: 1,603,809 (1.31%) · g: 85,017 (0.07%) · c: 105,975,454 (86.25%) · k: 10,434,873 (8.49%) (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 122,871,517 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2db4850f18c3e09486cd434352d2e790a3aef4e0c72eccdf9d905cfda8e1a219
the corpus checksum ledger names this file with the same digest
joined 122,878,876 to merged 122,871,517, minus 7,359 (minus 0.0060%)
boundary drops 7,359 · 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-24T13:19:36Z 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,676,173 146,854,718 0-48 5ebee6c9602c358a27865d9cbc4c751c5c7f08715852128dcaf1e6563ee29879 book 1,215,929 73,505,850 49-53 49b1a4458b25aa3bec5dceb21c45318d47f286602d502f77f498f04d90a1ec45 last_trade_price 58,262 3,294,975 54-54 3b1e13303d19570dd83f63375146ffc7da6451693852cc7abf8788b45106ed07 market_resolved 979 125,702 55-55 0ccb4578d8e2d3cd86279555953171d0df48421ebd4fa004a6fdbd5f4f837edd new_market 710 79,435 56-56 d5adb117c88d5c2b1b0023dfef292764f873e5c03be174098d8fd9b6fb1f8207 price_change 108,916,404 1,106,116,757 57-472 d2cc1c8d09351fdd997cf3dcb61de6c4ef2590d58817210275efad3e530446a5 tick_size_change 3,060 113,265 473-473 c65a51d320197706417b7b2fca6f7e53c864ce4ca0395c1b47916e04acfad0fd EVENT MIX count share price_change 108,916,404 88.64% best_bid_ask 12,676,173 10.32% book 1,215,929 0.99% last_trade_price 58,262 0.05% tick_size_change 3,060 <0.01% market_resolved 979 <0.01% new_market 710 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,676,380 12,676,173 207 1,054 FULL book 1,221,347 1,215,929 5,418 191,765 FULL last_trade_price 58,262 58,262 0 227 FULL market_resolved 979 979 0 26 FULL new_market 710 710 0 0 FULL price_change 108,918,138 108,916,404 1,734 141 FULL tick_size_change 3,060 3,060 0 78 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,079,166 11,115,571 5ms 14ms 104ms 2.0s 0 transport_latency_assumed best_bid_ask g 12,668,690 1,136 80ms 105ms 350ms 23.0s 0 transport_latency_assumed best_bid_ask h 12,673,766 439,448 19ms 35ms 188ms 17.4s 0 transport_latency_assumed best_bid_ask i 12,674,079 146,316 23ms 34ms 123ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,620,676 973,702 13ms 20ms 82ms 1.3s 0 transport_latency_assumed book c 597,635 349,997 4.4min 3.6d 39.9d 117.6d 0 book_staleness book g 212,409 66,024 972ms 1.6d 32.9d 117.6d 0 book_staleness book h 246,155 84,481 4.1s 1.8d 32.9d 117.6d 0 book_staleness book i 193,699 62,118 84ms 14.4h 29.7d 117.5d 0 book_staleness book k 970,042 653,309 6.8min 3.9d 42.7d 117.5d 0 book_staleness last_trade_price c 53,984 48,220 6ms 29ms 213ms 1.2s 0 transport_latency_assumed last_trade_price g 56,795 48 91ms 657ms 10.5s 23.0s 0 transport_latency_assumed last_trade_price h 58,021 3,177 21ms 97ms 566ms 7.1s 0 transport_latency_assumed last_trade_price i 57,938 970 26ms 186ms 966ms 2.2s 0 transport_latency_assumed last_trade_price k 51,826 5,847 14ms 42ms 242ms 1.2s 0 transport_latency_assumed market_resolved c 758 554 6ms 51.1s 5.4min 6.4min 0 transport_latency_assumed market_resolved g 761 not meas. 82ms 30.1s 55.9s 55.9s 0 transport_latency_assumed market_resolved h 761 168 22ms 36.9s 44.9s 56.3s 0 transport_latency_assumed market_resolved i 761 97 24ms 89ms 56.9s 57.2s 0 transport_latency_assumed market_resolved k 812 160 15ms 5.4min 8.7min 10.4min 0 transport_latency_assumed new_market c 514 224 75ms 12.2s 6.4min 6.5min 0 transport_latency_assumed new_market g 506 19 288ms 9.2s 17.7s 1.4min 0 transport_latency_assumed new_market h 506 138 121ms 10.1s 37.8s 1.3min 0 transport_latency_assumed new_market i 506 122 114ms 11.6s 17.9s 1.7min 0 transport_latency_assumed new_market k 514 207 72ms 396ms 7.4min 7.5min 0 transport_latency_assumed price_change c 103,359,490 94,458,226 5ms 17ms 120ms 3.7s 0 transport_latency_assumed price_change g 108,545,350 17,790 81ms 138ms 1.5s 23.2s 0 transport_latency_assumed price_change h 108,860,880 4,244,840 19ms 41ms 246ms 17.9s 0 transport_latency_assumed price_change i 108,854,822 1,394,158 23ms 43ms 227ms 4.0s 0 transport_latency_assumed price_change k 99,287,955 8,801,390 13ms 23ms 103ms 1.3s 0 transport_latency_assumed tick_size_change c 2,940 2,662 5ms 16ms 73ms 454ms 0 transport_latency_assumed tick_size_change g 3,060 not meas. 81ms 103ms 254ms 2.8s 0 transport_latency_assumed tick_size_change h 3,060 112 19ms 39ms 133ms 371ms 0 transport_latency_assumed tick_size_change i 3,060 28 23ms 41ms 142ms 603ms 0 transport_latency_assumed tick_size_change k 2,828 258 13ms 22ms 79ms 263ms 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/11/2026-09-24T11.parquet sha256sum 2026-09-24T11.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.