Hour audit: 2026-09-17T09
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-17T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T09:00:00.000164127+00:00 · last event 2026-09-17T09:59:59.999959556+00:00
VOLUME 112,316,211 rows · 1,168,053,486 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 111,978,834 · c: 111,959,977 · f: 111,945,346 · h: 111,884,996 · g: 111,869,404 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 544,411 (0.48%) · c: 106,183,070 (94.54%) · f: 256,645 (0.23%) · h: 5,251,051 (4.68%) · g: 81,034 (0.07%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,316,211 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5dbd9539d2d9b57c76e5d6ad176ac8336bd74c33511c5036b3ec94b3bd96135d
the corpus checksum ledger names this file with the same digest
joined 112,318,718 to merged 112,316,211, minus 2,507 (minus 0.0022%)
boundary drops 2,507 · 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-17T10:59:09Z 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 10,948,606 125,237,130 0-41 f8460a1ddad4384038324e9c752c218896f2440da9914aa08ab8b9c97693f277 book 500,080 49,717,402 42-43 3a8c8e9e31d5f44b3b909e18c9c3e62c0a8d71e5297938dd704d50bcf3e67f1e last_trade_price 53,600 3,026,017 44-44 4dbf5ecb493c765a34b2b2b8f1d128490ea1e43912e88e3d1eaa055954c0f6b4 market_resolved 553 92,194 45-45 ea7dc56f0d5b10c9549f5ce46d29318928e0827d593328d99601c037bfe97b9a new_market 684 74,318 46-46 27af830a55a19d8d825cc7ac1c30d998e1abf83fe0186ca7ae6dbe31258c784c price_change 100,810,140 988,535,673 47-431 325b4642c93bad3a82e7625cb21aca85a493777b154160cd0e157b3cc8123e9e tick_size_change 2,548 93,172 432-432 5baa8eb3e2942ca5859d69bd42882d642443781318a9cee238ffa681f414a808 EVENT MIX count share price_change 100,810,140 89.76% best_bid_ask 10,948,606 9.75% book 500,080 0.45% last_trade_price 53,600 0.05% tick_size_change 2,548 <0.01% new_market 684 <0.01% market_resolved 553 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,948,852 10,948,606 246 127 FULL book 500,082 500,080 2 139,957 FULL last_trade_price 53,601 53,600 1 2 FULL market_resolved 553 553 0 2 FULL new_market 684 684 0 0 FULL price_change 100,812,398 100,810,140 2,258 53 FULL tick_size_change 2,548 2,548 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,944,162 10,414,464 5ms 12ms 86ms 13.2s 0 transport_latency_assumed best_bid_ask e 10,945,306 36,820 38ms 44ms 136ms 6.6s 0 transport_latency_assumed best_bid_ask f 10,945,198 11,310 47ms 56ms 169ms 5.3s 0 transport_latency_assumed best_bid_ask g 10,944,892 1,444 77ms 94ms 241ms 11.1s 0 transport_latency_assumed best_bid_ask h 10,944,686 484,568 18ms 26ms 100ms 18.5s 0 transport_latency_assumed book c 207,725 182,788 37ms 28.6min 25.8d 110.5d 0 book_staleness book e 247,606 104,295 8.7s 33.2min 25.8d 110.5d 0 book_staleness book f 247,329 104,277 8.6s 33.3min 25.8d 110.5d 0 book_staleness book g 188,333 54,825 160ms 26.1min 25.8d 102.7d 0 book_staleness book h 179,852 53,895 36ms 25.2min 25.8d 110.5d 0 book_staleness last_trade_price c 53,331 50,041 11ms 52ms 262ms 12.5s 0 transport_latency_assumed last_trade_price e 53,196 476 46ms 148ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price f 53,153 184 54ms 147ms 786ms 5.0s 0 transport_latency_assumed last_trade_price g 53,128 55 91ms 255ms 5.0s 11.1s 0 transport_latency_assumed last_trade_price h 53,002 2,844 24ms 82ms 381ms 5.5s 0 transport_latency_assumed market_resolved c 553 536 6ms 11ms 197ms 594ms 0 transport_latency_assumed market_resolved e 552 not meas. 113ms 202ms 471ms 603ms 0 transport_latency_assumed market_resolved f 552 not meas. 119ms 205ms 457ms 797ms 0 transport_latency_assumed market_resolved g 551 not meas. 202ms 310ms 740ms 1.3s 0 transport_latency_assumed market_resolved h 552 17 39ms 72ms 147ms 458ms 0 transport_latency_assumed new_market c 478 251 75ms 15.1s 25.3s 1.1min 0 transport_latency_assumed new_market e 478 100 122ms 12.4s 19.0s 2.1min 0 transport_latency_assumed new_market f 478 54 133ms 12.9s 26.2s 58.6s 0 transport_latency_assumed new_market g 478 46 203ms 549ms 28.1s 28.4s 0 transport_latency_assumed new_market h 478 233 77ms 13.7s 19.2s 1.1min 0 transport_latency_assumed price_change c 100,751,180 95,532,550 6ms 14ms 107ms 13.5s 0 transport_latency_assumed price_change e 100,729,148 402,720 39ms 49ms 245ms 6.7s 0 transport_latency_assumed price_change f 100,696,088 140,820 47ms 61ms 254ms 6.2s 0 transport_latency_assumed price_change g 100,679,474 24,664 77ms 99ms 405ms 11.1s 0 transport_latency_assumed price_change h 100,703,878 4,709,386 18ms 29ms 148ms 18.8s 0 transport_latency_assumed tick_size_change c 2,548 2,440 5ms 10ms 50ms 257ms 0 transport_latency_assumed tick_size_change e 2,548 not meas. 39ms 80ms 118ms 197ms 0 transport_latency_assumed tick_size_change f 2,548 not meas. 47ms 58ms 260ms 439ms 0 transport_latency_assumed tick_size_change g 2,548 not meas. 76ms 92ms 182ms 307ms 0 transport_latency_assumed tick_size_change h 2,548 108 18ms 32ms 106ms 580ms 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/09/2026-09-17T09.parquet sha256sum 2026-09-17T09.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.