Hour audit: 2026-09-24T04
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-24T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T04:00:00.000092029+00:00 · last event 2026-09-24T04:59:59.999983265+00:00
VOLUME 112,337,837 rows · 1,145,841,759 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 112,245,855 · i: 112,240,366 · k: 112,234,760 · h: 112,191,750 · g: 112,172,204 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,892,277 (90.70%) · i: 1,965,168 (1.75%) · k: 6,585,178 (5.86%) · h: 1,875,681 (1.67%) · g: 19,533 (0.02%) (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 112,337,837 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6b1b74ceec1756aff1a0016303c0cf2cba303fe9c997bda4d520c566bbbc06a2
the corpus checksum ledger names this file with the same digest
joined 112,339,395 to merged 112,337,837, minus 1,558 (minus 0.0014%)
boundary drops 1,558 · 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-24T08:48:54Z 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,038,966 138,157,106 0-45 c8f82729eb5340d911963f3cadde12eca2cca1961a70080e218db70e5dcad035 book 168,415 17,038,626 46-46 3c8b4ce96e0586df8bc1211ac747612bd6bea54d7ffdfc2a628ab0b7fa3993f7 last_trade_price 43,643 2,488,832 47-47 e92a53771ff2f9e0eb46381b8c7c0ffe4e1d2562e97ad935643d8760ba6ad41a market_resolved 1,009 158,422 48-48 c65e6bc9bce5a5ab0e96cf9ce4764281298555bd4ec226175ab9aa53e6cb6300 new_market 2,658 283,608 49-49 01ed69b3c0be82a5709de2b44a84a30fd9ce751a9472e54b52ed5d029d8086f8 price_change 100,079,826 986,318,905 50-431 c54c87f64095028f8f6cd0601ab0d8c705f75839dc90ee8bd5e043d6a865e0dd tick_size_change 3,320 118,696 432-432 7d46b12faa3e5e344756639c46e76a24dfbfbe38bd793098b81fb91931db757e EVENT MIX count share price_change 100,079,826 89.09% best_bid_ask 12,038,966 10.72% book 168,415 0.15% last_trade_price 43,643 0.04% tick_size_change 3,320 <0.01% new_market 2,658 <0.01% market_resolved 1,009 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,039,133 12,038,966 167 114 FULL book 168,465 168,415 50 30,767 FULL last_trade_price 43,644 43,643 1 0 FULL market_resolved 1,009 1,009 0 54 FULL new_market 2,658 2,658 0 0 FULL price_change 100,081,166 100,079,826 1,340 295 FULL tick_size_change 3,320 3,320 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,037,997 11,039,502 4ms 14ms 193ms 12.9s 0 transport_latency_assumed best_bid_ask g 12,036,127 948 80ms 110ms 495ms 16.1s 0 transport_latency_assumed best_bid_ask h 12,037,127 173,838 17ms 36ms 400ms 36.2s 0 transport_latency_assumed best_bid_ask i 12,037,318 198,995 21ms 30ms 126ms 4.1s 0 transport_latency_assumed best_bid_ask k 12,037,211 625,683 12ms 21ms 187ms 9.5s 0 transport_latency_assumed book c 108,670 93,813 7ms 5.7min 15.4d 98.8d 0 book_staleness book g 99,284 7,919 85ms 3.6s 4.6d 98.7d 0 book_staleness book h 97,220 9,240 21ms 1.2s 3.3d 117.3d 0 book_staleness book i 115,973 27,654 25ms 15.6min 16.7d 98.8d 0 book_staleness book k 114,156 29,789 16ms 13.8min 16.7d 117.3d 0 book_staleness last_trade_price c 43,467 38,168 5ms 31ms 267ms 3.6s 0 transport_latency_assumed last_trade_price g 43,233 16 82ms 249ms 3.4s 16.1s 0 transport_latency_assumed last_trade_price h 43,409 1,010 19ms 63ms 470ms 10.1s 0 transport_latency_assumed last_trade_price i 43,485 865 23ms 63ms 303ms 2.9s 0 transport_latency_assumed last_trade_price k 43,330 3,584 14ms 38ms 317ms 7.6s 0 transport_latency_assumed market_resolved c 976 807 5ms 473ms 48.0s 48.0s 0 transport_latency_assumed market_resolved g 922 not meas. 82ms 415ms 36.9s 42.8s 0 transport_latency_assumed market_resolved h 976 15 19ms 19.2s 54.8s 54.8s 0 transport_latency_assumed market_resolved i 976 154 22ms 20.7s 54.3s 54.4s 0 transport_latency_assumed market_resolved k 922 33 13ms 92ms 41.5s 46.6s 0 transport_latency_assumed new_market c 1,850 681 120ms 16.5s 2.1min 3.3min 0 transport_latency_assumed new_market g 1,850 162 281ms 16.6s 2.0min 3.3min 0 transport_latency_assumed new_market h 1,850 514 158ms 16.4s 2.0min 3.3min 0 transport_latency_assumed new_market i 1,850 824 110ms 17.4s 2.1min 3.3min 0 transport_latency_assumed new_market k 1,850 477 169ms 14.3s 2.2min 2.9min 0 transport_latency_assumed price_change c 100,049,575 90,716,162 5ms 18ms 203ms 13.4s 0 transport_latency_assumed price_change g 99,987,468 10,488 81ms 128ms 679ms 16.2s 0 transport_latency_assumed price_change h 100,007,848 1,691,048 18ms 41ms 376ms 36.4s 0 transport_latency_assumed price_change i 100,037,444 1,736,640 21ms 35ms 158ms 4.1s 0 transport_latency_assumed price_change k 100,033,971 5,925,488 13ms 25ms 199ms 9.6s 0 transport_latency_assumed tick_size_change c 3,320 3,144 4ms 7ms 75ms 160ms 0 transport_latency_assumed tick_size_change g 3,320 not meas. 80ms 96ms 378ms 890ms 0 transport_latency_assumed tick_size_change h 3,320 16 18ms 30ms 122ms 680ms 0 transport_latency_assumed tick_size_change i 3,320 36 21ms 26ms 65ms 198ms 0 transport_latency_assumed tick_size_change k 3,320 124 12ms 16ms 51ms 474ms 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/04/2026-09-24T04.parquet sha256sum 2026-09-24T04.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.