Hour audit: 2026-10-01T20
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-10-01T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T20:00:00.000044178+00:00 · last event 2026-10-01T20:59:59.999973774+00:00
VOLUME 112,506,205 rows · 1,216,430,160 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 111,693,593 · k: 111,671,057 · i: 111,659,137 · h: 111,649,442 · g: 106,123,149 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 108,245,906 (96.21%) · k: 2,827,870 (2.51%) · i: 355,143 (0.32%) · h: 601,895 (0.53%) · g: 475,391 (0.42%) (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,506,205 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 175286b03848f73c59fbaf163ab973cd52afdb6d1e229dd59d4bd4f1d515f494
the corpus checksum ledger names this file with the same digest
joined 112,515,086 to merged 112,506,205, minus 8,881 (minus 0.0079%)
boundary drops 8,881 · 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-10-01T23:08:29Z 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,052,588 116,241,000 0-38 7638932f34aa6fd83303e21b344050fcf7a83830cdd01b9a94133e1ea85574eb book 1,234,232 87,450,677 39-43 0d6b981256a360b04ee11417232e3fce60fe92c3ab0a0a78771bc94e9d34e9bf last_trade_price 65,972 3,712,433 44-44 750ae87969779f662f39fbd2bfbbb462adc7b9043176e71f47a8edf1429fbcd9 market_resolved 1,088 163,717 45-45 a010d36f2ceca163670ca5c354dda31784114326e734653fd52a1ec152e279d6 new_market 1,241 144,891 46-46 dae7aa5e2364a8253ba019b489ce224a50287816c7764b7a4bdec073dad36d84 price_change 101,147,208 1,007,293,443 47-432 586b0407a29d1ae44220c697de43a79ff9aab90d4776c50dd950fde46b2be324 tick_size_change 3,876 141,274 433-433 08f1736a76f93ab731028d89436469e26d97bb2e58ae3a60043eff4518eb4cfb EVENT MIX count share price_change 101,147,208 89.90% best_bid_ask 10,052,588 8.94% book 1,234,232 1.10% last_trade_price 65,972 0.06% tick_size_change 3,876 <0.01% new_market 1,241 <0.01% market_resolved 1,088 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,053,000 10,052,588 412 615 FULL book 1,238,358 1,234,232 4,126 214,195 FULL last_trade_price 65,977 65,972 5 113 FULL market_resolved 1,088 1,088 0 8 FULL new_market 1,241 1,241 0 0 FULL price_change 101,151,546 101,147,208 4,338 435 FULL tick_size_change 3,876 3,876 0 35 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,504,642 3,412 76ms 92ms 246ms 11.2s 0 transport_latency_assumed best_bid_ask h 10,049,665 40,226 20ms 33ms 237ms 1.3min 0 transport_latency_assumed best_bid_ask i 10,050,370 15,237 38ms 52ms 115ms 9.1s 0 transport_latency_assumed best_bid_ask k 10,049,347 236,427 13ms 23ms 131ms 1.8min 0 transport_latency_assumed best_bid_ask m 10,051,150 9,757,286 5ms 9ms 57ms 5.4s 0 transport_latency_assumed book g 808,959 429,041 33.0min 3.2d 40.3d 124.9d 0 book_staleness book h 419,514 148,981 3.8min 2.4d 40.3d 124.9d 0 book_staleness book i 429,874 177,318 4.1min 2.5d 40.3d 124.9d 0 book_staleness book k 452,661 167,363 4.9min 2.6d 40.3d 124.9d 0 book_staleness book m 454,827 311,529 5.1min 2.6d 40.3d 124.9d 0 book_staleness last_trade_price g 62,007 34 77ms 127ms 503ms 9.7s 0 transport_latency_assumed last_trade_price h 65,908 240 23ms 36ms 419ms 58.7s 0 transport_latency_assumed last_trade_price i 65,910 139 39ms 54ms 273ms 5.6s 0 transport_latency_assumed last_trade_price k 65,918 1,620 15ms 25ms 183ms 41.7s 0 transport_latency_assumed last_trade_price m 65,943 63,939 6ms 10ms 78ms 2.0s 0 transport_latency_assumed market_resolved g 1,024 41 78ms 16.1s 5.2min 6.1min 0 transport_latency_assumed market_resolved h 1,021 6 22ms 60ms 51.9s 56.1s 0 transport_latency_assumed market_resolved i 1,021 90 42ms 119ms 41.5s 52.3s 0 transport_latency_assumed market_resolved k 1,021 40 14ms 40ms 53.4s 56.4s 0 transport_latency_assumed market_resolved m 1,021 911 5ms 30ms 41.5s 53.1s 0 transport_latency_assumed new_market g 958 129 15.5s 49.8s 4.5min 5.9min 0 transport_latency_assumed new_market h 958 88 14.8s 26.0s 55.9s 22.7d 0 transport_latency_assumed new_market i 958 165 13.3s 24.2s 54.1s 22.7d 0 transport_latency_assumed new_market k 958 99 13.7s 24.5s 56.0s 22.7d 0 transport_latency_assumed new_market m 958 760 14.8s 25.3s 52.5s 1.9min 0 transport_latency_assumed price_change g 95,741,823 42,734 76ms 94ms 400ms 13.9s 0 transport_latency_assumed price_change h 101,108,500 412,342 21ms 34ms 323ms 1.4min 0 transport_latency_assumed price_change i 101,107,128 162,194 38ms 53ms 185ms 9.5s 0 transport_latency_assumed price_change k 101,097,276 2,422,242 14ms 24ms 180ms 1.8min 0 transport_latency_assumed price_change m 101,115,818 98,107,696 5ms 9ms 78ms 5.4s 0 transport_latency_assumed tick_size_change g 3,736 not meas. 76ms 91ms 303ms 819ms 0 transport_latency_assumed tick_size_change h 3,876 12 21ms 34ms 250ms 5.3s 0 transport_latency_assumed tick_size_change i 3,876 not meas. 34ms 51ms 121ms 315ms 0 transport_latency_assumed tick_size_change k 3,876 79 13ms 22ms 122ms 993ms 0 transport_latency_assumed tick_size_change m 3,876 3,785 5ms 8ms 22ms 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-10-01/20/2026-10-01T20.parquet sha256sum 2026-10-01T20.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.