Hour audit: 2026-09-19T17
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-19T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T17:00:00.000003188+00:00 · last event 2026-09-19T17:59:59.997989398+00:00
VOLUME 4,652,601 rows · 111,669,917 bytes (106.50 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 4,267,130 · c: 4,261,234 · f: 4,218,186 · h: 4,216,779 · g: 4,212,824 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 241,157 (5.18%) · c: 3,677,174 (79.03%) · f: 195,766 (4.21%) · h: 393,144 (8.45%) · g: 145,360 (3.12%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 4,652,601 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 051bd81db6d1750bc10465e51ecf7acab38444cc4827366494ba076aa93cb378
the corpus checksum ledger names this file with the same digest
joined 4,653,866 to merged 4,652,601, minus 1,265 (minus 0.0272%)
boundary drops 1,265 · 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-19T18:36:50Z 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 an incident recorded by the venue intersects this hour: Trading degraded, then cancel-only mode, 2026-09-19T16:54Z to 2026-09-19T18:58ZThe 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 335,034 10,570,057 0-1 6c1b413024be0ba3bd438cd1e05981eacf6c42ce5bcd597c31b203bdfae56dd7 book 744,098 49,267,393 2-4 63f4306e5d4a2dfa3e15516c20148d82056697a3ffc157a068cd4eede37067e0 last_trade_price 1,235 92,818 5-5 b74733086efa8ad4a0b9ea96fdea9420ffc8a08ad68c2353473d517bafaa3d99 market_resolved 2,886 459,183 6-6 3ce4df2c2864861ca11e442ae8f77c0277763d36c9083f4dcf7ffb3c727d29b0 new_market 1,072 112,676 7-7 b13fd685b8c8a967dce1a90eea3efb31a18082d6932c5d245229af31829c741b price_change 3,567,596 51,073,104 8-21 0a84a6863d5cee78bee308f8b004a2d5cd05fcd3be27b0e01f8333b27fc1060e tick_size_change 680 24,712 22-22 5c30c326863196cc1ecdc7f4aed55eeec4cc834644a74007db95d74989f09a2d EVENT MIX count share price_change 3,567,596 76.68% book 744,098 15.99% best_bid_ask 335,034 7.20% market_resolved 2,886 0.06% last_trade_price 1,235 0.03% new_market 1,072 0.02% tick_size_change 680 0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 335,138 335,034 104 67 FULL book 744,174 744,098 76 181,724 FULL last_trade_price 1,236 1,235 1 0 FULL market_resolved 2,886 2,886 0 0 FULL new_market 1,072 1,072 0 0 FULL price_change 3,568,680 3,567,596 1,084 34 FULL tick_size_change 680 680 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 334,916 311,852 6ms 30ms 429ms 3.1s 0 transport_latency_assumed best_bid_ask e 334,760 3,405 42ms 96ms 530ms 2.0s 0 transport_latency_assumed best_bid_ask f 334,912 2,617 48ms 102ms 509ms 2.3s 0 transport_latency_assumed best_bid_ask g 334,882 655 80ms 204ms 879ms 11.5s 0 transport_latency_assumed best_bid_ask h 334,940 16,505 20ms 49ms 810ms 9.9s 0 transport_latency_assumed book c 354,972 176,741 36.6min 1.1d 38.9d 112.8d 0 book_staleness book e 364,268 169,622 36.8min 1.1d 38.9d 112.8d 0 book_staleness book f 313,139 134,914 38.0min 1.1d 39.0d 112.8d 0 book_staleness book g 305,304 125,623 37.6min 1.1d 39.0d 112.8d 0 book_staleness book h 309,562 137,198 37.8min 1.1d 39.0d 112.8d 0 book_staleness last_trade_price c 1,231 1,084 12ms 119ms 910ms 4.8s 0 transport_latency_assumed last_trade_price e 1,225 17 72ms 391ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price f 1,228 18 82ms 355ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 1,235 4 139ms 4.1s 11.2s 11.5s 0 transport_latency_assumed last_trade_price h 1,234 112 29ms 169ms 865ms 8.3s 0 transport_latency_assumed market_resolved c 2,871 2,853 5ms 8ms 24ms 2.2min 0 transport_latency_assumed market_resolved e 2,871 10 121ms 337ms 528ms 56.0s 0 transport_latency_assumed market_resolved f 2,871 3 128ms 356ms 537ms 2.1min 0 transport_latency_assumed market_resolved g 2,871 not meas. 222ms 555ms 845ms 1.3s 0 transport_latency_assumed market_resolved h 2,871 20 41ms 100ms 164ms 2.1min 0 transport_latency_assumed new_market c 726 424 78ms 13.8s 1.1min 3.8min 0 transport_latency_assumed new_market e 726 189 156ms 22.1s 57.1s 1.3min 0 transport_latency_assumed new_market f 726 126 160ms 23.6s 1.0min 20.7min 0 transport_latency_assumed new_market g 726 70 253ms 16.0s 55.7s 14.5min 0 transport_latency_assumed new_market h 726 263 138ms 15.7s 1.0min 43.5min 0 transport_latency_assumed price_change c 3,565,838 3,183,540 6ms 102ms 748ms 4.3s 0 transport_latency_assumed price_change e 3,562,600 67,914 43ms 241ms 931ms 2.8s 0 transport_latency_assumed price_change f 3,564,630 58,088 49ms 239ms 864ms 2.3s 0 transport_latency_assumed price_change g 3,567,126 19,008 83ms 412ms 2.3s 11.6s 0 transport_latency_assumed price_change h 3,566,766 239,046 21ms 149ms 843ms 10.1s 0 transport_latency_assumed tick_size_change c 680 680 5ms 7ms 11ms 18ms 0 transport_latency_assumed tick_size_change e 680 not meas. 42ms 46ms 201ms 204ms 0 transport_latency_assumed tick_size_change f 680 not meas. 47ms 51ms 190ms 193ms 0 transport_latency_assumed tick_size_change g 680 not meas. 79ms 94ms 235ms 373ms 0 transport_latency_assumed tick_size_change h 680 not meas. 19ms 22ms 81ms 84ms 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/17/2026-09-19T17.parquet sha256sum 2026-09-19T17.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.