Hour audit: 2026-09-11T01
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-11T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T01:00:00.000706044+00:00 · last event 2026-09-11T01:59:59.998626965+00:00
VOLUME 118,458,331 rows · 1,242,228,513 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,235,585 · e: 117,216,351 · f: 112,481,020 · g: 112,381,293 · c: 107,823,094 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,025,403 (11.00%) · e: 1,065,799 (0.90%) · f: 372,802 (0.31%) · g: 112,731 (0.10%) · c: 103,881,596 (87.69%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 118,458,331 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 675a73e33f6d871caafef3254d43e76fa932e11f9e08c0e025dc261104be0516
the corpus checksum ledger names this file with the same digest
joined 118,462,885 to merged 118,458,331, minus 4,554 (minus 0.0038%)
boundary drops 4,554 · 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-11T03:00:00Z 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 11,376,003 123,759,425 0-43 26a148e4a13e4e698eb980a0c30baecfbf53e780b57f51fec700baae6fb7cd7b book 1,303,309 84,472,237 44-48 e2ae42f57f5e4ad748712d8d22973d169e66ed84b40add2d1b7b96e583402fac last_trade_price 48,990 2,904,873 49-49 bfab528a2cab829251c37d6d05de776ca6060d3f631fafb6a92308c9d1d8db02 market_resolved 724 97,401 50-50 c4ce09feb3a65473ce0028f7bacd6a5be2c12083a5d2bc36d364419a93881e36 new_market 623 67,897 51-51 887016cc719313c0fa00ce64ad933d822789ebd0142c309338a9604c37a798fb price_change 105,726,282 1,029,489,189 52-455 b742b83dae8372f987b8434a13713758ac1963e37e83e7ddda72c23243049fd0 tick_size_change 2,400 89,491 456-456 f6c6f4f6eae92603b1244c48a8147205f37883112ccba56cc58e4bb2131b550a EVENT MIX count share price_change 105,726,282 89.25% best_bid_ask 11,376,003 9.60% book 1,303,309 1.10% last_trade_price 48,990 0.04% tick_size_change 2,400 <0.01% market_resolved 724 <0.01% new_market 623 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,376,253 11,376,003 250 1,687 FULL book 1,303,938 1,303,309 629 180,984 FULL last_trade_price 48,991 48,990 1 157 FULL market_resolved 724 724 0 5 FULL new_market 623 623 0 17 FULL price_change 105,729,956 105,726,282 3,674 1,097 FULL tick_size_change 2,400 2,400 0 88 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,381,900 10,027,542 5ms 9ms 73ms 2.8s 0 transport_latency_assumed best_bid_ask e 11,367,544 91,613 39ms 45ms 122ms 3.0s 0 transport_latency_assumed best_bid_ask f 10,873,329 19,053 45ms 57ms 152ms 1.9s 0 transport_latency_assumed best_bid_ask g 10,890,397 1,686 79ms 107ms 256ms 12.3s 0 transport_latency_assumed best_bid_ask h 11,374,152 1,236,109 18ms 26ms 108ms 8.8s 0 transport_latency_assumed book c 967,546 913,899 19.5min 1.1d 30.3d 104.1d 0 book_staleness book e 247,425 71,215 32.8s 15.5h 19.5d 104.1d 0 book_staleness book f 575,533 153,630 9.3min 22.3h 29.3d 104.1d 0 book_staleness book g 549,760 92,292 8.2min 22.2h 28.9d 104.1d 0 book_staleness book h 237,396 72,273 22.2s 14.3h 19.5d 104.1d 0 book_staleness last_trade_price c 44,993 42,857 10ms 40ms 202ms 4.9s 0 transport_latency_assumed last_trade_price e 48,522 500 45ms 93ms 361ms 4.9s 0 transport_latency_assumed last_trade_price f 46,137 134 53ms 108ms 396ms 4.9s 0 transport_latency_assumed last_trade_price g 46,815 19 94ms 188ms 504ms 5.0s 0 transport_latency_assumed last_trade_price h 48,849 5,480 23ms 64ms 261ms 8.8s 0 transport_latency_assumed market_resolved c 672 653 5ms 7.2min 12.7min 12.7min 0 transport_latency_assumed market_resolved e 586 6 39ms 114ms 376ms 619ms 0 transport_latency_assumed market_resolved f 582 2 47ms 161ms 440ms 745ms 0 transport_latency_assumed market_resolved g 586 8 86ms 341ms 4.4min 4.4min 0 transport_latency_assumed market_resolved h 585 55 18ms 64ms 309ms 1.2s 0 transport_latency_assumed new_market c 466 287 83ms 6.5min 8.3min 8.3min 0 transport_latency_assumed new_market e 431 103 95ms 12.9s 20.0s 1.0min 0 transport_latency_assumed new_market f 431 63 120ms 438ms 21.8s 1.0min 0 transport_latency_assumed new_market g 431 12 195ms 564ms 27.0s 41.2min 0 transport_latency_assumed new_market h 431 158 72ms 288ms 24.5s 57.1s 0 transport_latency_assumed price_change c 96,425,341 92,894,190 5ms 10ms 85ms 3.4s 0 transport_latency_assumed price_change e 105,549,443 902,354 39ms 48ms 156ms 3.2s 0 transport_latency_assumed price_change f 100,982,724 199,920 46ms 60ms 184ms 2.9s 0 transport_latency_assumed price_change g 100,891,088 18,714 79ms 115ms 305ms 12.8s 0 transport_latency_assumed price_change h 105,571,772 11,711,104 18ms 29ms 128ms 8.8s 0 transport_latency_assumed tick_size_change c 2,176 2,168 5ms 7ms 19ms 75ms 0 transport_latency_assumed tick_size_change e 2,400 8 39ms 43ms 98ms 233ms 0 transport_latency_assumed tick_size_change f 2,284 not meas. 45ms 50ms 98ms 242ms 0 transport_latency_assumed tick_size_change g 2,216 not meas. 78ms 94ms 179ms 422ms 0 transport_latency_assumed tick_size_change h 2,400 224 18ms 23ms 70ms 215ms 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-11/01/2026-09-11T01.parquet sha256sum 2026-09-11T01.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.