Hour audit: 2026-09-10T10
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-10T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T10:00:00.000128506+00:00 · last event 2026-09-10T10:59:59.998615657+00:00
VOLUME 107,072,445 rows · 1,122,951,746 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 106,310,135 · f: 106,305,449 · h: 106,127,727 · g: 106,099,625 · c: 97,392,377 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 647,513 (0.60%) · f: 235,947 (0.22%) · h: 12,635,558 (11.80%) · g: 36,224 (0.03%) · c: 93,517,203 (87.34%) (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 107,072,445 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2f1c2c93a4a746dfcbf3f5b8c34c07b1553c40f493507089060fb8f605d679c4
the corpus checksum ledger names this file with the same digest
joined 107,074,702 to merged 107,072,445, minus 2,257 (minus 0.0021%)
boundary drops 2,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-10T11:59:23Z 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,096,690 109,834,892 0-38 e1b8954e8c7ba6bee278be55d2c43dd1059ffa2a16f9db9cf0d61af5cd0e051c book 1,035,114 73,476,161 39-42 0cbac4e0e6f9f252c337e232bdcebd59758df8b22b86db0c68b3930274118fd3 last_trade_price 56,198 3,164,988 43-43 cd93ea287a828e78891cb9c566c5d315b37a8d0810dc7f76cb61869453ba961d market_resolved 982 133,137 44-44 29242345b1bb4d73b9a320fada24da6992aa3a2a6cb7c9d06776aabf7c41efb8 new_market 983 109,983 45-45 0e4c80efaf6a1c169ec5f46e614af8111f829c1a61d530352635080d2d794f3d price_change 95,879,242 934,895,500 46-411 c043e345837e7c3eb7a2787d33fb86100f909171f9fac790568117b045f2bb23 tick_size_change 3,236 118,196 412-412 871ecfd49b829dbae1c6faf6175b59e3ddbc2fc03439a80b782ae76496dbc398 EVENT MIX count share price_change 95,879,242 89.55% best_bid_ask 10,096,690 9.43% book 1,035,114 0.97% last_trade_price 56,198 0.05% tick_size_change 3,236 <0.01% new_market 983 <0.01% market_resolved 982 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,096,910 10,096,690 220 1,144 FULL book 1,035,160 1,035,114 46 194,116 FULL last_trade_price 56,199 56,198 1 147 FULL market_resolved 982 982 0 0 FULL new_market 983 983 0 0 FULL price_change 95,881,232 95,879,242 1,990 1,404 FULL tick_size_change 3,236 3,236 0 84 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,165,696 8,814,489 5ms 10ms 94ms 5.1s 0 transport_latency_assumed best_bid_ask e 10,092,591 51,521 38ms 44ms 152ms 4.1s 0 transport_latency_assumed best_bid_ask f 10,092,840 14,302 46ms 55ms 175ms 6.9s 0 transport_latency_assumed best_bid_ask g 10,093,899 2,099 77ms 96ms 306ms 17.0s 0 transport_latency_assumed best_bid_ask h 10,094,840 1,214,279 18ms 25ms 126ms 7.8s 0 transport_latency_assumed book c 893,741 886,031 12.7min 1.1d 29.6d 103.5d 0 book_staleness book e 328,061 64,909 1.4min 15.2h 18.9d 103.5d 0 book_staleness book f 337,089 63,017 1.5min 15.5h 18.9d 103.5d 0 book_staleness book g 125,943 4,784 86ms 906ms 18.8h 103.5d 0 book_staleness book h 118,856 16,373 22ms 95ms 13.8min 84.8d 0 book_staleness last_trade_price c 50,538 47,721 10ms 46ms 225ms 5.0s 0 transport_latency_assumed last_trade_price e 55,777 584 47ms 171ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 55,882 362 56ms 199ms 2.7s 6.9s 0 transport_latency_assumed last_trade_price g 55,843 216 93ms 261ms 2.2s 17.3s 0 transport_latency_assumed last_trade_price h 55,845 7,315 24ms 88ms 452ms 5.4s 0 transport_latency_assumed market_resolved c 853 814 5ms 5.0min 6.2min 6.2min 0 transport_latency_assumed market_resolved e 816 42 39ms 190ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 816 2 47ms 200ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 816 7 84ms 242ms 606ms 1.1s 0 transport_latency_assumed market_resolved h 816 117 18ms 97ms 1.0min 1.0min 0 transport_latency_assumed new_market c 714 395 79ms 15.0s 36.6s 4.4min 0 transport_latency_assumed new_market e 714 141 131ms 15.4s 31.5s 1.3min 0 transport_latency_assumed new_market f 714 114 181ms 17.3s 32.1s 1.3min 0 transport_latency_assumed new_market g 714 54 260ms 528ms 30.8s 37.2s 0 transport_latency_assumed new_market h 714 279 88ms 13.3s 36.0s 1.2min 0 transport_latency_assumed price_change c 87,277,935 83,764,881 5ms 12ms 108ms 6.3s 0 transport_latency_assumed price_change e 95,828,940 530,310 38ms 49ms 221ms 4.2s 0 transport_latency_assumed price_change f 95,814,872 158,150 46ms 60ms 251ms 6.9s 0 transport_latency_assumed price_change g 95,819,174 29,064 78ms 107ms 427ms 17.1s 0 transport_latency_assumed price_change h 95,853,420 11,396,837 18ms 27ms 154ms 8.2s 0 transport_latency_assumed tick_size_change c 2,900 2,872 5ms 8ms 22ms 40ms 0 transport_latency_assumed tick_size_change e 3,236 6 38ms 61ms 111ms 164ms 0 transport_latency_assumed tick_size_change f 3,236 not meas. 46ms 51ms 81ms 127ms 0 transport_latency_assumed tick_size_change g 3,236 not meas. 78ms 91ms 189ms 312ms 0 transport_latency_assumed tick_size_change h 3,236 358 18ms 27ms 49ms 159ms 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/10/2026-09-10T10.parquet sha256sum 2026-09-10T10.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.