Hour audit: 2026-09-17T04
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-17T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T04:00:00.000200804+00:00 · last event 2026-09-17T04:59:59.999655346+00:00
VOLUME 111,104,252 rows · 1,096,178,451 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,026,193 · f: 110,987,890 · h: 110,980,574 · e: 110,966,898 · g: 110,939,334 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,726,296 (95.16%) · f: 334,564 (0.30%) · h: 4,312,477 (3.88%) · e: 645,371 (0.58%) · g: 85,544 (0.08%) (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 111,104,252 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 12996f62d343ec8d327cd4740dd96f90c3c6cbb1b68be05f7e64e931622608a9
the corpus checksum ledger names this file with the same digest
joined 111,107,127 to merged 111,104,252, minus 2,875 (minus 0.0026%)
boundary drops 2,875 · 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-17T05:58:34Z 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 13,281,433 145,791,227 0-50 6645554b465976bd0e5d631af76801c0a55457364ece6ef3b813298e27ffeaaf book 142,198 15,036,828 51-51 ce30107ff060b2bd9334433fae8c74eea175696975c52047ed0c004d08b3042f last_trade_price 40,627 2,350,312 52-52 85569b475e70a4819facece015c2cdfbf8484dedc36b92a6c2677af48efd84e5 market_resolved 1,427 234,744 53-53 7f572124a395e0d58c8b88ac58b113e52c0d90144e50965a18698841ee582aff new_market 3,329 315,787 54-54 4aeccd7ae57c5be081c181fe793d57e4296161f554736b303448dc46f45a8aa0 price_change 97,631,578 931,051,668 55-427 d3cb5948d09fc0e6948987e03ebfb02b5ff43db928244e2682e050a10377d990 tick_size_change 3,660 133,080 428-428 97f90a69faa115c8a99e752258806be3ae79c658f6ec11f38b31f7ebf725174c EVENT MIX count share price_change 97,631,578 87.87% best_bid_ask 13,281,433 11.95% book 142,198 0.13% last_trade_price 40,627 0.04% tick_size_change 3,660 <0.01% new_market 3,329 <0.01% market_resolved 1,427 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,281,731 13,281,433 298 280 FULL book 142,886 142,198 688 23,119 FULL last_trade_price 40,628 40,627 1 0 FULL market_resolved 1,427 1,427 0 0 FULL new_market 3,329 3,329 0 0 FULL price_change 97,633,466 97,631,578 1,888 54 FULL tick_size_change 3,660 3,660 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,280,263 12,710,058 5ms 9ms 179ms 14.2s 0 transport_latency_assumed best_bid_ask e 13,277,840 70,937 39ms 46ms 235ms 8.2s 0 transport_latency_assumed best_bid_ask f 13,278,495 31,457 46ms 56ms 268ms 6.4s 0 transport_latency_assumed best_bid_ask g 13,277,664 5,720 79ms 100ms 470ms 17.6s 0 transport_latency_assumed best_bid_ask h 13,278,572 463,261 17ms 24ms 380ms 39.5s 0 transport_latency_assumed book c 101,395 93,137 7ms 1.1min 7.8d 91.7d 0 book_staleness book e 97,235 11,255 42ms 6.1s 4.3d 91.7d 0 book_staleness book f 91,339 5,114 48ms 507ms 28.2min 110.2d 0 book_staleness book g 107,762 19,820 87ms 4.5min 9.7d 110.2d 0 book_staleness book h 94,022 12,872 21ms 2.4s 7.0h 110.3d 0 book_staleness last_trade_price c 40,487 38,117 10ms 48ms 276ms 4.9s 0 transport_latency_assumed last_trade_price e 40,385 284 47ms 122ms 1.7s 8.2s 0 transport_latency_assumed last_trade_price f 40,454 132 53ms 130ms 871ms 6.4s 0 transport_latency_assumed last_trade_price g 40,364 41 91ms 220ms 3.7s 17.7s 0 transport_latency_assumed last_trade_price h 40,306 2,053 23ms 68ms 724ms 12.0s 0 transport_latency_assumed market_resolved c 1,427 1,370 5ms 12ms 309ms 1.2s 0 transport_latency_assumed market_resolved e 1,427 5 112ms 199ms 575ms 899ms 0 transport_latency_assumed market_resolved f 1,427 3 118ms 199ms 548ms 1.2s 0 transport_latency_assumed market_resolved g 1,427 not meas. 201ms 337ms 927ms 1.3s 0 transport_latency_assumed market_resolved h 1,427 49 37ms 67ms 483ms 2.7s 0 transport_latency_assumed new_market c 2,045 1,294 88ms 20.0s 1.4min 12.5min 0 transport_latency_assumed new_market e 2,045 624 153ms 20.4s 1.5min 14.3min 0 transport_latency_assumed new_market f 2,045 432 199ms 20.7s 1.4min 3.4min 0 transport_latency_assumed new_market g 2,045 207 280ms 20.7s 1.6min 8.1min 0 transport_latency_assumed new_market h 2,045 772 160ms 20.8s 1.4min 9.4min 0 transport_latency_assumed price_change c 97,596,916 92,878,784 5ms 11ms 245ms 14.9s 0 transport_latency_assumed price_change e 97,544,306 562,266 40ms 53ms 400ms 8.2s 0 transport_latency_assumed price_change f 97,570,470 297,422 46ms 63ms 412ms 6.5s 0 transport_latency_assumed price_change g 97,506,412 59,756 80ms 110ms 689ms 17.8s 0 transport_latency_assumed price_change h 97,560,542 3,833,350 18ms 28ms 517ms 41.6s 0 transport_latency_assumed tick_size_change c 3,660 3,536 5ms 8ms 71ms 352ms 0 transport_latency_assumed tick_size_change e 3,660 not meas. 39ms 64ms 229ms 1.4s 0 transport_latency_assumed tick_size_change f 3,660 4 46ms 52ms 123ms 1.3s 0 transport_latency_assumed tick_size_change g 3,660 not meas. 78ms 94ms 265ms 2.6s 0 transport_latency_assumed tick_size_change h 3,660 120 17ms 22ms 67ms 2.7s 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-17/04/2026-09-17T04.parquet sha256sum 2026-09-17T04.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.