Hour audit: 2026-09-06T20
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-06T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T20:00:00.000046161+00:00 · last event 2026-09-06T20:59:59.999996681+00:00
VOLUME 123,449,093 rows · 1,350,356,260 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,715,704 · e: 120,680,192 · f: 116,488,690 · g: 116,117,638 · c: 87,712,543 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 34,620,457 (28.04%) · e: 3,743,495 (3.03%) · f: 1,455,329 (1.18%) · g: 253,012 (0.20%) · c: 83,376,800 (67.54%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4d1068ff6105e5edcb6c553cebef795fadb970bfa8ff1d288cb888fec07c0c38
the corpus checksum ledger names this file with the same digest
joined 123,468,898 to merged 123,449,093, minus 19,805 (minus 0.0160%)
boundary drops 19,805 · 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-07T01:50:17Z as cefgh
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 12,469,144 141,766,023 0-47 d43870f9b1cfaf63038c25ec5d50fcf487412e345297b69a71a2231b000c1d9e book 2,725,238 97,121,713 48-58 bf4342abb79dc949c894f5daadd32aee15117ea0b4c5947888f9e860fe8d798f last_trade_price 61,200 3,488,342 59-59 009c4cc0f715b67a174534c2ef5799b0f6d5adfdd873e47a8c3375667f9579f3 market_resolved 6,008 609,991 60-60 797a1a849da5ecf34a2a4e9aeea5274ca385c33c87b9c9bb35d4db326a1d27ff new_market 10,431 761,735 61-61 e52dde6fa282ba520217e2e744036a63c94bb4e4b24091f846a9bb2c30c8d6a7 price_change 108,169,748 1,104,935,281 62-474 7c9c6cccd62d64fdf8010d055424bb7ab16d32c22b28c633c4e6bd0d6174d5f0 tick_size_change 7,324 268,938 475-475 9390a5f5a4a69e8cdbf0657dc36c310b56c6c67c12445b3154d049f4b6193ad0 EVENT MIX count share price_change 108,169,748 87.62% best_bid_ask 12,469,144 10.10% book 2,725,238 2.21% last_trade_price 61,200 0.05% new_market 10,431 <0.01% tick_size_change 7,324 <0.01% market_resolved 6,008 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,471,009 12,469,144 1,865 4,988 FULL book 2,729,556 2,725,238 4,318 173,200 FULL last_trade_price 61,204 61,200 4 558 FULL market_resolved 6,008 6,008 0 154 FULL new_market 10,435 10,431 4 128 FULL price_change 108,183,362 108,169,748 13,614 3,555 FULL tick_size_change 7,324 7,324 0 789 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,808,485 8,381,869 5ms 13ms 223ms 9.5s 0 transport_latency_assumed best_bid_ask e 12,466,891 393,073 39ms 68ms 429ms 17.4s 0 transport_latency_assumed best_bid_ask f 11,975,834 137,473 46ms 79ms 440ms 18.7s 0 transport_latency_assumed best_bid_ask g 11,947,679 11,537 85ms 200ms 1.1s 35.7s 0 transport_latency_assumed best_bid_ask h 12,467,531 3,545,192 18ms 47ms 936ms 1.2min 0 transport_latency_assumed book c 2,566,152 2,521,710 7.7min 1.1d 35.4d 99.9d 0 book_staleness book e 133,814 7,682 42ms 956ms 13.0s 42.1d 0 book_staleness book f 483,831 23,413 1.4min 14.2h 30.9d 99.9d 0 book_staleness book g 487,834 131,322 1.5min 14.5h 32.1d 99.9d 0 book_staleness book h 135,560 41,111 23ms 429ms 2.7min 81.4d 0 book_staleness last_trade_price c 41,080 38,990 10ms 45ms 320ms 5.6s 0 transport_latency_assumed last_trade_price e 61,121 1,927 45ms 280ms 11.3s 17.4s 0 transport_latency_assumed last_trade_price f 59,316 831 53ms 280ms 9.0s 18.8s 0 transport_latency_assumed last_trade_price g 58,279 137 96ms 652ms 15.6s 35.8s 0 transport_latency_assumed last_trade_price h 61,107 19,315 24ms 122ms 1.9s 53.1s 0 transport_latency_assumed market_resolved c 5,031 4,900 43ms 9.6min 13.9min 14.2min 0 transport_latency_assumed market_resolved e 3,608 120 42ms 171ms 589ms 1.0min 0 transport_latency_assumed market_resolved f 3,570 58 49ms 193ms 616ms 2.5min 0 transport_latency_assumed market_resolved g 3,576 14 91ms 381ms 1.1s 2.4min 0 transport_latency_assumed market_resolved h 3,608 916 28ms 87ms 896ms 28.9s 0 transport_latency_assumed new_market c 9,459 6,775 3.3min 9.4min 10.4min 4.2h 0 transport_latency_assumed new_market e 4,436 902 230ms 2.0min 6.5min 28.9min 0 transport_latency_assumed new_market f 4,347 853 215ms 2.8min 6.5min 1.6h 0 transport_latency_assumed new_market g 4,410 690 362ms 3.2min 6.1min 7.4min 0 transport_latency_assumed new_market h 4,436 1,211 189ms 42.1s 5.0min 1.5h 0 transport_latency_assumed price_change c 76,278,060 72,418,431 5ms 15ms 244ms 10.3s 0 transport_latency_assumed price_change e 108,002,998 3,339,449 39ms 84ms 521ms 17.4s 0 transport_latency_assumed price_change f 103,954,628 1,292,610 46ms 91ms 513ms 18.9s 0 transport_latency_assumed price_change g 103,608,692 109,304 85ms 233ms 1.7s 35.8s 0 transport_latency_assumed price_change h 108,036,138 31,009,954 18ms 52ms 975ms 1.2min 0 transport_latency_assumed tick_size_change c 4,276 4,125 5ms 9ms 49ms 211ms 0 transport_latency_assumed tick_size_change e 7,324 342 38ms 60ms 326ms 611ms 0 transport_latency_assumed tick_size_change f 7,164 91 46ms 83ms 364ms 855ms 0 transport_latency_assumed tick_size_change g 7,168 8 84ms 288ms 710ms 1.3s 0 transport_latency_assumed tick_size_change h 7,324 2,758 18ms 48ms 744ms 15.7s 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-06/20/2026-09-06T20.parquet sha256sum 2026-09-06T20.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.