Hour audit: 2026-09-05T02
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-05T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T02:00:00.023838531+00:00 · last event 2026-09-05T02:59:59.999809133+00:00
VOLUME 112,042,068 rows · 1,151,415,595 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 110,837,510 · e: 110,831,691 · c: 110,807,546 · b: 96,616,315 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 25,003 (0.02%) · e: 110,829,942 (98.92%) · c: 31,328 (0.03%) · b: 1,155,795 (1.03%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,042,068 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 e6ce7af90fb294ea86f4dd90590e8a84b5573a1bd22724287a382498dbd0b129
the corpus checksum ledger names this file with the same digest
joined 112,053,973 to merged 112,042,068, minus 11,905 (minus 0.0106%)
boundary drops 11,905 · 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-05T03:55:51Z as bceh
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 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 11,626,873 126,308,026 0-44 a6db0286dcd245a17eefe2ed282be799a3c22d7f2aa026a795efbd8bdcde13f9 book 1,295,090 73,990,167 45-49 b7e1c17b59d876a323199c635d515b199fdfa13859c80344241318a6cf8a6fb1 last_trade_price 44,430 2,532,734 50-50 94b688b6c2adcb7e4d2a49b1ecdb57a2b4c5cd096f2a7c100d6476ebc4e8946a market_resolved 3,804 565,680 51-51 51509bfe48a94123724e76d21d2e327aca07b6ce117eec520cf63e534fb29ada new_market 1,079 114,863 52-52 cd4dc9346da80444ee9e82a10e2c36e86d29502f7ffd5878cb10be0c455db8ce price_change 99,065,328 946,432,256 53-430 e5f806cedfeb6ffa303914d89355722f53b4d072409b3ce76e7265b3e3321c4f tick_size_change 5,464 198,741 431-431 87194b3829fbb6cc2a7a9dc797bfe544b4d510ac4eb3a9b8af2e0df0c75deb8a EVENT MIX count share price_change 99,065,328 88.42% best_bid_ask 11,626,873 10.38% book 1,295,090 1.16% last_trade_price 44,430 0.04% tick_size_change 5,464 <0.01% market_resolved 3,804 <0.01% new_market 1,079 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,627,811 11,626,873 938 2,696 FULL book 1,298,388 1,295,090 3,298 190,865 FULL last_trade_price 44,433 44,430 3 265 FULL market_resolved 3,804 3,804 0 712 FULL new_market 1,129 1,079 50 123 FULL price_change 99,072,944 99,065,328 7,616 2,473 FULL tick_size_change 5,464 5,464 0 147 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,010,707 66 56ms 67ms 165ms 2.2s 0 transport_latency_assumed best_bid_ask c 11,623,247 634 4ms 7ms 49ms 3.8s 0 transport_latency_assumed best_bid_ask e 11,625,077 11,624,932 41ms 47ms 177ms 2.4s 0 transport_latency_assumed best_bid_ask h 11,626,332 1,241 18ms 22ms 126ms 8.5s 0 transport_latency_assumed book b 1,252,014 1,153,832 2.7min 9.3h 33.6d 98.2d 0 book_staleness book c 118,303 26,597 6ms 7.6min 5.4d 79.7d 0 book_staleness book e 107,282 107,276 43ms 1.1min 9.5d 98.2d 0 book_staleness book h 98,702 7,385 20ms 132ms 4.9h 79.7d 0 book_staleness last_trade_price b 37,747 2 62ms 102ms 464ms 4.9s 0 transport_latency_assumed last_trade_price c 44,117 21 9ms 35ms 227ms 4.8s 0 transport_latency_assumed last_trade_price e 44,339 44,339 46ms 85ms 560ms 4.8s 0 transport_latency_assumed last_trade_price h 44,373 68 23ms 57ms 410ms 8.8s 0 transport_latency_assumed market_resolved b 3,307 657 87ms 6.5min 11.4min 11.9min 0 transport_latency_assumed market_resolved c 3,146 not meas. 4ms 6ms 43ms 43.1s 0 transport_latency_assumed market_resolved e 3,146 3,146 45ms 123ms 365ms 743ms 0 transport_latency_assumed market_resolved h 3,146 1 29ms 54ms 176ms 46.3s 0 transport_latency_assumed new_market b 822 222 234ms 5.3min 8.8min 1.1h 0 transport_latency_assumed new_market c 685 58 64ms 9.4s 28.0s 5.5min 0 transport_latency_assumed new_market e 685 685 133ms 10.3s 28.9s 3.3min 0 transport_latency_assumed new_market h 685 114 120ms 10.7s 24.9s 47.4s 0 transport_latency_assumed price_change b 85,306,842 1,016 56ms 68ms 181ms 2.2s 0 transport_latency_assumed price_change c 99,012,584 4,018 4ms 7ms 55ms 3.8s 0 transport_latency_assumed price_change e 99,045,698 99,044,100 41ms 52ms 196ms 2.4s 0 transport_latency_assumed price_change h 99,058,808 16,194 18ms 24ms 137ms 8.6s 0 transport_latency_assumed tick_size_change b 4,876 not meas. 56ms 67ms 124ms 234ms 0 transport_latency_assumed tick_size_change c 5,464 not meas. 4ms 6ms 25ms 116ms 0 transport_latency_assumed tick_size_change e 5,464 5,464 41ms 53ms 113ms 180ms 0 transport_latency_assumed tick_size_change h 5,464 not meas. 18ms 21ms 53ms 1.8s 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-05/02/2026-09-05T02.parquet sha256sum 2026-09-05T02.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.