Hour audit: 2026-09-15T20
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-15T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T20:00:00.000663349+00:00 · last event 2026-09-15T20:59:59.999960243+00:00
VOLUME 121,060,274 rows · 1,335,939,910 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 119,497,250 · e: 119,282,339 · f: 114,987,851 · g: 114,668,352 · c: 105,872,192 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,858,036 (16.40%) · e: 1,678,512 (1.39%) · f: 898,813 (0.74%) · g: 286,256 (0.24%) · c: 98,338,657 (81.23%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4e15d1b809c3be74dc6ea0a440c4a378f38547399bf93362247e5020fe9833a1
the corpus checksum ledger names this file with the same digest
joined 121,077,784 to merged 121,060,274, minus 17,510 (minus 0.0145%)
boundary drops 17,510 · 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-15T22:00:20Z 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,481,922 146,311,032 0-47 439004bfcbf357371a55c52d46f17dba5d84a3fb97b250d9399b0068ebb3c745 book 1,806,111 95,296,474 48-54 e0f1d0b30d04c98c4672ded0670d9be52e50448be9ce1a51e2bc88213b7f8ce1 last_trade_price 54,525 3,130,317 55-55 9a257003c7e1a7d64583befc022eb3eab247ad0c5f0185e83bb7320265570e36 market_resolved 1,699 214,625 56-56 d93348195086c9ea63fd8a7a69abc740a0f62914b49bd3487de29b134cdd97ea new_market 5,457 529,738 57-57 c668df29022ce0c73cd6978b8ef21f5b3f1352927bf5a28880483b7f4f947b3f price_change 106,702,944 1,088,803,552 58-465 3ec37e5c85b1873939652275bff2bb14ea98acc0e166598fa5c5b19c55cfbce4 tick_size_change 7,616 276,922 466-466 8c2c4f799314f4e4640babe51d1637f9ce96c8474da1eb238d3069b2f01836b1 EVENT MIX count share price_change 106,702,944 88.14% best_bid_ask 12,481,922 10.31% book 1,806,111 1.49% last_trade_price 54,525 0.05% tick_size_change 7,616 <0.01% new_market 5,457 <0.01% market_resolved 1,699 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,482,258 12,481,922 336 2,133 FULL book 1,818,871 1,806,111 12,760 122,255 FULL last_trade_price 54,527 54,525 2 275 FULL market_resolved 1,699 1,699 0 136 FULL new_market 5,457 5,457 0 8 FULL price_change 106,707,356 106,702,944 4,412 477 FULL tick_size_change 7,616 7,616 0 273 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,919,134 10,187,159 6ms 18ms 239ms 9.8s 0 transport_latency_assumed best_bid_ask e 12,471,244 160,934 41ms 67ms 438ms 26.9s 0 transport_latency_assumed best_bid_ask f 11,987,086 64,664 44ms 75ms 432ms 23.5s 0 transport_latency_assumed best_bid_ask g 11,977,462 4,169 82ms 156ms 915ms 39.5s 0 transport_latency_assumed best_bid_ask h 12,476,508 2,064,996 18ms 38ms 419ms 1.4min 0 transport_latency_assumed book c 1,228,721 992,130 4.6min 2.2d 37.2d 108.9d 0 book_staleness book e 350,339 140,065 52.6s 2.5h 30.0d 108.9d 0 book_staleness book f 655,765 246,744 2.8min 20.0h 35.1d 108.9d 0 book_staleness book g 671,098 238,497 3.0min 1.1d 35.1d 108.9d 0 book_staleness book h 378,231 188,675 1.0min 3.9h 27.0d 108.9d 0 book_staleness last_trade_price c 47,535 44,186 12ms 63ms 353ms 4.9s 0 transport_latency_assumed last_trade_price e 53,735 829 61ms 568ms 7.2s 27.0s 0 transport_latency_assumed last_trade_price f 52,218 374 65ms 626ms 8.4s 23.6s 0 transport_latency_assumed last_trade_price g 51,056 37 109ms 1.7s 17.1s 39.6s 0 transport_latency_assumed last_trade_price h 54,324 9,099 26ms 140ms 1.0s 43.1s 0 transport_latency_assumed market_resolved c 1,327 1,273 7ms 4.7min 5.7min 9.8min 0 transport_latency_assumed market_resolved e 1,300 35 44ms 197ms 52.6s 1.1min 0 transport_latency_assumed market_resolved f 1,300 61 51ms 304ms 3.9min 4.3min 0 transport_latency_assumed market_resolved g 1,236 43 94ms 491ms 5.0min 5.1min 0 transport_latency_assumed market_resolved h 1,299 287 21ms 80ms 49.4s 1.0min 0 transport_latency_assumed new_market c 3,423 1,997 125ms 1.9min 6.2min 9.5min 0 transport_latency_assumed new_market e 3,356 624 260ms 1.2min 3.3min 3.7min 0 transport_latency_assumed new_market f 3,353 622 231ms 1.1min 3.3min 3.6min 0 transport_latency_assumed new_market g 3,364 567 357ms 1.8min 3.9min 5.3min 0 transport_latency_assumed new_market h 3,356 1,647 165ms 1.2min 3.2min 4.1min 0 transport_latency_assumed price_change c 93,665,156 87,105,427 6ms 21ms 255ms 24.6s 0 transport_latency_assumed price_change e 106,394,749 1,375,980 41ms 105ms 1.5s 27.0s 0 transport_latency_assumed price_change f 102,280,829 586,321 44ms 106ms 1.3s 23.7s 0 transport_latency_assumed price_change g 101,956,716 42,940 84ms 231ms 4.3s 39.8s 0 transport_latency_assumed price_change h 106,575,916 17,592,276 18ms 45ms 513ms 1.4min 0 transport_latency_assumed tick_size_change c 6,896 6,485 6ms 15ms 199ms 408ms 0 transport_latency_assumed tick_size_change e 7,616 45 41ms 72ms 437ms 639ms 0 transport_latency_assumed tick_size_change f 7,300 27 44ms 89ms 357ms 999ms 0 transport_latency_assumed tick_size_change g 7,420 3 81ms 163ms 662ms 1.9s 0 transport_latency_assumed tick_size_change h 7,616 1,056 18ms 37ms 344ms 1.3min 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-15/20/2026-09-15T20.parquet sha256sum 2026-09-15T20.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.