Hour audit: 2026-09-19T14
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-19T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T14:00:00.000870865+00:00 · last event 2026-09-19T14:59:59.999988023+00:00
VOLUME 154,288,431 rows · 1,783,948,462 bytes (1.66 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 149,136,409 · e: 137,009,587 · g: 118,353,498 · f: 112,244,147 · c: 94,609,339 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 57,033,629 (36.97%) · e: 5,662,656 (3.67%) · g: 1,110,722 (0.72%) · f: 1,757,995 (1.14%) · c: 88,723,429 (57.50%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 df8e2cd5e687bd0589c9247330c5468b764e89536d9568cedf39868d90cc0bc1
the corpus checksum ledger names this file with the same digest
joined 154,319,158 to merged 154,288,431, minus 30,727 (minus 0.0199%)
boundary drops 30,727 · 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-19T16:05:56Z 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 17,005,048 202,260,491 0-64 8d561915a864cb532683f7abb86e4c59b7b0938d76274d7333a0eee40479aebb book 5,232,475 178,428,490 65-84 22c6aa3490fd52a3a60744dab6c9c293bc65dab7445a383e18331d7a8cb16bf2 last_trade_price 74,041 4,447,753 85-85 d2d66a3d1cc39e975b71cbc14683a12c23039fcbbb224e4164bbbc539e270df6 market_resolved 9,767 412,921 86-86 0dfaae31885507d2e9ddf7723e315de25012ac2dbc653c994684ee20515df77a new_market 5,070 309,022 87-87 f86940c0455bacffb795f57be11089003c1b0057e4454aa30f1976ed18ba7e43 price_change 131,947,926 1,395,826,364 88-591 b850a3d20df13f170e84474177fd11f64badf69be2496e947bd92ca5b879e346 tick_size_change 14,104 513,269 592-592 882dc0031cb071d8bf83bbd7d4ef961722c117a3faa34205482f5d27e707e967 EVENT MIX count share price_change 131,947,926 85.52% best_bid_ask 17,005,048 11.02% book 5,232,475 3.39% last_trade_price 74,041 0.05% tick_size_change 14,104 <0.01% market_resolved 9,767 <0.01% new_market 5,070 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 17,005,362 17,005,048 314 13,943 FULL book 5,259,998 5,232,475 27,523 201,342 FULL last_trade_price 74,043 74,041 2 2,277 FULL market_resolved 9,767 9,767 0 284 FULL new_market 5,070 5,070 0 13 FULL price_change 131,950,814 131,947,926 2,888 6,939 FULL tick_size_change 14,104 14,104 0 2,228 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,329,817 9,747,922 5ms 17ms 160ms 4.5s 0 transport_latency_assumed best_bid_ask e 15,578,112 610,512 40ms 58ms 317ms 24.9s 0 transport_latency_assumed best_bid_ask f 12,494,334 107,252 49ms 70ms 360ms 30.5s 0 transport_latency_assumed best_bid_ask g 13,281,468 21,536 79ms 108ms 639ms 33.0s 0 transport_latency_assumed best_bid_ask h 17,001,123 6,517,826 19ms 48ms 368ms 59.4s 0 transport_latency_assumed book c 3,841,894 3,339,174 5.2min 22.4h 38.8d 112.7d 0 book_staleness book e 1,008,496 276,311 3.3min 20.2h 35.0d 112.7d 0 book_staleness book f 2,714,129 703,083 4.9min 22.3h 38.8d 112.7d 0 book_staleness book g 2,210,980 854,203 4.6min 22.3h 38.6d 112.7d 0 book_staleness book h 160,400 59,704 26ms 178ms 12.4min 94.1d 0 book_staleness last_trade_price c 44,234 41,433 11ms 60ms 511ms 5.0s 0 transport_latency_assumed last_trade_price e 66,277 2,612 54ms 306ms 6.7s 24.9s 0 transport_latency_assumed last_trade_price f 54,140 724 65ms 368ms 7.5s 30.4s 0 transport_latency_assumed last_trade_price g 54,071 285 95ms 586ms 10.1s 33.1s 0 transport_latency_assumed last_trade_price h 73,741 28,987 29ms 135ms 1.1s 50.6s 0 transport_latency_assumed market_resolved c 8,666 7,641 17.6min 38.0min 45.6min 46.6min 0 transport_latency_assumed market_resolved e 2,135 132 106ms 317ms 5.1min 6.5min 0 transport_latency_assumed market_resolved f 2,396 158 124ms 8.2min 11.8min 13.7min 0 transport_latency_assumed market_resolved g 3,206 907 482ms 11.8min 17.2min 17.7min 0 transport_latency_assumed market_resolved h 2,139 929 35ms 89ms 58.1s 1.0min 0 transport_latency_assumed new_market c 4,351 3,336 5.8min 21.7min 30.2min 40.1min 0 transport_latency_assumed new_market e 1,836 362 221ms 34.8s 4.2min 1.1h 0 transport_latency_assumed new_market f 1,937 307 255ms 1.1min 8.6min 2.0h 0 transport_latency_assumed new_market g 2,201 497 483ms 5.5min 9.3min 20.4min 0 transport_latency_assumed new_market h 1,832 568 188ms 29.8s 1.7min 1.8min 0 transport_latency_assumed price_change c 80,370,813 75,574,745 5ms 20ms 191ms 8.3s 0 transport_latency_assumed price_change e 120,339,059 4,772,377 41ms 75ms 681ms 25.0s 0 transport_latency_assumed price_change f 96,965,507 946,425 49ms 90ms 800ms 30.5s 0 transport_latency_assumed price_change g 102,790,896 233,286 80ms 145ms 1.7s 33.2s 0 transport_latency_assumed price_change h 131,883,070 50,421,093 20ms 54ms 458ms 1.0min 0 transport_latency_assumed tick_size_change c 9,564 9,178 5ms 12ms 86ms 427ms 0 transport_latency_assumed tick_size_change e 13,672 350 40ms 49ms 135ms 908ms 0 transport_latency_assumed tick_size_change f 11,704 46 48ms 58ms 158ms 765ms 0 transport_latency_assumed tick_size_change g 10,676 8 79ms 95ms 301ms 2.8s 0 transport_latency_assumed tick_size_change h 14,104 4,522 19ms 38ms 103ms 2.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-19/14/2026-09-19T14.parquet sha256sum 2026-09-19T14.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.