Hour audit: 2026-10-01T21
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-01T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T21:00:00.000067878+00:00 · last event 2026-10-01T21:59:59.999885840+00:00
VOLUME 106,095,787 rows · 1,114,318,524 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 105,304,508 · h: 105,302,834 · k: 105,300,508 · i: 105,234,893 · g: 105,183,644 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 102,331,636 (96.45%) · h: 701,783 (0.66%) · k: 2,345,321 (2.21%) · i: 459,838 (0.43%) · g: 257,209 (0.24%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,095,787 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 88f2a3d4e141a728a96fae1455b78672c9f1337ff19e1bd30e2afd529ddac583
the corpus checksum ledger names this file with the same digest
joined 106,105,017 to merged 106,095,787, minus 9,230 (minus 0.0087%)
boundary drops 9,230 · 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-02T00:07:44Z 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,068,158 105,612,906 0-34 24a249d43faa4b7e40102b0debd5cb17f7483fd7d0ee42e169c9fe6167ffa22c book 1,343,294 90,800,234 35-40 6ceffc215e9bdbb869d997d133f1b56d6f0ff4a7761e99013090853836fb44cb last_trade_price 46,544 2,693,102 41-41 d6f5595c9c75f7702f27418a412800ceed05d11a7293fa53d48e32966ea8609c market_resolved 577 90,048 42-42 ceca30612a71bd05ba90542c3be0ef114a43e28c2a95971670801a8ee3aca015 new_market 1,612 153,718 43-43 db45333774e4b186715168a19b4ef0c71964e393a37dabf58df35ce6477851a6 price_change 95,632,998 913,661,240 44-408 2de3d8a59417db0b003513ff5846ec003d3b907f7f184bd5dae54a3eadb05267 tick_size_change 2,604 95,635 409-409 52a9c63585f4b2dd448cb0cb10e5146b6ee704d2650ae828f2ca37483bf389a3 EVENT MIX count share price_change 95,632,998 90.14% best_bid_ask 9,068,158 8.55% book 1,343,294 1.27% last_trade_price 46,544 0.04% tick_size_change 2,604 <0.01% new_market 1,612 <0.01% market_resolved 577 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,068,452 9,068,158 294 193 FULL book 1,343,742 1,343,294 448 150,694 FULL last_trade_price 46,544 46,544 0 5 FULL market_resolved 577 577 0 1 FULL new_market 1,612 1,612 0 0 FULL price_change 95,641,486 95,632,998 8,488 97 FULL tick_size_change 2,604 2,604 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,063,251 3,982 76ms 92ms 271ms 9.2s 0 transport_latency_assumed best_bid_ask h 9,064,396 33,423 19ms 33ms 263ms 42.2s 0 transport_latency_assumed best_bid_ask i 9,064,579 16,428 38ms 49ms 123ms 9.1s 0 transport_latency_assumed best_bid_ask k 9,065,155 169,462 13ms 21ms 147ms 40.5s 0 transport_latency_assumed best_bid_ask m 9,066,038 8,844,863 5ms 8ms 57ms 6.4s 0 transport_latency_assumed book g 512,763 208,166 14.8min 2.9d 40.3d 125.0d 0 book_staleness book h 591,293 262,435 20.1min 3.2d 40.3d 125.0d 0 book_staleness book i 563,652 252,532 18.2min 3.0d 40.3d 125.0d 0 book_staleness book k 607,709 285,528 21.2min 3.2d 40.3d 125.0d 0 book_staleness book m 588,897 334,633 18.3min 2.9d 40.3d 125.0d 0 book_staleness last_trade_price g 46,492 32 77ms 153ms 631ms 9.0s 0 transport_latency_assumed last_trade_price h 46,503 270 21ms 36ms 488ms 37.1s 0 transport_latency_assumed last_trade_price i 46,518 134 41ms 52ms 267ms 3.1s 0 transport_latency_assumed last_trade_price k 46,519 1,084 14ms 24ms 188ms 7.4s 0 transport_latency_assumed last_trade_price m 46,525 45,024 6ms 10ms 115ms 1.2s 0 transport_latency_assumed market_resolved g 546 not meas. 81ms 343ms 53.3s 56.6s 0 transport_latency_assumed market_resolved h 546 2 24ms 74ms 55.3s 56.8s 0 transport_latency_assumed market_resolved i 546 27 44ms 239ms 46.2s 48.7s 0 transport_latency_assumed market_resolved k 545 37 14ms 40ms 55.4s 55.5s 0 transport_latency_assumed market_resolved m 546 511 5ms 36ms 46.2s 49.9s 0 transport_latency_assumed new_market g 994 209 224ms 15.0s 56.6s 1.3min 0 transport_latency_assumed new_market h 994 259 179ms 13.8s 54.6s 1.6min 0 transport_latency_assumed new_market i 994 163 147ms 18.9s 45.8s 1.6min 0 transport_latency_assumed new_market k 994 254 201ms 20.7s 50.4s 1.7min 0 transport_latency_assumed new_market m 994 727 61ms 18.7s 43.8s 1.6min 0 transport_latency_assumed price_change g 95,556,994 44,820 76ms 95ms 402ms 10.1s 0 transport_latency_assumed price_change h 95,596,498 405,370 20ms 33ms 308ms 44.3s 0 transport_latency_assumed price_change i 95,556,000 190,554 38ms 49ms 171ms 9.2s 0 transport_latency_assumed price_change k 95,576,982 1,888,910 14ms 22ms 163ms 40.7s 0 transport_latency_assumed price_change m 95,598,904 93,103,344 5ms 8ms 69ms 6.4s 0 transport_latency_assumed tick_size_change g 2,604 not meas. 76ms 91ms 318ms 611ms 0 transport_latency_assumed tick_size_change h 2,604 24 19ms 32ms 142ms 1.3s 0 transport_latency_assumed tick_size_change i 2,604 not meas. 38ms 49ms 72ms 410ms 0 transport_latency_assumed tick_size_change k 2,604 46 14ms 21ms 163ms 395ms 0 transport_latency_assumed tick_size_change m 2,604 2,534 5ms 8ms 26ms 35ms 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/21/2026-10-01T21.parquet sha256sum 2026-10-01T21.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.