Hour audit: 2026-09-24T18
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-24T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T18:00:00.000036605+00:00 · last event 2026-09-24T18:59:59.999984160+00:00
VOLUME 125,509,955 rows · 1,387,860,212 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 123,504,911 · i: 123,395,369 · k: 118,842,745 · g: 118,744,869 · c: 102,567,490 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,850,227 (3.86%) · i: 2,032,162 (1.62%) · k: 25,698,478 (20.48%) · g: 199,471 (0.16%) · c: 92,729,617 (73.88%) (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 125,509,955 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cb8c2b4ff3f31e486ba9a0cc19ee44288215c9d259e3d54917808a2d5a1ab9b2
the corpus checksum ledger names this file with the same digest
joined 125,529,845 to merged 125,509,955, minus 19,890 (minus 0.0158%)
boundary drops 19,890 · 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-24T21:03:58Z 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,455,068 147,062,240 0-47 4a810bdaafbbd43df384b18f33f06d8d88b3caa3abab73778e24b31f96c2c0a2 book 2,205,376 95,041,737 48-56 b24ddcf23bfeef3ef236eff5c484f7fdeff7bbd1c03d7cf4902fb555683db754 last_trade_price 57,531 3,280,226 57-57 d53919ed8931d81b75c2c0f314d7d68ad6e77108d7b30b98a5c7746cd97f25d7 market_resolved 1,479 133,444 58-58 c2d2af8d10312cd98add26623a389ce7737cd31bb658f387d61c37acef202f39 new_market 1,155 110,788 59-59 a748d76a6289877c98991603e0b999551b239cf094a1586838fc2a8a1f8845f5 price_change 110,786,426 1,140,695,114 60-482 1db3e148e77f3beac581cc5bf6f69088bb7a061a18d2903c306f06bff92a9119 tick_size_change 2,920 108,371 483-483 d99a2833da57f3239b0a74162c676ccc85eab8df9de64a38bdaf4db14b09ad1e EVENT MIX count share price_change 110,786,426 88.27% best_bid_ask 12,455,068 9.92% book 2,205,376 1.76% last_trade_price 57,531 0.05% tick_size_change 2,920 <0.01% market_resolved 1,479 <0.01% new_market 1,155 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,455,310 12,455,068 242 2,988 FULL book 2,223,109 2,205,376 17,733 193,194 FULL last_trade_price 57,531 57,531 0 438 FULL market_resolved 1,482 1,479 3 104 FULL new_market 1,155 1,155 0 28 FULL price_change 110,788,338 110,786,426 1,912 1,856 FULL tick_size_change 2,920 2,920 0 140 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,238,284 9,309,268 6ms 15ms 104ms 8.3s 0 transport_latency_assumed best_bid_ask g 11,962,853 967 82ms 113ms 419ms 21.3s 0 transport_latency_assumed best_bid_ask h 12,452,986 442,064 18ms 40ms 126ms 6.8s 0 transport_latency_assumed best_bid_ask i 12,453,839 185,386 23ms 33ms 115ms 6.5s 0 transport_latency_assumed best_bid_ask k 11,950,548 2,517,383 13ms 20ms 94ms 39.9s 0 transport_latency_assumed book c 1,878,943 1,814,437 9.7min 5.2d 44.0d 117.9d 0 book_staleness book g 601,201 185,399 8.1min 3.5d 39.0d 117.8d 0 book_staleness book h 233,432 45,467 680ms 2.0d 33.2d 117.9d 0 book_staleness book i 119,377 4,875 26ms 162ms 28.8min 99.3d 0 book_staleness book k 609,037 155,198 7.2min 3.1d 40.2d 117.8d 0 book_staleness last_trade_price c 45,237 40,281 7ms 24ms 186ms 1.1s 0 transport_latency_assumed last_trade_price g 54,049 15 92ms 1.4s 10.8s 21.2s 0 transport_latency_assumed last_trade_price h 57,421 2,964 20ms 71ms 390ms 3.9s 0 transport_latency_assumed last_trade_price i 57,401 1,473 26ms 108ms 852ms 3.9s 0 transport_latency_assumed last_trade_price k 54,409 12,798 14ms 40ms 282ms 36.5s 0 transport_latency_assumed market_resolved c 1,287 1,166 5.4min 15.5min 23.6min 23.9min 0 transport_latency_assumed market_resolved g 701 22 85ms 1.1s 6.1min 6.1min 0 transport_latency_assumed market_resolved h 691 25 19ms 123ms 56.0s 57.2s 0 transport_latency_assumed market_resolved i 691 132 26ms 38.1s 54.4s 54.5s 0 transport_latency_assumed market_resolved k 684 134 14ms 102ms 5.1min 5.1min 0 transport_latency_assumed new_market c 853 507 106ms 7.4min 19.0min 19.0min 0 transport_latency_assumed new_market g 656 49 257ms 9.5s 18.0s 5.0min 0 transport_latency_assumed new_market h 654 198 76ms 10.6s 39.0s 1.7min 0 transport_latency_assumed new_market i 654 147 83ms 10.0s 28.3s 1.4min 0 transport_latency_assumed new_market k 654 254 58ms 9.8s 30.2s 2.8min 0 transport_latency_assumed price_change c 90,400,378 81,561,766 6ms 17ms 120ms 9.0s 0 transport_latency_assumed price_change g 106,122,597 13,019 83ms 156ms 4.5s 21.4s 0 transport_latency_assumed price_change h 110,756,807 4,359,472 18ms 45ms 165ms 6.8s 0 transport_latency_assumed price_change i 110,760,487 1,840,122 24ms 40ms 191ms 6.5s 0 transport_latency_assumed price_change k 106,224,537 23,012,047 13ms 23ms 120ms 40.4s 0 transport_latency_assumed tick_size_change c 2,508 2,192 6ms 23ms 136ms 280ms 0 transport_latency_assumed tick_size_change g 2,812 not meas. 81ms 112ms 421ms 588ms 0 transport_latency_assumed tick_size_change h 2,920 37 18ms 44ms 117ms 3.2s 0 transport_latency_assumed tick_size_change i 2,920 27 23ms 30ms 79ms 180ms 0 transport_latency_assumed tick_size_change k 2,876 664 13ms 19ms 89ms 254ms 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/18/2026-09-24T18.parquet sha256sum 2026-09-24T18.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.