Hour audit: 2026-10-06T06
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-10-06T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T06:00:00.000012184+00:00 · last event 2026-10-06T06:59:59.999982486+00:00
VOLUME 106,335,478 rows · 1,212,905,178 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 105,798,555 · m: 105,788,065 · h: 105,776,355 · n: 105,605,705 · i: 105,524,935 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 50,855,070 (47.83%) · m: 53,755,501 (50.55%) · h: 793,961 (0.75%) · n: 268,871 (0.25%) · i: 662,075 (0.62%) (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 106,335,478 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1bf5e9e6c9eeceac117b04db433333bb9cb73f1636ea8a81efe0c62130a041c9
the corpus checksum ledger names this file with the same digest
joined 106,357,200 to merged 106,335,478, minus 21,722 (minus 0.0204%)
boundary drops 21,722 · 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-10-06T07:59:05Z as himno
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,594,314 134,152,624 0-40 2fd5e36a66384f9c7a5b8f27901092417be5b896ca5237c8230056e8230181b8 book 767,817 63,794,241 41-43 bc80b49662505a51a8e7a443b74ae63f470b2462d0e11b4cb927d74e08735dc6 last_trade_price 43,732 2,543,000 44-44 3cbd398725b82428a8a27d4dce957a4d4d410ed665039a36bd36223966dcd013 market_resolved 813 134,828 45-45 2341a3a729182fd268040d28b6db4c9f21900123a719163b585f9d2b27009c71 new_market 3,506 344,069 46-46 e45a8df4522e4bc6135665e7a321660df58ba54533868a5bae529949bf3befd3 price_change 94,923,168 1,010,642,176 47-409 8496630c91d2778c24e9c4be7aa899748c2457a1c066448c24e6d71d10004032 tick_size_change 2,128 80,298 410-410 d3182dfde700b741ef8904494d63477c9e65690387e731c5b1418f5fd9f0ac48 EVENT MIX count share price_change 94,923,168 89.27% best_bid_ask 10,594,314 9.96% book 767,817 0.72% last_trade_price 43,732 0.04% new_market 3,506 <0.01% tick_size_change 2,128 <0.01% market_resolved 813 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,596,344 10,594,314 2,030 236 FULL book 770,503 767,817 2,686 213,933 FULL last_trade_price 43,734 43,732 2 0 FULL market_resolved 813 813 0 7 FULL new_market 3,506 3,506 0 0 FULL price_change 94,940,172 94,923,168 17,004 42 FULL tick_size_change 2,128 2,128 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,590,677 53,232 18ms 33ms 889ms 2.2min 0 transport_latency_assumed best_bid_ask i 10,591,005 57,213 21ms 29ms 226ms 13.6s 0 transport_latency_assumed best_bid_ask m 10,591,749 5,383,904 4ms 12ms 166ms 7.0s 0 transport_latency_assumed best_bid_ask n 10,588,617 5,541 43ms 57ms 420ms 21.8s 0 transport_latency_assumed best_bid_ask o 10,592,003 5,094,424 4ms 12ms 166ms 6.0s 0 transport_latency_assumed book h 328,261 178,483 3.9min 21.2h 44.7d 129.4d 0 book_staleness book i 107,333 11,738 25ms 3.4min 8.1d 129.4d 0 book_staleness book m 291,723 203,783 2.6min 20.6h 44.7d 129.4d 0 book_staleness book n 328,557 185,557 3.9min 21.2h 44.7d 129.4d 0 book_staleness book o 289,521 188,256 2.7min 20.7h 44.7d 129.4d 0 book_staleness last_trade_price h 43,510 350 22ms 135ms 3.4s 1.3min 0 transport_latency_assumed last_trade_price i 43,390 199 23ms 186ms 2.5s 13.6s 0 transport_latency_assumed last_trade_price m 43,533 23,762 5ms 21ms 236ms 3.7s 0 transport_latency_assumed last_trade_price n 42,762 20 47ms 375ms 5.7s 21.8s 0 transport_latency_assumed last_trade_price o 43,622 19,401 6ms 24ms 243ms 3.3s 0 transport_latency_assumed market_resolved h 807 2 20ms 132ms 24.0s 26.8s 0 transport_latency_assumed market_resolved i 809 27 22ms 117ms 17.4s 20.2s 0 transport_latency_assumed market_resolved m 808 432 5ms 13ms 25.5s 28.3s 0 transport_latency_assumed market_resolved n 809 2 45ms 248ms 43.0s 44.9s 0 transport_latency_assumed market_resolved o 807 350 5ms 15ms 36.6s 39.4s 0 transport_latency_assumed new_market h 2,270 644 9.1s 2.6min 2.8min 2.8min 0 transport_latency_assumed new_market i 2,270 506 21.9s 2.6min 2.8min 2.9min 0 transport_latency_assumed new_market m 2,270 1,156 8.9s 2.6min 2.8min 2.9min 0 transport_latency_assumed new_market n 2,270 559 407ms 2.5min 2.8min 2.8min 0 transport_latency_assumed new_market o 2,270 641 12.9s 2.6min 2.8min 2.9min 0 transport_latency_assumed price_change h 94,808,706 561,238 19ms 44ms 1.1s 2.3min 0 transport_latency_assumed price_change i 94,778,000 592,384 21ms 37ms 481ms 13.6s 0 transport_latency_assumed price_change m 94,855,854 48,141,390 4ms 14ms 215ms 7.5s 0 transport_latency_assumed price_change n 94,640,562 77,192 44ms 79ms 1.1s 23.7s 0 transport_latency_assumed price_change o 94,868,204 45,550,964 4ms 14ms 215ms 9.6s 0 transport_latency_assumed tick_size_change h 2,124 12 18ms 34ms 279ms 19.0s 0 transport_latency_assumed tick_size_change i 2,128 8 21ms 46ms 134ms 278ms 0 transport_latency_assumed tick_size_change m 2,128 1,074 4ms 12ms 57ms 122ms 0 transport_latency_assumed tick_size_change n 2,128 not meas. 43ms 60ms 247ms 338ms 0 transport_latency_assumed tick_size_change o 2,128 1,034 4ms 10ms 50ms 228ms 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-10-06/06/2026-10-06T06.parquet sha256sum 2026-10-06T06.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.