Hour audit: 2026-09-30T19
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-30T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T19:00:00.000046139+00:00 · last event 2026-09-30T19:59:59.999981081+00:00
VOLUME 109,257,871 rows · 1,139,280,733 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 109,122,866 · k: 109,102,524 · h: 109,073,852 · m: 109,067,985 · g: 108,719,917 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 635,530 (0.58%) · k: 5,703,684 (5.22%) · h: 1,502,168 (1.37%) · m: 101,337,278 (92.75%) · g: 79,211 (0.07%) (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 109,257,871 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0a4dcecb426bba43969f890abe7814c5e7f6c49be5ebb21c9d7c0eab4fb86c79
the corpus checksum ledger names this file with the same digest
joined 109,261,681 to merged 109,257,871, minus 3,810 (minus 0.0035%)
boundary drops 3,810 · 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-30T23:31:11Z as ghikm
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 10,134,628 118,128,137 0-38 a1b9d43ef347185376f624a443255fb19bccdd028da584bdbfad1056e32aeb62 book 216,549 22,978,217 39-39 8a6b9d56ebed88e75a530e3be828aa7e6dbe7ad60cdef91dde90dcd362ebabad last_trade_price 50,826 2,976,834 40-40 760934ca704725ee89f0ee27965c270f32a7d3f9866e813678d295712d749738 market_resolved 721 110,919 41-41 a6f8fcb8e57d6797638f4ba7bfaf457f83983a6537566ab08c8de6650a530e13 new_market 2,527 247,048 42-42 8a2c5cdee28daa291c98e62a7e7df3ac93fed991bf1ba4646355d006d1b75581 price_change 98,849,472 993,477,175 43-420 a33c9011f7b22b907f6ce0db69dbf2d9bef365085c900b2a2d235ed6b1b4c678 tick_size_change 3,148 115,582 421-421 17392c02d0e11a678ceec59421fd274f67f061d86add3cff58e752e52851f200 EVENT MIX count share price_change 98,849,472 90.47% best_bid_ask 10,134,628 9.28% book 216,549 0.20% last_trade_price 50,826 0.05% tick_size_change 3,148 <0.01% new_market 2,527 <0.01% market_resolved 721 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,135,015 10,134,628 387 105 FULL book 216,579 216,549 30 49,982 FULL last_trade_price 50,827 50,826 1 4 FULL market_resolved 721 721 0 0 FULL new_market 2,527 2,527 0 0 FULL price_change 98,852,864 98,849,472 3,392 172 FULL tick_size_change 3,148 3,148 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,126,873 2,329 78ms 110ms 884ms 36.0s 0 transport_latency_assumed best_bid_ask h 10,130,938 106,305 18ms 27ms 530ms 1.4min 0 transport_latency_assumed best_bid_ask i 10,133,651 48,315 22ms 33ms 275ms 6.8s 0 transport_latency_assumed best_bid_ask k 10,133,307 406,506 13ms 23ms 286ms 1.0min 0 transport_latency_assumed best_bid_ask m 10,131,701 9,571,173 5ms 10ms 136ms 6.3s 0 transport_latency_assumed book g 131,776 26,950 92ms 3.5h 23.3d 105.3d 0 book_staleness book h 131,404 28,009 25ms 3.6h 20.4d 105.4d 0 book_staleness book i 126,532 21,633 30ms 58.2min 15.5d 123.9d 0 book_staleness book k 124,178 25,857 19ms 23.8min 11.2d 123.9d 0 book_staleness book m 127,986 114,100 8ms 1.9h 8.0d 105.2d 0 book_staleness last_trade_price g 49,825 144 83ms 700ms 9.1s 29.0s 0 transport_latency_assumed last_trade_price h 50,650 1,153 19ms 89ms 1.3s 24.2s 0 transport_latency_assumed last_trade_price i 50,750 435 26ms 122ms 1.9s 4.8s 0 transport_latency_assumed last_trade_price k 50,675 4,138 15ms 41ms 480ms 45.0s 0 transport_latency_assumed last_trade_price m 50,636 44,956 6ms 21ms 223ms 3.6s 0 transport_latency_assumed market_resolved g 675 not meas. 81ms 386ms 55.6s 55.6s 0 transport_latency_assumed market_resolved h 675 4 20ms 96ms 54.9s 55.0s 0 transport_latency_assumed market_resolved i 675 1 23ms 252ms 51.1s 51.1s 0 transport_latency_assumed market_resolved k 675 67 14ms 40ms 52.6s 52.7s 0 transport_latency_assumed market_resolved m 675 649 5ms 190ms 48.7s 57.0s 0 transport_latency_assumed new_market g 1,522 202 463ms 11.0s 14.9s 1.4min 0 transport_latency_assumed new_market h 1,522 461 209ms 10.5s 15.6s 1.7min 0 transport_latency_assumed new_market i 1,522 438 169ms 11.0s 21.2s 37.9s 0 transport_latency_assumed new_market k 1,522 314 214ms 10.9s 37.0s 1.7min 0 transport_latency_assumed new_market m 1,522 1,112 104ms 11.4s 19.0s 1.6min 0 transport_latency_assumed price_change g 98,406,098 49,586 79ms 176ms 2.8s 36.0s 0 transport_latency_assumed price_change h 98,755,515 1,366,216 18ms 33ms 729ms 1.5min 0 transport_latency_assumed price_change i 98,806,588 564,700 22ms 45ms 618ms 32.0s 0 transport_latency_assumed price_change k 98,789,019 5,266,671 14ms 25ms 355ms 1.1min 0 transport_latency_assumed price_change m 98,752,317 91,602,299 5ms 13ms 186ms 6.3s 0 transport_latency_assumed tick_size_change g 3,148 not meas. 79ms 100ms 772ms 1.0s 0 transport_latency_assumed tick_size_change h 3,148 20 18ms 28ms 580ms 8.8s 0 transport_latency_assumed tick_size_change i 3,148 8 23ms 40ms 194ms 373ms 0 transport_latency_assumed tick_size_change k 3,148 131 13ms 23ms 227ms 1.1s 0 transport_latency_assumed tick_size_change m 3,148 2,989 5ms 10ms 61ms 193ms 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-30/19/2026-09-30T19.parquet sha256sum 2026-09-30T19.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.