Hour audit: 2026-09-30T01
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-30T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T01:00:00.000353369+00:00 · last event 2026-09-30T01:59:59.999877314+00:00
VOLUME 110,371,132 rows · 1,131,296,353 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 110,158,687 · i: 110,029,295 · h: 110,018,924 · m: 109,959,210 · g: 109,931,303 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 4,378,085 (3.97%) · i: 423,459 (0.38%) · h: 1,141,116 (1.03%) · m: 104,414,244 (94.60%) · g: 14,228 (0.01%) (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 110,371,132 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c2077da731fb673589b3c390a6169ab86a340852851fb2d953aa2249fbd5a7cc
the corpus checksum ledger names this file with the same digest
joined 110,373,234 to merged 110,371,132, minus 2,102 (minus 0.0019%)
boundary drops 2,102 · 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-30T14:11:10Z 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,342,432 118,455,875 0-39 d01c1067f06674f5683b58ea5c151508a6539c1bbfb77873600fb2a3912be7a6 book 296,239 29,432,917 40-41 92cf0e731d85b62b46e1da637647b73129c24888baf7fd9d06bdf0911d19b042 last_trade_price 57,474 3,159,199 42-42 d4fff24b8497e2218170fa6b2d4c9e3d2b885c9396b8a6e75abada0926624f3e market_resolved 485 78,613 43-43 832ba7ca33ea71b3567d794d7d6e6de803a37da3a318644596dde04fe0359381 new_market 622 72,236 44-44 60ac54668a75d725990e160e77b0a1721a6f8c141eb3e2e4c6455bd5821ce952 price_change 99,671,884 978,761,836 45-425 afa3e01e9d2969beff559679e8a09cc215fdb0e0405d94f95d9fe17936a7b5fb tick_size_change 1,996 74,210 426-426 dc96125ef142c44e5cfa0a49dce21be720f745bcd2c276787772ca1a2dc850d4 EVENT MIX count share price_change 99,671,884 90.31% best_bid_ask 10,342,432 9.37% book 296,239 0.27% last_trade_price 57,474 0.05% tick_size_change 1,996 <0.01% new_market 622 <0.01% market_resolved 485 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,342,694 10,342,432 262 114 FULL book 296,252 296,239 13 74,719 FULL last_trade_price 57,475 57,474 1 3 FULL market_resolved 485 485 0 0 FULL new_market 622 622 0 0 FULL price_change 99,673,710 99,671,884 1,826 131 FULL tick_size_change 1,996 1,996 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,335,526 430 80ms 104ms 311ms 15.9s 0 transport_latency_assumed best_bid_ask h 10,332,387 87,101 19ms 29ms 116ms 33.8s 0 transport_latency_assumed best_bid_ask i 10,336,004 31,806 25ms 36ms 124ms 5.6s 0 transport_latency_assumed best_bid_ask k 10,340,477 386,595 13ms 26ms 100ms 18.0s 0 transport_latency_assumed best_bid_ask m 10,332,621 9,836,500 4ms 10ms 58ms 7.5s 0 transport_latency_assumed book g 121,064 8,015 94ms 5.0s 1.9d 123.1d 0 book_staleness book h 191,748 75,960 44ms 18.3h 27.3d 123.1d 0 book_staleness book i 149,935 30,432 31ms 3.0h 21.3d 123.1d 0 book_staleness book k 159,713 44,068 21ms 6.4h 22.6d 104.6d 0 book_staleness book m 146,702 137,764 6ms 2.0h 10.5d 123.2d 0 book_staleness last_trade_price g 55,504 11 92ms 498ms 9.8s 15.9s 0 transport_latency_assumed last_trade_price h 56,660 592 20ms 62ms 283ms 6.6s 0 transport_latency_assumed last_trade_price i 56,897 177 28ms 86ms 483ms 2.0s 0 transport_latency_assumed last_trade_price k 57,138 2,378 15ms 46ms 230ms 1.3s 0 transport_latency_assumed last_trade_price m 57,032 54,316 5ms 12ms 91ms 2.1s 0 transport_latency_assumed market_resolved g 477 not meas. 85ms 244ms 56.5s 57.2s 0 transport_latency_assumed market_resolved h 477 8 19ms 68ms 56.6s 56.9s 0 transport_latency_assumed market_resolved i 477 32 25ms 83ms 40.0s 46.9s 0 transport_latency_assumed market_resolved k 477 18 15ms 60ms 47.0s 54.2s 0 transport_latency_assumed market_resolved m 477 427 5ms 20ms 57.2s 2.4min 0 transport_latency_assumed new_market g 456 30 212ms 12.5s 36.7s 1.5min 0 transport_latency_assumed new_market h 456 119 74ms 10.7s 36.2s 1.3min 0 transport_latency_assumed new_market i 456 52 85ms 12.2s 23.8s 1.4min 0 transport_latency_assumed new_market k 456 82 92ms 10.1s 37.1s 1.5min 0 transport_latency_assumed new_market m 456 339 37ms 10.8s 26.3s 1.6min 0 transport_latency_assumed price_change g 99,416,280 5,742 80ms 128ms 848ms 15.9s 0 transport_latency_assumed price_change h 99,435,200 977,320 19ms 35ms 159ms 35.7s 0 transport_latency_assumed price_change i 99,483,530 360,957 26ms 43ms 200ms 6.3s 0 transport_latency_assumed price_change k 99,598,430 3,944,875 13ms 29ms 124ms 18.5s 0 transport_latency_assumed price_change m 99,419,926 94,382,990 4ms 11ms 69ms 7.5s 0 transport_latency_assumed tick_size_change g 1,996 not meas. 80ms 95ms 245ms 444ms 0 transport_latency_assumed tick_size_change h 1,996 16 19ms 29ms 59ms 132ms 0 transport_latency_assumed tick_size_change i 1,996 3 25ms 35ms 72ms 170ms 0 transport_latency_assumed tick_size_change k 1,996 69 13ms 26ms 62ms 116ms 0 transport_latency_assumed tick_size_change m 1,996 1,908 4ms 9ms 33ms 91ms 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/01/2026-09-30T01.parquet sha256sum 2026-09-30T01.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.