Hour audit: 2026-09-10T23
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-10T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T23:00:00.000046536+00:00 · last event 2026-09-10T23:59:59.999978422+00:00
VOLUME 110,680,094 rows · 1,140,168,915 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 109,702,766 · f: 109,559,102 · e: 109,450,970 · h: 109,418,146 · c: 101,331,705 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 50,683 (0.05%) · f: 263,077 (0.24%) · e: 1,024,984 (0.93%) · h: 12,983,194 (11.73%) · c: 96,358,156 (87.06%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,680,094 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f4c45a68134d285aa621ea1498d5fe4b848784a520650c7975f1927424599446
the corpus checksum ledger names this file with the same digest
joined 110,683,232 to merged 110,680,094, minus 3,138 (minus 0.0028%)
boundary drops 3,138 · 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-11T01:00:22Z 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,546,814 115,723,728 0-40 44cbb54747e03e5341e5e31a182f97e0ae25734e4a9de21e749c3c6d7943aa7c book 935,336 67,283,421 41-44 fffaa146ddde0e167b544361b265c459d2aef13de67ba2fd2858b4b8deef592c last_trade_price 48,287 2,694,980 45-45 996e3ebafa2cb90bb4f30845054a7a972b446baf8f11cedc67e6f334d3fcec67 market_resolved 1,148 131,505 46-46 9db40d75a6a0bc701cb7a388dc41e0ede38fba0862ba48834f9a5eddbfaec9d8 new_market 951 97,654 47-47 5ef2ef8331b0581fd89249d2cc7f817d1860298c7ddc753f4542d9cb09b3491c price_change 99,144,550 952,864,180 48-426 7390bb9585afa3b68f64c69023fbd07cec5f6ee1c1d74714cee43f1ddf3fa00b tick_size_change 3,008 110,724 427-427 834c14d5b24524e7bca3e0edbb40ba01d59b9216877dd5eac6de3880a6c839f2 EVENT MIX count share price_change 99,144,550 89.58% best_bid_ask 10,546,814 9.53% book 935,336 0.85% last_trade_price 48,287 0.04% tick_size_change 3,008 <0.01% market_resolved 1,148 <0.01% new_market 951 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,546,984 10,546,814 170 1,360 FULL book 935,342 935,336 6 203,211 FULL last_trade_price 48,287 48,287 0 140 FULL market_resolved 1,148 1,148 0 6 FULL new_market 951 951 0 0 FULL price_change 99,147,512 99,144,550 2,962 964 FULL tick_size_change 3,008 3,008 0 73 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,608,461 9,167,761 5ms 11ms 121ms 4.5s 0 transport_latency_assumed best_bid_ask e 10,544,847 90,375 39ms 46ms 165ms 6.2s 0 transport_latency_assumed best_bid_ask f 10,544,421 18,899 45ms 56ms 188ms 6.1s 0 transport_latency_assumed best_bid_ask g 10,543,844 1,983 79ms 98ms 336ms 10.9s 0 transport_latency_assumed best_bid_ask h 10,545,591 1,267,796 18ms 26ms 136ms 42.3s 0 transport_latency_assumed book c 915,012 906,676 18.4min 1.1d 30.2d 104.0d 0 book_staleness book e 101,930 2,433 41ms 169ms 3.8s 85.5d 0 book_staleness book f 104,098 2,941 48ms 235ms 5.7h 81.6d 0 book_staleness book g 115,845 7,754 92ms 1.2min 2.1d 85.6d 0 book_staleness book h 101,826 15,532 21ms 69ms 4.5s 39.5d 0 book_staleness last_trade_price c 42,998 40,389 10ms 45ms 230ms 4.9s 0 transport_latency_assumed last_trade_price e 48,170 556 47ms 155ms 1.5s 6.3s 0 transport_latency_assumed last_trade_price f 48,007 191 54ms 171ms 1.2s 6.1s 0 transport_latency_assumed last_trade_price g 48,045 32 96ms 328ms 4.3s 10.8s 0 transport_latency_assumed last_trade_price h 48,118 7,119 23ms 73ms 312ms 8.6s 0 transport_latency_assumed market_resolved c 1,069 1,041 6ms 11.6min 12.4min 12.6min 0 transport_latency_assumed market_resolved e 790 13 40ms 118ms 318ms 449ms 0 transport_latency_assumed market_resolved f 790 2 47ms 126ms 348ms 608ms 0 transport_latency_assumed market_resolved g 790 not meas. 87ms 241ms 540ms 823ms 0 transport_latency_assumed market_resolved h 790 92 20ms 60ms 150ms 59.0s 0 transport_latency_assumed new_market c 692 367 167ms 5.9min 7.9min 8.0min 0 transport_latency_assumed new_market e 618 160 193ms 16.2s 26.2s 57.7s 0 transport_latency_assumed new_market f 618 58 226ms 10.5s 26.6s 28.4s 0 transport_latency_assumed new_market g 618 84 333ms 18.6s 23.8s 1.2min 0 transport_latency_assumed new_market h 618 282 147ms 12.0s 20.1s 56.0s 0 transport_latency_assumed price_change c 90,760,757 86,239,371 5ms 13ms 172ms 4.8s 0 transport_latency_assumed price_change e 98,751,607 931,438 39ms 52ms 272ms 6.3s 0 transport_latency_assumed price_change f 98,858,160 240,982 45ms 63ms 297ms 6.1s 0 transport_latency_assumed price_change g 98,990,616 40,830 79ms 111ms 586ms 11.8s 0 transport_latency_assumed price_change h 98,718,195 11,691,929 18ms 30ms 192ms 42.8s 0 transport_latency_assumed tick_size_change c 2,716 2,551 5ms 18ms 129ms 388ms 0 transport_latency_assumed tick_size_change e 3,008 9 39ms 47ms 119ms 446ms 0 transport_latency_assumed tick_size_change f 3,008 4 45ms 57ms 127ms 883ms 0 transport_latency_assumed tick_size_change g 3,008 not meas. 79ms 96ms 260ms 510ms 0 transport_latency_assumed tick_size_change h 3,008 444 18ms 35ms 95ms 200ms 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-10/23/2026-09-10T23.parquet sha256sum 2026-09-10T23.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.