Hour audit: 2026-09-05T22
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-05T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T22:00:00.067372578+00:00 · last event 2026-09-05T22:59:59.998832245+00:00
VOLUME 124,235,340 rows · 1,296,942,177 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 122,111,452 · e: 122,100,645 · h: 122,083,420 · g: 121,238,956 · c: 95,061,253 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 924,643 (0.74%) · e: 17,447 (0.01%) · h: 17,906 (0.01%) · g: 121,234,248 (97.58%) · c: 2,041,096 (1.64%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 124,235,340 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fa493bb728b6ebc8b066b92e86777308db6f4383392d522099554947bb063550
the corpus checksum ledger names this file with the same digest
joined 124,240,126 to merged 124,235,340, minus 4,786 (minus 0.0039%)
boundary drops 4,786 · 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-06T01:56:42Z 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,042,238 132,534,639 0-45 a17aa2a25e88efd5f525216fead7464e8610d7580ce2b4e8b9f0a0fb774c96b1 book 2,164,872 86,865,456 46-54 efd71a688d2152c7289c2f2a95b87bfaff84cd8f778aafc63db156c7050a381a last_trade_price 55,665 3,200,976 55-55 2544adb2cb135b9394298ee835d3806f037392e4762829df8c3d9b92c012c6c2 market_resolved 5,685 534,655 56-56 13d42442d9216b706f83f595941629d413bf5f9f1e4b88df425afdc1f139726b new_market 3,637 286,134 57-57 4eef08a2fd8d19a87d289107bcc434847d5b58aae2b5b904e226c9a811eec626 price_change 109,958,491 1,071,931,920 58-477 a4bb6ef2b978bc87abb3a9c8dc3a06a12031b110de06f90f3c521559abc52c1b tick_size_change 4,752 175,759 478-478 4ebbcb10f9186d90a32a603e102360e206108724f7acc9f6c5b80c2459314b65 EVENT MIX count share price_change 109,958,491 88.51% best_bid_ask 12,042,238 9.69% book 2,164,872 1.74% last_trade_price 55,665 0.04% market_resolved 5,685 <0.01% tick_size_change 4,752 <0.01% new_market 3,637 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,042,664 12,042,238 426 4,629 FULL book 2,164,942 2,164,872 70 183,986 FULL last_trade_price 55,667 55,665 2 648 FULL market_resolved 5,685 5,685 0 224 FULL new_market 3,637 3,637 0 2 FULL price_change 109,962,779 109,958,491 4,288 4,447 FULL tick_size_change 4,752 4,752 0 351 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,182,512 310 4ms 9ms 115ms 7.8s 0 transport_latency_assumed best_bid_ask e 12,040,292 588 40ms 49ms 248ms 17.5s 0 transport_latency_assumed best_bid_ask f 12,039,969 51,069 49ms 62ms 277ms 18.7s 0 transport_latency_assumed best_bid_ask g 11,989,847 11,989,421 82ms 142ms 1.2s 39.0s 0 transport_latency_assumed best_bid_ask h 12,040,294 850 17ms 36ms 315ms 1.3min 0 transport_latency_assumed book c 2,118,672 2,021,587 7.8min 11.9h 34.4d 99.0d 0 book_staleness book e 117,550 763 42ms 183ms 4.3s 80.4d 0 book_staleness book f 117,964 7,331 51ms 194ms 5.3s 80.4d 0 book_staleness book g 133,534 133,532 87ms 1.4min 8.8h 80.4d 0 book_staleness book h 118,383 1,659 21ms 94ms 12.3s 36.6d 0 book_staleness last_trade_price c 39,982 3 9ms 39ms 263ms 5.0s 0 transport_latency_assumed last_trade_price e 55,475 84 46ms 131ms 2.0s 17.7s 0 transport_latency_assumed last_trade_price f 55,385 2,823 55ms 134ms 1.4s 18.3s 0 transport_latency_assumed last_trade_price g 52,711 52,709 89ms 286ms 4.8s 37.5s 0 transport_latency_assumed last_trade_price h 55,490 46 23ms 73ms 685ms 51.8s 0 transport_latency_assumed market_resolved c 4,861 2,528 2.5min 14.2min 20.0min 20.8min 0 transport_latency_assumed market_resolved e 3,150 4 42ms 172ms 52.8s 1.0min 0 transport_latency_assumed market_resolved f 3,150 2 52ms 180ms 52.1s 1.0min 0 transport_latency_assumed market_resolved g 3,148 3,148 90ms 355ms 55.4s 1.0min 0 transport_latency_assumed market_resolved h 3,150 3 21ms 65ms 51.2s 1.0min 0 transport_latency_assumed new_market c 2,725 1,043 305ms 16.1min 1.1h 4.0h 0 transport_latency_assumed new_market e 1,742 94 195ms 36.6s 1.3min 1.3h 0 transport_latency_assumed new_market f 1,742 672 205ms 39.4s 1.4min 10.4min 0 transport_latency_assumed new_market g 1,742 1,742 326ms 37.0s 1.4min 1.5h 0 transport_latency_assumed new_market h 1,742 86 165ms 39.1s 1.4min 53.2min 0 transport_latency_assumed price_change c 83,709,133 15,625 4ms 10ms 128ms 8.7s 0 transport_latency_assumed price_change e 109,877,684 15,914 40ms 54ms 305ms 17.5s 0 transport_latency_assumed price_change f 109,888,490 862,706 49ms 67ms 326ms 18.8s 0 transport_latency_assumed price_change g 109,053,262 109,048,984 83ms 176ms 1.9s 39.0s 0 transport_latency_assumed price_change h 109,859,609 15,262 18ms 39ms 330ms 1.5min 0 transport_latency_assumed tick_size_change c 3,368 not meas. 4ms 9ms 101ms 685ms 0 transport_latency_assumed tick_size_change e 4,752 not meas. 39ms 46ms 163ms 452ms 0 transport_latency_assumed tick_size_change f 4,752 40 49ms 58ms 187ms 481ms 0 transport_latency_assumed tick_size_change g 4,712 4,712 83ms 189ms 1.4s 26.6s 0 transport_latency_assumed tick_size_change h 4,752 not meas. 18ms 28ms 252ms 6.1s 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/22/2026-09-05T22.parquet sha256sum 2026-09-05T22.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.