Hour audit: 2026-09-20T15
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-20T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T15:00:00.000031471+00:00 · last event 2026-09-20T15:59:59.999994050+00:00
VOLUME 138,394,269 rows · 1,537,586,873 bytes (1.43 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 135,968,919 · e: 135,924,739 · g: 124,980,806 · f: 116,424,637 · c: 111,184,480 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 28,770,274 (20.79%) · e: 2,832,433 (2.05%) · g: 403,997 (0.29%) · f: 973,226 (0.70%) · c: 105,414,339 (76.17%) (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 138,394,269 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 959caa008f162477222db05eeb3bbc9fdaaf1c0c013be2b708feb3cd52633ada
the corpus checksum ledger names this file with the same digest
joined 138,400,089 to merged 138,394,269, minus 5,820 (minus 0.0042%)
boundary drops 5,820 · 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-20T17:40:46Z 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 14,575,470 168,388,825 0-55 2ff26d6d8e26ba0223c12131b4af01b1ab91e7051beb924a23573d4362c2d9fc book 2,524,060 113,645,772 56-65 e5c0ac5d8b24936176bed71ff95de19787ff28031e82271a871b75e4119a10c2 last_trade_price 77,418 4,560,675 66-66 82a71ec3283e6f1cd85a37607162f9ad115b56ffb6df1347a3a61d4d61eb1384 market_resolved 4,857 584,817 67-67 6a886e2e1a2e8485b4f2770df229353d1e0e92a276fece253db6aa4943f0eefa new_market 1,550 154,289 68-68 a5903875a9b3b05543607382ec9ae445e841579ab31029e1cbad8f66ce29a35c price_change 121,199,346 1,248,252,778 69-531 747f055e47afc9654fc2ef4fbf640dda90781b4bff262efacb6aff3149b2c75f tick_size_change 11,568 427,489 532-532 a13b1bfabd260d19a034f80c5db20cf8b2fbe38454f94ed1b52799719650c80e EVENT MIX count share price_change 121,199,346 87.58% best_bid_ask 14,575,470 10.53% book 2,524,060 1.82% last_trade_price 77,418 0.06% tick_size_change 11,568 <0.01% market_resolved 4,857 <0.01% new_market 1,550 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,575,718 14,575,470 248 5,364 FULL book 2,526,117 2,524,060 2,057 167,437 FULL last_trade_price 77,421 77,418 3 949 FULL market_resolved 4,857 4,857 0 661 FULL new_market 1,550 1,550 0 11 FULL price_change 121,202,858 121,199,346 3,512 2,457 FULL tick_size_change 11,568 11,568 0 1,004 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,696,872 11,133,605 6ms 14ms 83ms 1.8s 0 transport_latency_assumed best_bid_ask e 14,572,894 303,964 40ms 54ms 177ms 11.6s 0 transport_latency_assumed best_bid_ask f 12,337,362 47,685 47ms 63ms 190ms 11.3s 0 transport_latency_assumed best_bid_ask g 13,380,051 3,519 81ms 108ms 349ms 23.3s 0 transport_latency_assumed best_bid_ask h 14,574,642 3,086,697 18ms 37ms 118ms 6.5s 0 transport_latency_assumed book c 1,848,997 1,649,008 5.5min 2.0d 42.9d 113.7d 0 book_staleness book e 163,880 8,315 44ms 641ms 59.5min 95.2d 0 book_staleness book f 1,516,364 476,716 4.8min 2.0d 42.7d 113.7d 0 book_staleness book g 847,793 355,694 2.4min 2.0d 39.9d 113.7d 0 book_staleness book h 158,361 34,327 23ms 74ms 5.9s 95.2d 0 book_staleness last_trade_price c 61,695 58,060 6ms 21ms 151ms 1.8s 0 transport_latency_assumed last_trade_price e 77,045 1,712 43ms 226ms 3.3s 11.6s 0 transport_latency_assumed last_trade_price f 64,472 388 50ms 220ms 4.1s 11.3s 0 transport_latency_assumed last_trade_price g 69,894 103 89ms 514ms 11.7s 23.4s 0 transport_latency_assumed last_trade_price h 77,301 17,155 20ms 57ms 263ms 3.8s 0 transport_latency_assumed market_resolved c 3,510 3,387 7ms 4.6min 9.0min 9.4min 0 transport_latency_assumed market_resolved e 3,556 110 44ms 194ms 680ms 48.8s 0 transport_latency_assumed market_resolved f 3,536 348 87ms 5.2min 9.0min 9.3min 0 transport_latency_assumed market_resolved g 3,436 112 90ms 365ms 4.7min 5.4min 0 transport_latency_assumed market_resolved h 3,556 900 30ms 78ms 1.7s 49.5s 0 transport_latency_assumed new_market c 1,028 805 41ms 4.6min 2.7h 14.7h 0 transport_latency_assumed new_market e 1,001 153 121ms 40.8s 3.2min 1.7h 0 transport_latency_assumed new_market f 1,017 132 103ms 1.2min 2.5h 7.3h 0 transport_latency_assumed new_market g 1,001 115 186ms 1.1min 1.3h 5.3h 0 transport_latency_assumed new_market h 1,001 345 69ms 56.4s 3.3min 2.8h 0 transport_latency_assumed price_change c 97,562,854 92,560,380 6ms 16ms 94ms 2.1s 0 transport_latency_assumed price_change e 121,094,795 2,517,980 40ms 67ms 634ms 11.7s 0 transport_latency_assumed price_change f 102,492,262 447,924 47ms 76ms 556ms 11.4s 0 transport_latency_assumed price_change g 110,668,063 44,454 81ms 138ms 2.7s 23.5s 0 transport_latency_assumed price_change h 121,142,490 25,628,608 19ms 41ms 142ms 6.5s 0 transport_latency_assumed tick_size_change c 9,524 9,094 6ms 12ms 59ms 257ms 0 transport_latency_assumed tick_size_change e 11,568 199 40ms 48ms 119ms 7.9s 0 transport_latency_assumed tick_size_change f 9,624 33 47ms 58ms 177ms 861ms 0 transport_latency_assumed tick_size_change g 10,568 not meas. 80ms 96ms 273ms 1.1s 0 transport_latency_assumed tick_size_change h 11,568 2,242 19ms 31ms 96ms 327ms 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-20/15/2026-09-20T15.parquet sha256sum 2026-09-20T15.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.