Hour audit: 2026-10-03T07
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-03T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T07:00:00.000003901+00:00 · last event 2026-10-03T07:59:59.999933495+00:00
VOLUME 100,120,816 rows · 1,019,612,196 bytes (972.38 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 100,050,373 · m: 100,013,622 · i: 100,010,023 · h: 99,993,633 · g: 99,873,231 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,711,138 (3.71%) · m: 95,118,023 (95.00%) · i: 396,805 (0.40%) · h: 862,177 (0.86%) · g: 32,673 (0.03%) (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 100,120,816 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 53a07b90f7baa35f705b3de75ddd48d5ce801a4825174adbc0e0a29973ba3978
the corpus checksum ledger names this file with the same digest
joined 100,122,627 to merged 100,120,816, minus 1,811 (minus 0.0018%)
boundary drops 1,811 · 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-03T09:43:00Z 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,562,520 111,302,200 0-36 e486752d86892e3cb2a803f350c93b0975630ccc16dc2883b5f3d4fac0552c3e book 126,836 13,326,993 37-37 bc1448f56b598930cdc0840621dcb822529093ef2019688e4f2cfef2cfa0110e last_trade_price 42,766 2,485,938 38-38 5948401e0f7c81016424622fb0b07d1a4fb46e7201c20242e8273cb15b53f8a4 market_resolved 487 80,498 39-39 865cf83b243e576ed763734d0a46718a62aa8750144bb4818aed3e0b5647fe8a new_market 1,393 131,005 40-40 918be4496e063f0481fda01ac690859c1157d7cf381816941df77b7b327029fd price_change 90,384,674 891,062,648 41-385 fe037961da7156602ee58d489550251e0e986ad0afcb532a3ad4633c4e1ad48c tick_size_change 2,140 79,407 386-386 430a5567124d465bde9d2c14b3dda4e9f20d529f61d36a4cd11105d775395f6a EVENT MIX count share price_change 90,384,674 90.28% best_bid_ask 9,562,520 9.55% book 126,836 0.13% last_trade_price 42,766 0.04% tick_size_change 2,140 <0.01% new_market 1,393 <0.01% market_resolved 487 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,562,745 9,562,520 225 146 FULL book 126,842 126,836 6 16,483 FULL last_trade_price 42,768 42,766 2 0 FULL market_resolved 487 487 0 0 FULL new_market 1,393 1,393 0 0 FULL price_change 90,386,252 90,384,674 1,578 245 FULL tick_size_change 2,140 2,140 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,558,196 816 76ms 95ms 455ms 29.1s 0 transport_latency_assumed best_bid_ask h 9,560,266 72,486 17ms 23ms 220ms 51.3s 0 transport_latency_assumed best_bid_ask i 9,561,225 32,036 21ms 26ms 130ms 11.5s 0 transport_latency_assumed best_bid_ask k 9,561,243 331,300 12ms 20ms 183ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,561,276 9,125,882 4ms 9ms 66ms 9.0s 0 transport_latency_assumed book g 108,893 22,950 93ms 1.7h 24.0d 107.9d 0 book_staleness book h 93,668 8,496 21ms 231ms 1.1d 107.9d 0 book_staleness book i 90,272 3,842 23ms 90ms 9.9h 107.8d 0 book_staleness book k 90,460 8,391 16ms 62ms 10.2h 107.8d 0 book_staleness book m 89,992 83,157 6ms 31ms 4.9h 104.1d 0 book_staleness last_trade_price g 42,038 11 82ms 325ms 9.5s 29.1s 0 transport_latency_assumed last_trade_price h 42,543 661 19ms 38ms 403ms 41.0s 0 transport_latency_assumed last_trade_price i 42,664 278 23ms 46ms 315ms 3.7s 0 transport_latency_assumed last_trade_price k 42,642 2,441 14ms 28ms 310ms 23.6s 0 transport_latency_assumed last_trade_price m 42,558 39,375 6ms 15ms 173ms 1.2s 0 transport_latency_assumed market_resolved g 480 not meas. 119ms 36.7s 52.5s 52.6s 0 transport_latency_assumed market_resolved h 480 3 22ms 45.9s 53.2s 53.3s 0 transport_latency_assumed market_resolved i 480 2 34ms 39.9s 54.3s 54.3s 0 transport_latency_assumed market_resolved k 480 9 18ms 48.0s 55.3s 55.3s 0 transport_latency_assumed market_resolved m 480 473 5ms 34.3s 49.0s 49.1s 0 transport_latency_assumed new_market g 854 114 406ms 33.2s 39.6s 1.6min 0 transport_latency_assumed new_market h 854 215 176ms 10.0s 24.6s 1.8min 0 transport_latency_assumed new_market i 854 189 139ms 21.5s 39.6s 1.9min 0 transport_latency_assumed new_market k 854 281 302ms 35.0s 42.0s 1.6min 0 transport_latency_assumed new_market m 854 594 71ms 18.3s 40.1s 1.5min 0 transport_latency_assumed price_change g 90,160,630 8,782 77ms 102ms 1.3s 29.2s 0 transport_latency_assumed price_change h 90,293,682 780,296 17ms 25ms 311ms 52.3s 0 transport_latency_assumed price_change i 90,312,388 360,450 21ms 29ms 251ms 13.0s 0 transport_latency_assumed price_change k 90,352,554 3,368,666 13ms 22ms 234ms 1.1min 0 transport_latency_assumed price_change m 90,316,322 85,866,480 5ms 10ms 78ms 9.1s 0 transport_latency_assumed tick_size_change g 2,140 not meas. 77ms 91ms 156ms 340ms 0 transport_latency_assumed tick_size_change h 2,140 20 17ms 22ms 91ms 3.7s 0 transport_latency_assumed tick_size_change i 2,140 8 21ms 27ms 62ms 305ms 0 transport_latency_assumed tick_size_change k 2,140 50 13ms 21ms 55ms 540ms 0 transport_latency_assumed tick_size_change m 2,140 2,062 4ms 9ms 48ms 245ms 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-03/07/2026-10-03T07.parquet sha256sum 2026-10-03T07.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.