Hour audit: 2026-10-07T21
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-07T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T21:00:00.000039237+00:00 · last event 2026-10-07T21:59:59.999970287+00:00
VOLUME 92,558,482 rows · 1,060,458,771 bytes (1011.33 MiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 92,204,480 · m: 92,173,816 · h: 92,154,576 · i: 92,113,098 · n: 91,982,646 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 46,648,391 (50.40%) · m: 44,374,799 (47.94%) · h: 666,969 (0.72%) · i: 696,100 (0.75%) · n: 172,223 (0.19%) (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 92,558,482 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f7452bd8c04bf8bd332cc53290f9d0448d8fde74ee98d8326d053d4054349226
the corpus checksum ledger names this file with the same digest
joined 92,560,878 to merged 92,558,482, minus 2,396 (minus 0.0026%)
boundary drops 2,396 · 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-07T22:57:56Z 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 8,709,480 111,965,204 0-33 bbb2e779c58c09260c6ad411ad9e901995dd5f656f0139ff4bed073f07dc94e0 book 531,839 51,254,859 34-36 d363d9e05e772c08a183e95e255fe3035a8350feaae40ed658ed30bffe457b90 last_trade_price 43,503 2,523,985 37-37 0fb51bad1270d1239d78375bfab6180b8d9d1b5e8f4e4d74bc8e7b71fab04519 market_resolved 566 92,128 38-38 77341e50e1b2f2e961e98351aa8c64f47fed81f5802f5cda2f51c4279961150e new_market 3,486 318,312 39-39 8c74fe86b97bd04938898f2c04455fe32805edae85eff0e01663ed5e1f4986ad price_change 83,267,284 893,156,607 40-357 476563ca5bf2f443c671f1878d07e8b0a80565565917d85175d34dc4b4dc9e2c tick_size_change 2,324 86,766 358-358 5127479bb5a6a259fcae455de5a8396ae5fc71db46bfc4827c90b0a3e4a9559f EVENT MIX count share price_change 83,267,284 89.96% best_bid_ask 8,709,480 9.41% book 531,839 0.57% last_trade_price 43,503 0.05% new_market 3,486 <0.01% tick_size_change 2,324 <0.01% market_resolved 566 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,709,546 8,709,480 66 198 FULL book 533,109 531,839 1,270 175,779 FULL last_trade_price 43,503 43,503 0 0 FULL market_resolved 566 566 0 0 FULL new_market 3,486 3,486 0 0 FULL price_change 83,268,344 83,267,284 1,060 73 FULL tick_size_change 2,324 2,324 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,707,002 43,374 18ms 27ms 557ms 2.2min 0 transport_latency_assumed best_bid_ask i 8,707,239 55,655 21ms 28ms 199ms 6.2s 0 transport_latency_assumed best_bid_ask m 8,707,209 4,144,350 4ms 11ms 171ms 7.4s 0 transport_latency_assumed best_bid_ask n 8,705,288 3,846 43ms 59ms 466ms 24.6s 0 transport_latency_assumed best_bid_ask o 8,707,578 4,462,255 4ms 11ms 184ms 11.8s 0 transport_latency_assumed book h 223,015 111,647 46.6s 20.9h 43.1d 131.0d 0 book_staleness book i 136,211 33,757 64ms 5.4h 30.5d 130.9d 0 book_staleness book m 201,962 132,389 19.0s 14.4h 43.1d 131.0d 0 book_staleness book n 223,670 107,606 53.6s 18.2h 43.1d 131.0d 0 book_staleness book o 212,976 146,440 35.8s 16.5h 43.1d 131.0d 0 book_staleness last_trade_price h 43,411 238 20ms 268ms 1.1s 58.9s 0 transport_latency_assumed last_trade_price i 43,302 238 25ms 346ms 1.4s 6.1s 0 transport_latency_assumed last_trade_price m 43,317 20,462 6ms 24ms 251ms 3.1s 0 transport_latency_assumed last_trade_price n 42,824 36 55ms 1.7s 9.2s 24.6s 0 transport_latency_assumed last_trade_price o 43,346 22,529 6ms 25ms 242ms 3.4s 0 transport_latency_assumed market_resolved h 562 2 21ms 458ms 43.8s 51.2s 0 transport_latency_assumed market_resolved i 562 26 23ms 20.4s 34.0s 57.6s 0 transport_latency_assumed market_resolved m 562 244 5ms 79ms 36.1s 43.0s 0 transport_latency_assumed market_resolved n 562 not meas. 46ms 569ms 50.4s 57.7s 0 transport_latency_assumed market_resolved o 562 294 5ms 20.4s 34.1s 57.6s 0 transport_latency_assumed new_market h 2,036 388 197ms 31.5s 2.1min 2.5min 0 transport_latency_assumed new_market i 2,036 394 118ms 35.4s 2.5min 2.8min 0 transport_latency_assumed new_market m 2,036 1,123 75ms 33.9s 2.3min 2.8min 0 transport_latency_assumed new_market n 2,036 439 175ms 33.6s 2.3min 2.8min 0 transport_latency_assumed new_market o 2,036 1,142 87ms 37.3s 2.1min 2.5min 0 transport_latency_assumed price_change h 83,176,226 511,316 18ms 38ms 768ms 2.2min 0 transport_latency_assumed price_change i 83,221,424 606,022 21ms 39ms 571ms 6.3s 0 transport_latency_assumed price_change m 83,216,406 40,075,156 4ms 13ms 224ms 7.7s 0 transport_latency_assumed price_change n 83,005,942 60,296 43ms 105ms 2.7s 24.6s 0 transport_latency_assumed price_change o 83,235,658 42,014,494 4ms 13ms 231ms 12.0s 0 transport_latency_assumed tick_size_change h 2,324 4 17ms 24ms 69ms 28.8s 0 transport_latency_assumed tick_size_change i 2,324 8 21ms 26ms 58ms 274ms 0 transport_latency_assumed tick_size_change m 2,324 1,075 4ms 9ms 33ms 66ms 0 transport_latency_assumed tick_size_change n 2,324 not meas. 43ms 52ms 114ms 216ms 0 transport_latency_assumed tick_size_change o 2,324 1,237 4ms 9ms 29ms 68ms 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-07/21/2026-10-07T21.parquet sha256sum 2026-10-07T21.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.