Hour audit: 2026-09-06T15
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-06T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T15:00:00.033167712+00:00 · last event 2026-09-06T15:59:59.999996689+00:00
VOLUME 128,362,739 rows · 1,398,908,863 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,753,800 · e: 124,677,007 · f: 120,483,827 · g: 120,312,087 · c: 84,974,809 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 44,238,152 (34.46%) · e: 2,501,842 (1.95%) · f: 784,024 (0.61%) · g: 244,796 (0.19%) · c: 80,593,925 (62.79%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 64907f34a5ba4f905cb52db532dd6ef5c098a824f46eb9bad3e4e88c164fd48f
the corpus checksum ledger names this file with the same digest
joined 128,364,540 to merged 128,362,739, minus 1,801 (minus 0.0014%)
boundary drops 1,801 · 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-06T23:31:15Z 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,077,298 138,268,497 0-46 e4d5a82b687892e02f2871dccfdbc179db652b591873606220d8cc217758f437 book 3,553,981 117,258,826 47-60 a667509cd5dfc2887cc885895a0cd378717d8814947f0374c07d085dfa43262d last_trade_price 76,024 4,420,753 61-61 baad312a70438c6b94fc1302eb52429f16deec0d1e97b7bd04079e200a342430 market_resolved 6,569 487,779 62-62 001d0a2e509571d2a83249d9ffcbe468e9c7c82f1d5898decf29c422afaf389a new_market 4,079 261,528 63-63 2da3e795be61568efa8a8276288e67a30330b0989c9da14bbd2af0ebcced19ca price_change 112,635,472 1,136,412,711 64-493 490857b873b67b02f49ecd4cff0acdceccaab3f7ebc72195bc48581ec0c74f3a tick_size_change 9,316 338,338 494-494 f0e33efebe59232dcabebb02e8cb79a089a169664b97f279048397bef30c9ec1 EVENT MIX count share price_change 112,635,472 87.75% best_bid_ask 12,077,298 9.41% book 3,553,981 2.77% last_trade_price 76,024 0.06% tick_size_change 9,316 <0.01% market_resolved 6,569 <0.01% new_market 4,079 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,077,498 12,077,298 200 5,866 FULL book 3,554,021 3,553,981 40 172,499 FULL last_trade_price 76,024 76,024 0 1,132 FULL market_resolved 6,569 6,569 0 266 FULL new_market 4,080 4,079 1 2 FULL price_change 112,637,032 112,635,472 1,560 3,113 FULL tick_size_change 9,316 9,316 0 651 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,844,314 7,481,200 5ms 13ms 134ms 10.7s 0 transport_latency_assumed best_bid_ask e 12,075,361 222,981 39ms 50ms 193ms 13.7s 0 transport_latency_assumed best_bid_ask f 11,607,761 47,408 48ms 63ms 219ms 9.0s 0 transport_latency_assumed best_bid_ask g 11,584,063 3,839 81ms 115ms 400ms 26.0s 0 transport_latency_assumed best_bid_ask h 12,076,010 4,321,870 19ms 31ms 176ms 8.0s 0 transport_latency_assumed book c 3,293,475 3,223,990 4.9min 23.1h 35.1d 99.7d 0 book_staleness book e 158,849 6,289 42ms 134ms 3.2s 81.1d 0 book_staleness book f 528,702 90,308 57.1s 15.9h 29.9d 99.7d 0 book_staleness book g 535,776 180,686 55.6s 16.2h 29.3d 99.7d 0 book_staleness book h 158,267 52,708 23ms 65ms 2.0s 35.2d 0 book_staleness last_trade_price c 50,428 47,837 11ms 43ms 273ms 5.0s 0 transport_latency_assumed last_trade_price e 75,990 1,528 46ms 117ms 1.1s 6.0s 0 transport_latency_assumed last_trade_price f 73,081 316 54ms 152ms 1.5s 5.0s 0 transport_latency_assumed last_trade_price g 72,800 77 93ms 248ms 5.5s 26.0s 0 transport_latency_assumed last_trade_price h 75,942 26,266 24ms 65ms 416ms 7.0s 0 transport_latency_assumed market_resolved c 5,372 5,241 6.6min 15.8min 26.2min 27.0min 0 transport_latency_assumed market_resolved e 2,813 94 64ms 194ms 681ms 1.0min 0 transport_latency_assumed market_resolved f 2,682 25 80ms 200ms 507ms 2.1min 0 transport_latency_assumed market_resolved g 2,762 87 112ms 401ms 4.5min 4.9min 0 transport_latency_assumed market_resolved h 2,813 1,122 33ms 80ms 284ms 42.9s 0 transport_latency_assumed new_market c 3,257 2,665 4.7min 22.7min 2.3h 6.6h 0 transport_latency_assumed new_market e 1,597 350 128ms 23.3s 2.8min 28.8min 0 transport_latency_assumed new_market f 1,602 224 140ms 20.2s 3.1min 1.8h 0 transport_latency_assumed new_market g 1,598 184 264ms 24.7s 3.2min 3.4h 0 transport_latency_assumed new_market h 1,596 656 93ms 25.3s 3.0min 2.1h 0 transport_latency_assumed price_change c 73,770,887 69,826,166 5ms 17ms 210ms 11.6s 0 transport_latency_assumed price_change e 112,353,081 2,270,480 40ms 64ms 285ms 13.9s 0 transport_latency_assumed price_change f 108,260,855 645,706 48ms 77ms 307ms 10.8s 0 transport_latency_assumed price_change g 108,106,144 59,919 82ms 144ms 545ms 26.0s 0 transport_latency_assumed price_change h 112,429,856 39,833,201 19ms 38ms 250ms 8.3s 0 transport_latency_assumed tick_size_change c 7,076 6,826 5ms 10ms 118ms 546ms 0 transport_latency_assumed tick_size_change e 9,316 120 39ms 45ms 181ms 393ms 0 transport_latency_assumed tick_size_change f 9,144 37 47ms 54ms 186ms 517ms 0 transport_latency_assumed tick_size_change g 8,944 4 81ms 101ms 363ms 915ms 0 transport_latency_assumed tick_size_change h 9,316 2,329 18ms 26ms 160ms 975ms 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-06/15/2026-09-06T15.parquet sha256sum 2026-09-06T15.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.