Hour audit: 2026-10-01T05
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-01T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T05:00:00.000018271+00:00 · last event 2026-10-01T05:59:59.999965004+00:00
VOLUME 103,236,204 rows · 1,105,391,135 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 96,162,138 · m: 93,682,977 · i: 91,890,330 · k: 90,414,070 · g: 89,347,335 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,204,061 (4.07%) · m: 72,507,179 (70.23%) · i: 1,631,071 (1.58%) · k: 24,826,052 (24.05%) · g: 67,841 (0.07%) (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 103,236,204 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 033850a781dc9a48d7def4ad9d83351e4a65b0e3b06a3f9b90d0fc1451f4c6d5
the corpus checksum ledger names this file with the same digest
joined 103,237,968 to merged 103,236,204, minus 1,764 (minus 0.0017%)
boundary drops 1,764 · 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-01T08:05:27Z 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,742,708 125,711,559 0-40 cfb767b2a4e2f1e9aca325f7806ff550e937713534498888e6d605137315eadb book 619,320 60,610,212 41-43 16b27c4901a3f0217a204cf8408230ac2a59eca7afb40a252d9a6ce43de35e81 last_trade_price 45,844 2,668,555 44-44 01fc93a91e601c4a01411e894ed0b071d2fb0ca01c68606196abdef187eef005 market_resolved 1,158 173,948 45-45 68fb065eeeb3588088f17e2c2e94921c38dda863fc2fb075b0ff23f6abe64981 new_market 775 77,160 46-46 2ec4546afc2a5914f34035b1f1bcfb7c7078910e578e5044a4cf46cbb130efc5 price_change 91,823,483 914,865,919 47-397 9d13e11bdf86180395903154338a8db02d926497d7847e593f3b56e728e64356 tick_size_change 2,916 105,937 398-398 56d53ce533215e58ce4c7804a53c15fb766944d627d4713015392b374453ba5e EVENT MIX count share price_change 91,823,483 88.95% best_bid_ask 10,742,708 10.41% book 619,320 0.60% last_trade_price 45,844 0.04% tick_size_change 2,916 <0.01% market_resolved 1,158 <0.01% new_market 775 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,742,928 10,742,708 220 242 FULL book 619,344 619,320 24 228,083 FULL last_trade_price 45,844 45,844 0 8 FULL market_resolved 1,158 1,158 0 0 FULL new_market 775 775 0 0 FULL price_change 91,825,003 91,823,483 1,520 60,716 FULL tick_size_change 2,916 2,916 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,741,196 723 78ms 94ms 212ms 18.3s 0 transport_latency_assumed best_bid_ask h 10,742,336 161,744 17ms 26ms 108ms 45.4s 0 transport_latency_assumed best_bid_ask i 10,742,320 69,739 20ms 50ms 105ms 5.7s 0 transport_latency_assumed best_bid_ask k 10,719,879 2,216,645 10ms 19ms 125ms 13.7s 0 transport_latency_assumed best_bid_ask m 10,742,276 8,293,857 5ms 19ms 75ms 1.8s 0 transport_latency_assumed book g 100,392 8,267 83ms 530ms 2.6d 105.8d 0 book_staleness book h 95,332 4,330 21ms 49ms 8.3h 105.6d 0 book_staleness book i 93,154 1,176 21ms 58ms 2.0s 105.7d 0 book_staleness book k 610,202 519,768 10.0min 2.6d 39.7d 124.3d 0 book_staleness book m 103,901 85,779 7ms 15.6s 20.8d 61.9d 0 book_staleness last_trade_price g 45,740 6 81ms 160ms 912ms 18.3s 0 transport_latency_assumed last_trade_price h 45,840 743 18ms 35ms 211ms 19.7s 0 transport_latency_assumed last_trade_price i 45,838 260 21ms 54ms 258ms 1.7s 0 transport_latency_assumed last_trade_price k 45,765 8,861 10ms 21ms 161ms 8.0s 0 transport_latency_assumed last_trade_price m 45,837 35,974 6ms 20ms 117ms 938ms 0 transport_latency_assumed market_resolved g 1,073 29 80ms 222ms 51.0s 54.3s 0 transport_latency_assumed market_resolved h 1,073 16 19ms 72ms 47.1s 47.2s 0 transport_latency_assumed market_resolved i 1,073 15 22ms 22.8s 51.6s 55.1s 0 transport_latency_assumed market_resolved k 1,073 217 11ms 85ms 48.0s 48.1s 0 transport_latency_assumed market_resolved m 1,073 881 6ms 22.3s 51.2s 55.3s 0 transport_latency_assumed new_market g 501 88 179ms 15.6s 1.4min 1.6min 0 transport_latency_assumed new_market h 501 92 116ms 29.0s 1.3min 1.6min 0 transport_latency_assumed new_market i 501 152 79ms 37.9s 1.4min 1.7min 0 transport_latency_assumed new_market k 501 103 107ms 33.4s 1.3min 1.6min 0 transport_latency_assumed new_market m 501 340 46ms 13.9s 1.4min 1.6min 0 transport_latency_assumed price_change g 78,455,517 58,728 78ms 101ms 425ms 18.3s 0 transport_latency_assumed price_change h 85,274,140 4,037,108 17ms 28ms 163ms 45.6s 0 transport_latency_assumed price_change i 81,004,528 1,559,721 21ms 53ms 154ms 5.8s 0 transport_latency_assumed price_change k 79,033,734 22,079,835 10ms 21ms 142ms 13.7s 0 transport_latency_assumed price_change m 82,786,473 64,088,091 5ms 20ms 94ms 2.6s 0 transport_latency_assumed tick_size_change g 2,916 not meas. 78ms 95ms 124ms 219ms 0 transport_latency_assumed tick_size_change h 2,916 28 18ms 27ms 53ms 169ms 0 transport_latency_assumed tick_size_change i 2,916 8 20ms 50ms 81ms 129ms 0 transport_latency_assumed tick_size_change k 2,916 623 10ms 16ms 40ms 109ms 0 transport_latency_assumed tick_size_change m 2,916 2,257 5ms 22ms 75ms 155ms 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/05/2026-10-01T05.parquet sha256sum 2026-10-01T05.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.