Hour audit: 2026-09-24T08
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-24T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T08:00:00.000005091+00:00 · last event 2026-09-24T08:59:59.999968532+00:00
VOLUME 117,513,816 rows · 1,193,463,132 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 117,473,244 · k: 117,469,436 · c: 117,467,002 · h: 117,347,080 · g: 117,270,643 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 636,927 (0.54%) · k: 7,981,817 (6.79%) · c: 107,723,692 (91.67%) · h: 1,155,631 (0.98%) · g: 15,749 (0.01%) (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 117,513,816 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2e5240d83be321b6b6694f57b0a294e279760beff3e1cb263be63b69c0686f87
the corpus checksum ledger names this file with the same digest
joined 117,515,776 to merged 117,513,816, minus 1,960 (minus 0.0017%)
boundary drops 1,960 · 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-24T10:45:06Z 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,432,780 142,636,817 0-47 4bbf846c102d0ec86a060bf72b2f19023d3b8b0db223843498925d7ecfd919b2 book 143,889 14,792,716 48-48 dd479e2087bf2c6cf5f0b1c37645bb754b29123ac427f8b913185cef0990cc15 last_trade_price 56,955 3,246,124 49-49 b5719e85407c656c4b68a0954ae3a2704aed568acadb220503c5e079c99e8575 market_resolved 546 91,249 50-50 b128f45ea8a8a1fa9a858f990f01a65616784fc56690a77ed8a535241901d5fc new_market 884 101,108 51-51 e95f87903201b74261aeec5d90af90beee9a971d345545bcaa98d45727cfae48 price_change 104,876,498 1,031,171,780 52-452 51e71aba4ffbaef8c15129eedf913edd8125338e025195e3a947de0e8775d9b8 tick_size_change 2,264 83,814 453-453 0cac0bfe8d35a706494cf027d0791644131c11d3fd74a1b5a00ad89bb980451a EVENT MIX count share price_change 104,876,498 89.25% best_bid_ask 12,432,780 10.58% book 143,889 0.12% last_trade_price 56,955 0.05% tick_size_change 2,264 <0.01% new_market 884 <0.01% market_resolved 546 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,432,956 12,432,780 176 134 FULL book 143,899 143,889 10 10,219 FULL last_trade_price 56,955 56,955 0 0 FULL market_resolved 546 546 0 0 FULL new_market 884 884 0 0 FULL price_change 104,878,272 104,876,498 1,774 310 FULL tick_size_change 2,264 2,264 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,432,059 11,466,704 5ms 11ms 87ms 2.7s 0 transport_latency_assumed best_bid_ask g 12,427,730 357 79ms 101ms 344ms 22.0s 0 transport_latency_assumed best_bid_ask h 12,427,489 112,212 18ms 34ms 145ms 14.3s 0 transport_latency_assumed best_bid_ask i 12,431,722 64,732 23ms 31ms 106ms 6.2s 0 transport_latency_assumed best_bid_ask k 12,431,936 788,775 11ms 18ms 81ms 11.1s 0 transport_latency_assumed book c 119,787 106,666 7ms 45ms 1.4d 98.9d 0 book_staleness book g 123,207 9,755 87ms 9.3s 3.5d 98.9d 0 book_staleness book h 118,608 5,758 23ms 131ms 20.4min 98.8d 0 book_staleness book i 115,814 1,765 25ms 139ms 2.3s 98.9d 0 book_staleness book k 125,238 19,945 14ms 156ms 2.7d 98.9d 0 book_staleness last_trade_price c 56,820 50,787 6ms 21ms 188ms 1.3s 0 transport_latency_assumed last_trade_price g 55,870 10 85ms 1.0s 13.2s 21.7s 0 transport_latency_assumed last_trade_price h 56,608 660 20ms 77ms 487ms 7.6s 0 transport_latency_assumed last_trade_price i 56,880 336 26ms 120ms 798ms 4.8s 0 transport_latency_assumed last_trade_price k 56,859 5,162 12ms 32ms 193ms 1.9s 0 transport_latency_assumed market_resolved c 546 482 5ms 25ms 51.9s 51.9s 0 transport_latency_assumed market_resolved g 546 not meas. 81ms 366ms 52.1s 52.2s 0 transport_latency_assumed market_resolved h 546 4 19ms 93ms 43.3s 43.4s 0 transport_latency_assumed market_resolved i 546 26 24ms 147ms 42.8s 42.9s 0 transport_latency_assumed market_resolved k 546 34 12ms 73ms 52.8s 52.8s 0 transport_latency_assumed new_market c 656 254 76ms 14.0s 31.3s 2.0min 0 transport_latency_assumed new_market g 656 67 259ms 13.3s 37.8s 55.1s 0 transport_latency_assumed new_market h 656 189 114ms 13.0s 33.9s 1.6min 0 transport_latency_assumed new_market i 656 160 108ms 11.5s 29.3s 1.4min 0 transport_latency_assumed new_market k 656 214 82ms 8.0s 28.9s 1.3min 0 transport_latency_assumed price_change c 104,854,870 96,096,772 5ms 13ms 98ms 8.4s 0 transport_latency_assumed price_change g 104,660,370 5,560 79ms 117ms 1.6s 22.0s 0 transport_latency_assumed price_change h 104,740,909 1,036,784 18ms 39ms 194ms 14.5s 0 transport_latency_assumed price_change i 104,865,362 569,904 23ms 37ms 169ms 6.2s 0 transport_latency_assumed price_change k 104,851,937 7,167,478 11ms 20ms 94ms 12.6s 0 transport_latency_assumed tick_size_change c 2,264 2,027 5ms 15ms 71ms 251ms 0 transport_latency_assumed tick_size_change g 2,264 not meas. 79ms 99ms 303ms 441ms 0 transport_latency_assumed tick_size_change h 2,264 24 19ms 40ms 175ms 200ms 0 transport_latency_assumed tick_size_change i 2,264 4 23ms 41ms 76ms 172ms 0 transport_latency_assumed tick_size_change k 2,264 209 11ms 22ms 55ms 229ms 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/08/2026-09-24T08.parquet sha256sum 2026-09-24T08.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.