Hour audit: 2026-10-01T12
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-01T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T12:00:00.000156589+00:00 · last event 2026-10-01T12:59:59.999903038+00:00
VOLUME 106,420,992 rows · 1,193,693,187 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 106,087,282 · i: 105,825,629 · h: 104,510,631 · m: 103,487,169 · g: 103,007,302 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 12,140,724 (11.41%) · i: 16,009,752 (15.04%) · h: 28,114,147 (26.42%) · m: 47,126,692 (44.28%) · g: 3,029,677 (2.85%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 c6e7e1eb7a90d96699498d257c540ff12f8feaa6876149061066ad51d8c6ffb3
the corpus checksum ledger names this file with the same digest
joined 106,423,660 to merged 106,420,992, minus 2,668 (minus 0.0025%)
boundary drops 2,668 · 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-01T15:08:02Z 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 9,109,453 114,560,920 0-34 52b8bf04e4fc2491b22dad73d831aed9857be234253d3ba69f8686fdd439b0a1 book 441,661 45,572,111 35-36 bb45807ccdb1318fd6e32a77ec99318bc22c278fb711a0d8350c9505f2fac529 last_trade_price 55,314 3,203,052 37-37 84604fddb1a4b54bea37bc46dbe7ed36088c26e1e7bdb91a57a8f90cd0876084 market_resolved 996 154,973 38-38 f6c64aece83e732ccdd48d73c8c699cd54870b9fac34247cd7d004bbd19ee85f new_market 1,286 126,167 39-39 79e900b6725f94743171092f6648d2cec339e51e60ddef74080d0f6ba7efdbed price_change 96,809,770 1,028,766,428 40-409 b8f3531163d3e17b14f1defc8b5ae842f214b67728724ce8efc86399a4dfe355 tick_size_change 2,512 95,057 410-410 b865d683a2180540a22c18feb21501d4cf097f2ef621d71483e7bb2264b855b6 EVENT MIX count share price_change 96,809,770 90.97% best_bid_ask 9,109,453 8.56% book 441,661 0.42% last_trade_price 55,314 0.05% tick_size_change 2,512 <0.01% new_market 1,286 <0.01% market_resolved 996 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,109,719 9,109,453 266 175 FULL book 441,661 441,661 0 145,906 FULL last_trade_price 55,314 55,314 0 0 FULL market_resolved 996 996 0 11 FULL new_market 1,286 1,286 0 0 FULL price_change 96,812,172 96,809,770 2,402 12,186 FULL tick_size_change 2,512 2,512 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,105,822 249,752 129ms 313ms 734ms 14.4s 0 transport_latency_assumed best_bid_ask h 9,107,043 2,410,070 57ms 226ms 627ms 22.1s 0 transport_latency_assumed best_bid_ask i 9,107,206 1,376,468 84ms 251ms 633ms 6.6s 0 transport_latency_assumed best_bid_ask k 9,106,878 953,548 88ms 272ms 653ms 10.1s 0 transport_latency_assumed best_bid_ask m 9,107,272 4,119,615 49ms 211ms 586ms 4.9s 0 transport_latency_assumed book g 203,408 71,185 465ms 23.2h 35.9d 124.6d 0 book_staleness book h 199,355 100,814 324ms 22.1h 35.9d 124.6d 0 book_staleness book i 171,729 54,696 216ms 14.5h 26.0d 124.6d 0 book_staleness book k 195,555 76,170 346ms 21.8h 31.9d 124.6d 0 book_staleness book m 219,874 138,796 610ms 1.1d 34.8d 124.6d 0 book_staleness last_trade_price g 55,085 1,783 139ms 413ms 1.2s 14.5s 0 transport_latency_assumed last_trade_price h 55,227 16,900 67ms 332ms 905ms 10.1s 0 transport_latency_assumed last_trade_price i 55,190 5,362 99ms 381ms 918ms 5.7s 0 transport_latency_assumed last_trade_price k 55,164 5,503 103ms 385ms 1.1s 9.8s 0 transport_latency_assumed last_trade_price m 55,222 25,766 44ms 264ms 822ms 4.9s 0 transport_latency_assumed market_resolved g 941 19 153ms 439ms 52.7s 52.7s 0 transport_latency_assumed market_resolved h 952 217 76ms 402ms 43.7s 50.8s 0 transport_latency_assumed market_resolved i 952 176 107ms 523ms 48.8s 52.6s 0 transport_latency_assumed market_resolved k 941 127 95ms 305ms 55.2s 55.3s 0 transport_latency_assumed market_resolved m 952 457 58ms 520ms 49.1s 52.4s 0 transport_latency_assumed new_market g 816 100 403ms 17.1s 30.5s 1.9min 0 transport_latency_assumed new_market h 816 231 98ms 17.2s 32.4s 1.6min 0 transport_latency_assumed new_market i 816 155 128ms 11.7s 40.2s 1.6min 0 transport_latency_assumed new_market k 816 210 236ms 26.4s 31.6s 1.6min 0 transport_latency_assumed new_market m 816 590 50ms 15.1s 30.6s 1.5min 0 transport_latency_assumed price_change g 93,638,718 2,706,774 134ms 340ms 818ms 14.5s 0 transport_latency_assumed price_change h 95,144,726 25,585,343 64ms 254ms 694ms 22.5s 0 transport_latency_assumed price_change i 96,487,224 14,572,468 87ms 273ms 694ms 6.8s 0 transport_latency_assumed price_change k 96,725,416 11,104,922 91ms 291ms 698ms 10.2s 0 transport_latency_assumed price_change m 94,100,521 42,840,263 50ms 226ms 632ms 4.9s 0 transport_latency_assumed tick_size_change g 2,512 64 152ms 279ms 520ms 1.0s 0 transport_latency_assumed tick_size_change h 2,512 572 77ms 205ms 421ms 882ms 0 transport_latency_assumed tick_size_change i 2,512 427 91ms 227ms 449ms 821ms 0 transport_latency_assumed tick_size_change k 2,512 244 102ms 241ms 428ms 571ms 0 transport_latency_assumed tick_size_change m 2,512 1,205 54ms 169ms 350ms 531ms 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/12/2026-10-01T12.parquet sha256sum 2026-10-01T12.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.