Hour audit: 2026-09-09T07
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-09T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T07:00:00.000925301+00:00 · last event 2026-09-09T07:59:59.999364429+00:00
VOLUME 99,196,030 rows · 973,190,169 bytes (928.11 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 99,050,507 · c: 99,029,580 · e: 99,011,459 · g: 99,010,044 · h: 98,956,020 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 141,366 (0.14%) · c: 93,862,909 (94.62%) · e: 397,141 (0.40%) · g: 45,170 (0.05%) · h: 4,749,444 (4.79%) (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 99,196,030 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7dc98899aa872819b3d55937ce1e2785db91219e5684c043a1c1297eef11db43
the corpus checksum ledger names this file with the same digest
joined 99,199,327 to merged 99,196,030, minus 3,297 (minus 0.0033%)
boundary drops 3,297 · 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-09T08:56:10Z 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 8,859,578 97,871,049 0-33 2fc01381946da6469cdff800affbc332d686f6390b7453d5d6871b5690bbe4e2 book 133,531 13,945,720 34-34 ebbb064d760defdc1669c229314a16c47b29b04dac1284e82fab9f9b97962e2a last_trade_price 56,516 3,211,392 35-35 d31f8e63dbaedd5f0b44d4f7ac36051bb1f27105e1e95e06d21a5245bf41bed5 market_resolved 538 89,256 36-36 3cc0bc278701da29b69b3a0d46e326dc4f9dd85f011b55fd53d03347524d62f1 new_market 1,187 120,112 37-37 5d5e3a48e35399940c25d7de0e03ddabd48e359542f137852cc872410e8cd432 price_change 90,142,508 856,741,448 38-381 c5f2290961f2f4f20f60185d13f39ed70ecdc48b93a003fffde6e4c4b1afe085 tick_size_change 2,172 80,809 382-382 deac018c4c9dfac59339bb657393b00bfda17a613fc74e05b1544ca9021235ec EVENT MIX count share price_change 90,142,508 90.87% best_bid_ask 8,859,578 8.93% book 133,531 0.13% last_trade_price 56,516 0.06% tick_size_change 2,172 <0.01% new_market 1,187 <0.01% market_resolved 538 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,859,838 8,859,578 260 104 FULL book 133,533 133,531 2 6,888 FULL last_trade_price 56,521 56,516 5 1 FULL market_resolved 538 538 0 0 FULL new_market 1,187 1,187 0 0 FULL price_change 90,145,538 90,142,508 3,030 466 FULL tick_size_change 2,172 2,172 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,859,218 8,410,864 5ms 9ms 116ms 10.0s 0 transport_latency_assumed best_bid_ask e 8,857,674 31,410 35ms 40ms 181ms 9.8s 0 transport_latency_assumed best_bid_ask f 8,857,846 10,080 46ms 52ms 205ms 7.9s 0 transport_latency_assumed best_bid_ask g 8,857,050 1,105 84ms 110ms 420ms 18.2s 0 transport_latency_assumed best_bid_ask h 8,858,854 406,119 13ms 18ms 155ms 54.8s 0 transport_latency_assumed book c 118,912 110,809 7ms 25ms 57.4s 83.8d 0 book_staleness book e 119,272 3,162 38ms 169ms 7.0min 83.8d 0 book_staleness book f 119,286 2,416 48ms 195ms 12.5min 83.9d 0 book_staleness book g 125,127 8,295 92ms 690ms 14.7h 83.9d 0 book_staleness book h 119,076 8,849 17ms 64ms 2.3min 83.8d 0 book_staleness last_trade_price c 56,449 53,150 10ms 39ms 227ms 4.9s 0 transport_latency_assumed last_trade_price e 56,376 243 41ms 134ms 909ms 9.8s 0 transport_latency_assumed last_trade_price f 56,388 48 52ms 159ms 963ms 7.9s 0 transport_latency_assumed last_trade_price g 56,204 11 98ms 257ms 1.8s 18.2s 0 transport_latency_assumed last_trade_price h 56,398 3,064 18ms 61ms 363ms 38.2s 0 transport_latency_assumed market_resolved c 538 500 5ms 16ms 146ms 470ms 0 transport_latency_assumed market_resolved e 538 1 36ms 192ms 845ms 1.3s 0 transport_latency_assumed market_resolved f 538 not meas. 47ms 200ms 507ms 944ms 0 transport_latency_assumed market_resolved g 538 not meas. 87ms 379ms 955ms 5.0s 0 transport_latency_assumed market_resolved h 538 37 13ms 86ms 256ms 375ms 0 transport_latency_assumed new_market c 787 380 122ms 19.2s 37.8s 49.3s 0 transport_latency_assumed new_market e 787 246 202ms 22.9s 37.8s 1.3min 0 transport_latency_assumed new_market f 787 150 230ms 19.4s 44.4s 1.1min 0 transport_latency_assumed new_market g 787 43 354ms 24.4s 39.9s 57.6s 0 transport_latency_assumed new_market h 787 368 151ms 19.4s 37.7s 1.3min 0 transport_latency_assumed price_change c 89,991,504 85,285,208 5ms 10ms 129ms 11.0s 0 transport_latency_assumed price_change e 89,974,640 362,071 35ms 44ms 261ms 9.9s 0 transport_latency_assumed price_change f 90,013,490 128,668 46ms 57ms 292ms 8.0s 0 transport_latency_assumed price_change g 89,968,166 35,716 85ms 121ms 568ms 18.3s 0 transport_latency_assumed price_change h 89,918,195 4,330,845 13ms 21ms 184ms 55.0s 0 transport_latency_assumed tick_size_change c 2,172 1,998 5ms 12ms 164ms 998ms 0 transport_latency_assumed tick_size_change e 2,172 8 36ms 42ms 201ms 257ms 0 transport_latency_assumed tick_size_change f 2,172 4 46ms 76ms 176ms 708ms 0 transport_latency_assumed tick_size_change g 2,172 not meas. 85ms 149ms 386ms 749ms 0 transport_latency_assumed tick_size_change h 2,172 162 13ms 27ms 378ms 2.5s 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-09/07/2026-09-09T07.parquet sha256sum 2026-09-09T07.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.