Hour audit: 2026-09-08T01
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-08T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T01:00:00.000142364+00:00 · last event 2026-09-08T01:59:59.999986916+00:00
VOLUME 93,261,829 rows · 929,263,740 bytes (886.21 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 93,236,677 · h: 93,207,414 · e: 93,179,376 · g: 93,161,684 · f: 93,159,110 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 89,510,469 (95.98%) · h: 3,594,266 (3.85%) · e: 102,839 (0.11%) · g: 14,332 (0.02%) · f: 39,923 (0.04%) (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 93,261,829 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 66bc698422a13a8a5bacc9cf4e9fa7e22b2007325ff1505a98cedbd659443b23
the corpus checksum ledger names this file with the same digest
joined 93,264,455 to merged 93,261,829, minus 2,626 (minus 0.0028%)
boundary drops 2,626 · 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-08T02:54:34Z 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 10,115,075 109,344,397 0-38 f4603065b6961a1fb007d712c96fc0f1081bdd381448f560fe7bc4f3eff47469 book 162,172 16,234,502 39-39 fb5661bb115168bb03e0eeed1e5c18798e58e57529a2b60c90fa35b672e663b3 last_trade_price 59,868 3,287,839 40-40 4d719a72a9ea71d78551716183f2a0bb021cd953e265494679a7a2dcb4386090 market_resolved 634 94,120 41-41 1095b8b891d52aefb0ca6986b557a1f6ef189993bd9f32ce2ba76bd91ee8bce9 new_market 398 45,929 42-42 dd04886ea44a56853e3f1fd5ba3178bdea21599bd646fba43512324b277aa47c price_change 82,921,750 799,121,470 43-359 f3205ae89fb10b725efc30bf639fe2a205e537dc85a2dd5ca32a5ae62cffd953 tick_size_change 1,932 70,152 360-360 0f4bd1138f4e6c32bd958c958c37eb12145bced32fd2bb6d071fbf8192e3f305 EVENT MIX count share price_change 82,921,750 88.91% best_bid_ask 10,115,075 10.85% book 162,172 0.17% last_trade_price 59,868 0.06% tick_size_change 1,932 <0.01% market_resolved 634 <0.01% new_market 398 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,115,305 10,115,075 230 115 FULL book 162,172 162,172 0 17,352 FULL last_trade_price 59,868 59,868 0 0 FULL market_resolved 634 634 0 0 FULL new_market 398 398 0 0 FULL price_change 82,924,146 82,921,750 2,396 265 FULL tick_size_change 1,932 1,932 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,114,591 9,740,605 4ms 7ms 51ms 3.2s 0 transport_latency_assumed best_bid_ask e 10,113,514 9,415 41ms 45ms 100ms 2.3s 0 transport_latency_assumed best_bid_ask f 10,113,325 3,289 46ms 51ms 116ms 2.4s 0 transport_latency_assumed best_bid_ask g 10,112,316 206 82ms 101ms 212ms 9.9s 0 transport_latency_assumed best_bid_ask h 10,114,460 361,560 12ms 15ms 63ms 7.2s 0 transport_latency_assumed book c 144,616 137,345 6ms 2.1min 23.2h 82.6d 0 book_staleness book e 125,076 1,604 42ms 71ms 934ms 36.6d 0 book_staleness book f 125,354 1,710 48ms 82ms 16.8s 82.6d 0 book_staleness book g 135,674 11,732 84ms 361ms 15.0h 101.1d 0 book_staleness book h 127,389 9,781 15ms 37ms 48.6min 82.5d 0 book_staleness last_trade_price c 59,801 56,718 9ms 35ms 158ms 5.0s 0 transport_latency_assumed last_trade_price e 59,765 149 46ms 81ms 295ms 5.0s 0 transport_latency_assumed last_trade_price f 59,694 43 52ms 89ms 280ms 5.0s 0 transport_latency_assumed last_trade_price g 59,683 12 90ms 155ms 452ms 5.1s 0 transport_latency_assumed last_trade_price h 59,744 2,946 17ms 46ms 183ms 5.0s 0 transport_latency_assumed market_resolved c 577 513 4ms 24ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 577 58 43ms 467ms 56.3s 1.0min 0 transport_latency_assumed market_resolved f 577 not meas. 48ms 484ms 56.3s 1.0min 0 transport_latency_assumed market_resolved g 577 1 84ms 249ms 483ms 890ms 0 transport_latency_assumed market_resolved h 577 62 13ms 33ms 81ms 260ms 0 transport_latency_assumed new_market c 286 128 41ms 274ms 23.7s 1.1min 0 transport_latency_assumed new_market e 286 43 55ms 291ms 22.4s 1.1min 0 transport_latency_assumed new_market f 286 21 81ms 11.8s 1.0min 1.1min 0 transport_latency_assumed new_market g 286 33 99ms 13.6s 21.4s 1.4min 0 transport_latency_assumed new_market h 286 173 39ms 12.5s 1.0min 1.2min 0 transport_latency_assumed price_change c 82,914,874 79,573,278 4ms 8ms 61ms 4.1s 0 transport_latency_assumed price_change e 82,878,226 91,570 41ms 47ms 128ms 3.4s 0 transport_latency_assumed price_change f 82,857,942 34,860 47ms 53ms 143ms 3.6s 0 transport_latency_assumed price_change g 82,851,216 2,348 83ms 102ms 255ms 10.4s 0 transport_latency_assumed price_change h 82,903,026 3,219,694 12ms 17ms 76ms 7.2s 0 transport_latency_assumed tick_size_change c 1,932 1,882 4ms 7ms 31ms 155ms 0 transport_latency_assumed tick_size_change e 1,932 not meas. 41ms 45ms 95ms 159ms 0 transport_latency_assumed tick_size_change f 1,932 not meas. 47ms 51ms 117ms 183ms 0 transport_latency_assumed tick_size_change g 1,932 not meas. 83ms 101ms 211ms 233ms 0 transport_latency_assumed tick_size_change h 1,932 50 12ms 21ms 106ms 137ms 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-08/01/2026-09-08T01.parquet sha256sum 2026-09-08T01.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.