Hour audit: 2026-09-05T20
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-05T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T20:00:00.047568881+00:00 · last event 2026-09-05T20:59:59.999979221+00:00
VOLUME 114,845,966 rows · 1,250,793,073 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 113,247,977 · e: 113,231,215 · h: 113,167,415 · g: 110,402,098 · c: 95,963,607 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 2,957,192 (2.57%) · e: 25,597 (0.02%) · h: 42,139 (0.04%) · g: 110,338,774 (96.08%) · c: 1,482,264 (1.29%) (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 114,845,966 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a88ffde5369a73f0e877be298c46ad48f7b909636ae3804768bd0fafa0c69ce6
the corpus checksum ledger names this file with the same digest
joined 114,916,391 to merged 114,845,966, minus 70,425 (minus 0.0613%)
boundary drops 70,425 · 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-06T01:00:25Z 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,983,514 107,863,184 0-34 e740ea868a8e8cc1d985a735520fa1545bdb0d9e59010a3aa7ba60a3081f0d4d book 1,675,754 84,623,475 35-41 5861ea5b933bd1a2c3fcf5049e8acd360b4b4148749c7d76060dbd3d4f844b70 last_trade_price 72,047 4,041,627 42-42 82ec7ec9dd2458bfabbc2a4a50cfe51ff455defad752d33a880f0e6a50a6181a market_resolved 5,374 576,059 43-43 f06278c4f5b3549feed3427e5644b940c2b209787ec375891384ccc11d6fd890 new_market 12,171 1,138,682 44-44 f0e608c72fa058dc4d5755971b06838b6d99deec2100c00ce8c22284c6afdb9d price_change 104,090,338 1,050,990,203 45-442 cb24d0b987f7d2d7b13008dcf4c3607bf038b9a7ef380064b0c5bb8e5cd61cb7 tick_size_change 6,768 249,544 443-443 901c7420b8c4bdccc22252ed956d697962dfca38f18ba547429ccbee01a3aed6 EVENT MIX count share price_change 104,090,338 90.63% best_bid_ask 8,983,514 7.82% book 1,675,754 1.46% last_trade_price 72,047 0.06% new_market 12,171 0.01% tick_size_change 6,768 <0.01% market_resolved 5,374 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,988,086 8,983,514 4,572 4,592 FULL book 1,676,137 1,675,754 383 181,392 FULL last_trade_price 72,192 72,047 145 365 FULL market_resolved 5,375 5,374 1 127 FULL new_market 12,173 12,171 2 58 FULL price_change 104,155,648 104,090,338 65,310 2,925 FULL tick_size_change 6,780 6,768 12 239 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,485,836 662 5ms 25ms 301ms 15.1s 0 transport_latency_assumed best_bid_ask e 8,979,606 1,300 40ms 113ms 490ms 18.9s 0 transport_latency_assumed best_bid_ask f 8,979,085 144,591 50ms 134ms 530ms 26.5s 0 transport_latency_assumed best_bid_ask g 8,838,856 8,834,995 87ms 520ms 10.9s 50.6s 0 transport_latency_assumed best_bid_ask h 8,978,050 1,966 18ms 93ms 2.2s 1.6min 0 transport_latency_assumed book c 1,619,976 1,468,098 3.0min 13.7h 34.3d 98.9d 0 book_staleness book e 162,726 2,547 45ms 2.7s 38.1s 80.4d 0 book_staleness book f 162,182 18,299 56ms 2.5s 18.9s 80.4d 0 book_staleness book g 179,709 179,380 156ms 1.6min 9.3h 98.9d 0 book_staleness book h 166,407 7,430 28ms 2.3s 1.7h 80.4d 0 book_staleness last_trade_price c 60,749 3 10ms 69ms 572ms 6.8s 0 transport_latency_assumed last_trade_price e 71,522 252 48ms 525ms 11.6s 18.5s 0 transport_latency_assumed last_trade_price f 71,424 7,596 60ms 563ms 10.3s 26.6s 0 transport_latency_assumed last_trade_price g 64,061 63,923 100ms 1.4s 17.4s 51.1s 0 transport_latency_assumed last_trade_price h 71,259 273 26ms 194ms 2.9s 53.5s 0 transport_latency_assumed market_resolved c 4,562 1,942 11ms 10.9min 15.1min 15.7min 0 transport_latency_assumed market_resolved e 3,411 18 110ms 267ms 774ms 1.0min 0 transport_latency_assumed market_resolved f 3,411 10 119ms 273ms 688ms 42.2s 0 transport_latency_assumed market_resolved g 3,402 3,402 201ms 778ms 2.9s 1.5min 0 transport_latency_assumed market_resolved h 3,412 2 38ms 125ms 3.3s 2.2min 0 transport_latency_assumed new_market c 8,160 1,529 145ms 6.7min 11.5min 1.6h 0 transport_latency_assumed new_market e 7,023 732 215ms 1.4min 8.1min 2.2d 0 transport_latency_assumed new_market f 7,055 1,871 240ms 1.2min 7.9min 47.4min 0 transport_latency_assumed new_market g 7,055 7,053 361ms 1.3min 6.9min 11.2min 0 transport_latency_assumed new_market h 7,045 986 192ms 1.3min 7.1min 38.6min 0 transport_latency_assumed price_change c 86,778,460 10,030 5ms 28ms 319ms 18.3s 0 transport_latency_assumed price_change e 104,000,159 20,748 40ms 136ms 627ms 18.9s 0 transport_latency_assumed price_change f 104,018,052 2,784,781 50ms 157ms 646ms 26.6s 0 transport_latency_assumed price_change g 101,302,279 101,243,297 88ms 561ms 12.4s 50.6s 0 transport_latency_assumed price_change h 103,934,474 31,482 18ms 101ms 2.1s 1.6min 0 transport_latency_assumed tick_size_change c 5,864 not meas. 5ms 61ms 387ms 1.2s 0 transport_latency_assumed tick_size_change e 6,768 not meas. 40ms 89ms 467ms 763ms 0 transport_latency_assumed tick_size_change f 6,768 44 49ms 108ms 476ms 903ms 0 transport_latency_assumed tick_size_change g 6,736 6,724 91ms 405ms 6.0s 37.4s 0 transport_latency_assumed tick_size_change h 6,768 not meas. 18ms 95ms 849ms 10.3s 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-05/20/2026-09-05T20.parquet sha256sum 2026-09-05T20.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.