Hour audit: 2026-09-21T09
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-21T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T09:00:00.000009142+00:00 · last event 2026-09-21T09:59:59.999925206+00:00
VOLUME 120,520,752 rows · 1,268,298,989 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 119,274,033 · e: 118,883,960 · f: 114,786,416 · c: 106,620,936 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,156,506 (15.07%) · e: 821,180 (0.68%) · f: 397,223 (0.33%) · c: 101,145,843 (83.92%) (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 120,520,752 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 9fde92d9332559ecfd872859e960a9e3d2fb684eb8da0e23aaf1f1d4b88702e0
the corpus checksum ledger names this file with the same digest
joined 120,522,052 to merged 120,520,752, minus 1,300 (minus 0.0011%)
boundary drops 1,300 · 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-21T11:27:51Z as cefh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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,225,500 115,317,614 0-39 a7d03f85a2b3c31de15e9b30e6c5d70c0f6440f8edbb6f5da2c3791eff115042 book 1,192,636 68,849,924 40-44 66b967495ff432270c3d2bbb56fe1bda0bb31b3828fba39140a76036b1d74467 last_trade_price 69,117 3,839,990 45-45 5218b29152da9324376035d419711633435c315990ffd9542fded09dda57e8f0 market_resolved 699 102,789 46-46 dc6ae2b1f44e48ed10b4282df27e97019eda902151b17f1d4fec366a715d3e18 new_market 210 28,080 47-47 0c921a4f39c768e7130635daadfc8591083213ce798e31a76bc75ed46fc8adcf price_change 109,029,878 1,078,690,980 48-463 2c6225b39ab9634411c7f18e8d403b3c300382d6bffcfb0f3c26db7757722a29 tick_size_change 2,712 99,065 464-464 de7c101a226d83bfe02918e6bb66ad93af61be587ca1fe87830b805154e04bf7 EVENT MIX count share price_change 109,029,878 90.47% best_bid_ask 10,225,500 8.48% book 1,192,636 0.99% last_trade_price 69,117 0.06% tick_size_change 2,712 <0.01% market_resolved 699 <0.01% new_market 210 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,225,600 10,225,500 100 64,211 PARTIAL book 1,192,924 1,192,636 288 149,715 PARTIAL last_trade_price 69,117 69,117 0 3,039 PARTIAL market_resolved 699 699 0 627 PARTIAL new_market 210 210 0 188 PARTIAL price_change 109,030,790 109,029,878 912 114,074 PARTIAL tick_size_change 2,712 2,712 0 678 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,066,814 8,636,030 5ms 13ms 75ms 1.3s 0 transport_latency_assumed best_bid_ask e 10,218,522 62,524 41ms 53ms 178ms 17.8s 0 transport_latency_assumed best_bid_ask f 9,827,269 16,344 48ms 62ms 217ms 15.8s 0 transport_latency_assumed best_bid_ask h 10,224,631 1,510,602 19ms 29ms 87ms 3.9s 0 transport_latency_assumed book c 1,063,511 994,368 7.1min 2.7d 43.8d 114.5d 0 book_staleness book e 164,485 18,923 54ms 7.3min 14.0d 114.5d 0 book_staleness book f 451,948 142,953 2.1min 1.8d 40.6d 114.5d 0 book_staleness book h 166,613 36,392 24ms 4.4min 14.0d 114.5d 0 book_staleness last_trade_price c 61,836 57,926 6ms 21ms 179ms 1.0s 0 transport_latency_assumed last_trade_price e 67,134 424 46ms 1.2s 10.8s 17.8s 0 transport_latency_assumed last_trade_price f 65,474 181 53ms 1.2s 8.5s 15.8s 0 transport_latency_assumed last_trade_price h 69,088 10,586 20ms 52ms 230ms 1.4s 0 transport_latency_assumed market_resolved c 605 537 5ms 43.6s 5.2min 5.2min 0 transport_latency_assumed market_resolved e 627 63 43ms 22.5s 57.5s 1.0min 0 transport_latency_assumed market_resolved f 625 19 49ms 268ms 3.1min 4.8min 0 transport_latency_assumed market_resolved h 627 80 20ms 25.0s 1.0min 1.0min 0 transport_latency_assumed new_market c 188 76 7.5s 2.2min 2.9min 2.9min 0 transport_latency_assumed new_market e 188 54 6.0s 11.0s 20.3s 21.1s 0 transport_latency_assumed new_market f 188 35 5.2s 17.6s 1.1min 1.1min 0 transport_latency_assumed new_market h 188 45 7.2s 14.1s 19.7s 20.5s 0 transport_latency_assumed price_change c 96,425,706 91,454,726 5ms 15ms 85ms 1.6s 0 transport_latency_assumed price_change e 108,430,292 739,172 42ms 71ms 3.2s 17.9s 0 transport_latency_assumed price_change f 104,438,244 237,691 48ms 82ms 2.4s 15.9s 0 transport_latency_assumed price_change h 108,810,174 16,598,289 19ms 33ms 110ms 4.0s 0 transport_latency_assumed tick_size_change c 2,276 2,180 5ms 11ms 44ms 172ms 0 transport_latency_assumed tick_size_change e 2,712 20 41ms 47ms 112ms 644ms 0 transport_latency_assumed tick_size_change f 2,668 not meas. 47ms 54ms 113ms 272ms 0 transport_latency_assumed tick_size_change h 2,712 512 19ms 25ms 99ms 513ms 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-21/09/2026-09-21T09.parquet sha256sum 2026-09-21T09.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.