Hour audit: 2026-09-06T19
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-06T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T19:00:00.000084754+00:00 · last event 2026-09-06T19:59:59.999916457+00:00
VOLUME 124,776,294 rows · 1,357,248,104 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 122,172,985 · e: 122,141,395 · f: 118,284,816 · g: 117,766,248 · c: 95,469,993 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 29,590,263 (23.71%) · e: 2,579,235 (2.07%) · f: 1,246,269 (1.00%) · g: 182,783 (0.15%) · c: 91,177,744 (73.07%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 7a358ea2769d467cf89b998682b95c8381cd28953bba72ed5c6ca5dc46e706cb
the corpus checksum ledger names this file with the same digest
joined 124,784,242 to merged 124,776,294, minus 7,948 (minus 0.0064%)
boundary drops 7,948 · 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:23:11Z 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,424,588 140,330,997 0-47 9db003c5ecc96fc616b347e450c7a9e4b387db7ddca5270de003e5ba37d87beb book 2,520,453 98,495,586 48-57 3f5c614a5476816941f30e0a0b32cc3ed24ed57824817fd5ed93c744d16b86f8 last_trade_price 57,845 3,341,845 58-58 a7ffc372104b32cca650d20c9316d4f2f5da2e5232254e7d55431a2f8b936583 market_resolved 5,086 511,806 59-59 227e6c715c64aa1c53b96da44f3982a9b9b6969b27bec44c7877c4df0fca105a new_market 9,519 602,131 60-60 42a9eeb928632467a18d77573a766b08285bed782afe889fcb29afd163a970c7 price_change 109,751,639 1,112,288,728 61-479 1c7b706196824b6540361a26a95a74acf40c405f18c61ad0bfa7568f9d3336cd tick_size_change 7,164 258,754 480-480 35ae781aa010de9e4ea227ed7645cd9b21f1b9035b00f6f60d7f44838b5261f5 EVENT MIX count share price_change 109,751,639 87.96% best_bid_ask 12,424,588 9.96% book 2,520,453 2.02% last_trade_price 57,845 0.05% new_market 9,519 <0.01% tick_size_change 7,164 <0.01% market_resolved 5,086 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,424,828 12,424,588 240 4,736 FULL book 2,525,835 2,520,453 5,382 172,523 FULL last_trade_price 57,845 57,845 0 607 FULL market_resolved 5,162 5,086 76 569 FULL new_market 9,539 9,519 20 58 FULL price_change 109,753,869 109,751,639 2,230 3,512 FULL tick_size_change 7,164 7,164 0 555 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,465,041 9,045,887 5ms 12ms 174ms 4.8s 0 transport_latency_assumed best_bid_ask e 12,419,099 267,795 41ms 60ms 364ms 46.3s 0 transport_latency_assumed best_bid_ask f 12,027,758 106,642 45ms 72ms 396ms 25.3s 0 transport_latency_assumed best_bid_ask g 11,953,787 6,951 82ms 152ms 818ms 39.2s 0 transport_latency_assumed best_bid_ask h 12,419,489 2,997,313 18ms 36ms 588ms 1.0min 0 transport_latency_assumed book c 2,221,273 2,191,564 6.8min 1.0d 35.3d 99.9d 0 book_staleness book e 124,603 5,049 44ms 263ms 12.0s 26.0d 0 book_staleness book f 474,772 178,771 1.6min 15.1h 32.1d 99.9d 0 book_staleness book g 482,914 113,585 1.5min 15.5h 33.0d 99.9d 0 book_staleness book h 124,807 31,484 23ms 132ms 5.8s 81.3d 0 book_staleness last_trade_price c 43,766 41,626 10ms 45ms 358ms 5.0s 0 transport_latency_assumed last_trade_price e 57,801 996 47ms 170ms 5.5s 46.3s 0 transport_latency_assumed last_trade_price f 55,468 512 53ms 185ms 2.2s 25.4s 0 transport_latency_assumed last_trade_price g 55,411 30 93ms 385ms 5.0s 34.3s 0 transport_latency_assumed last_trade_price h 57,792 14,681 24ms 80ms 877ms 54.5s 0 transport_latency_assumed market_resolved c 4,511 4,319 176ms 16.2min 21.5min 22.2min 0 transport_latency_assumed market_resolved e 2,708 83 43ms 191ms 1.0min 1.1min 0 transport_latency_assumed market_resolved f 2,721 189 48ms 310ms 4.9min 5.1min 0 transport_latency_assumed market_resolved g 2,674 9 90ms 333ms 972ms 2.5min 0 transport_latency_assumed market_resolved h 2,708 486 21ms 71ms 491ms 10.8s 0 transport_latency_assumed new_market c 8,244 6,360 4.6min 12.8min 20.5min 4.1h 0 transport_latency_assumed new_market e 3,459 708 227ms 39.8s 1.5min 22.0min 0 transport_latency_assumed new_market f 3,465 838 236ms 46.5s 1.7min 46.8min 0 transport_latency_assumed new_market g 3,448 540 411ms 1.2min 4.0min 1.5h 0 transport_latency_assumed new_market h 3,459 1,073 183ms 41.0s 1.5min 2.6h 0 transport_latency_assumed price_change c 83,721,970 79,883,059 5ms 13ms 181ms 5.4s 0 transport_latency_assumed price_change e 109,526,561 2,304,385 41ms 68ms 404ms 46.3s 0 transport_latency_assumed price_change f 105,713,600 959,197 45ms 79ms 433ms 25.5s 0 transport_latency_assumed price_change g 105,261,122 61,664 84ms 168ms 984ms 39.3s 0 transport_latency_assumed price_change h 109,557,566 26,543,334 18ms 39ms 564ms 1.0min 0 transport_latency_assumed tick_size_change c 5,188 4,929 5ms 11ms 200ms 319ms 0 transport_latency_assumed tick_size_change e 7,164 219 41ms 71ms 415ms 1.1s 0 transport_latency_assumed tick_size_change f 7,032 120 45ms 75ms 478ms 735ms 0 transport_latency_assumed tick_size_change g 6,892 4 83ms 154ms 750ms 3.7s 0 transport_latency_assumed tick_size_change h 7,164 1,892 18ms 53ms 651ms 44.9s 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/19/2026-09-06T19.parquet sha256sum 2026-09-06T19.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.