Hour audit: 2026-09-16T12
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-16T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T12:00:00.000013438+00:00 · last event 2026-09-16T12:59:59.999904932+00:00
VOLUME 114,482,407 rows · 1,179,049,863 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 114,335,559 · h: 114,278,420 · f: 114,234,948 · e: 114,204,238 · g: 114,101,148 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 108,650,806 (94.91%) · h: 5,016,382 (4.38%) · f: 239,554 (0.21%) · e: 523,948 (0.46%) · g: 51,717 (0.05%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 114,482,407 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d45fcf13825bb456c3716901b46f5e1f6ab861d9dfb21e0a1f068f303740e186
the corpus checksum ledger names this file with the same digest
joined 114,485,664 to merged 114,482,407, minus 3,257 (minus 0.0028%)
boundary drops 3,257 · 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-16T14:36:38Z 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,070,804 138,889,509 0-46 e17c1a9793d4ccf2219fcd91a051468b33b7f7f3fccfe91e5175fdf25180bbd4 book 268,897 28,692,775 47-48 5b3566c849cafa991f19989b6662b6af831e95f30f1868b7897f0d86a92459f4 last_trade_price 54,037 3,106,580 49-49 fd250f4dffff7dd7ab196f39f8c14a2c1b43394c66f3e89de7377ffb91d00f66 market_resolved 752 117,653 50-50 20a16e5565a5aad3862f1940d1673cc70862ef2636f83210a34199e1143f136e new_market 1,579 161,983 51-51 03fc220992b9887098dc06fb5666c6e68c494df5cb6a4a26ac38febb832245dd price_change 102,082,942 1,006,650,437 52-441 52828dca7de7bb41bef8c8e84ff04f0b5301d229718bd0daf103006396113410 tick_size_change 3,396 124,821 442-442 2d9ffb0d479c28da4922752b46c747fe767c0e0cdc124bd38703fd4f9d37b6fd EVENT MIX count share price_change 102,082,942 89.17% best_bid_ask 12,070,804 10.54% book 268,897 0.23% last_trade_price 54,037 0.05% tick_size_change 3,396 <0.01% new_market 1,579 <0.01% market_resolved 752 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,071,152 12,070,804 348 265 FULL book 268,907 268,897 10 65,641 FULL last_trade_price 54,040 54,037 3 1 FULL market_resolved 752 752 0 0 FULL new_market 1,579 1,579 0 0 FULL price_change 102,085,838 102,082,942 2,896 115 FULL tick_size_change 3,396 3,396 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,069,426 11,504,053 5ms 13ms 116ms 5.4s 0 transport_latency_assumed best_bid_ask e 12,066,410 46,967 38ms 49ms 224ms 11.8s 0 transport_latency_assumed best_bid_ask f 12,066,988 17,293 46ms 60ms 257ms 13.1s 0 transport_latency_assumed best_bid_ask g 12,065,609 1,934 80ms 102ms 461ms 24.9s 0 transport_latency_assumed best_bid_ask h 12,067,943 500,557 19ms 31ms 176ms 40.1s 0 transport_latency_assumed book c 155,587 144,021 9ms 14.4min 11.0d 109.6d 0 book_staleness book e 151,975 37,127 54ms 13.1min 11.0d 109.6d 0 book_staleness book f 151,300 35,283 67ms 13.2min 11.0d 109.6d 0 book_staleness book g 141,266 28,142 98ms 6.4min 9.1d 109.6d 0 book_staleness book h 132,515 24,324 25ms 2.4min 7.2d 91.1d 0 book_staleness last_trade_price c 53,884 50,798 11ms 54ms 264ms 5.0s 0 transport_latency_assumed last_trade_price e 53,333 263 51ms 331ms 4.7s 11.8s 0 transport_latency_assumed last_trade_price f 53,500 150 61ms 436ms 5.9s 13.1s 0 transport_latency_assumed last_trade_price g 53,285 26 97ms 755ms 12.5s 24.9s 0 transport_latency_assumed last_trade_price h 53,542 2,800 26ms 97ms 467ms 9.9s 0 transport_latency_assumed market_resolved c 719 683 5ms 25ms 59.3s 1.0min 0 transport_latency_assumed market_resolved e 719 2 39ms 201ms 1.0min 1.1min 0 transport_latency_assumed market_resolved f 719 2 48ms 205ms 59.5s 1.0min 0 transport_latency_assumed market_resolved g 719 20 84ms 266ms 832ms 1.0s 0 transport_latency_assumed market_resolved h 719 45 20ms 73ms 60.0s 1.1min 0 transport_latency_assumed new_market c 1,053 607 96ms 14.2s 29.2s 1.4min 0 transport_latency_assumed new_market e 1,053 158 223ms 20.6s 29.5s 1.2min 0 transport_latency_assumed new_market f 1,053 258 176ms 14.4s 29.5s 1.2min 0 transport_latency_assumed new_market g 1,053 101 332ms 16.6s 29.0s 1.4min 0 transport_latency_assumed new_market h 1,053 455 135ms 19.2s 29.5s 1.9min 0 transport_latency_assumed price_change c 102,051,494 96,947,494 5ms 15ms 139ms 5.6s 0 transport_latency_assumed price_change e 101,927,352 439,414 38ms 63ms 614ms 11.9s 0 transport_latency_assumed price_change f 101,957,992 186,564 46ms 75ms 738ms 13.1s 0 transport_latency_assumed price_change g 101,835,820 21,494 81ms 133ms 1.4s 24.9s 0 transport_latency_assumed price_change h 102,019,252 4,487,976 19ms 36ms 260ms 45.9s 0 transport_latency_assumed tick_size_change c 3,396 3,150 6ms 20ms 145ms 354ms 0 transport_latency_assumed tick_size_change e 3,396 17 38ms 59ms 228ms 416ms 0 transport_latency_assumed tick_size_change f 3,396 4 46ms 90ms 209ms 433ms 0 transport_latency_assumed tick_size_change g 3,396 not meas. 81ms 115ms 377ms 854ms 0 transport_latency_assumed tick_size_change h 3,396 225 20ms 37ms 95ms 307ms 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-16/12/2026-09-16T12.parquet sha256sum 2026-09-16T12.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.