Hour audit: 2026-10-07T11
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-07T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T11:00:00.000146062+00:00 · last event 2026-10-07T11:59:59.999607993+00:00
VOLUME 131,435,811 rows · 1,554,467,530 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 130,747,278 · h: 130,733,919 · m: 130,710,248 · i: 130,301,118 · n: 130,188,526 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 63,406,944 (48.24%) · h: 1,658,826 (1.26%) · m: 65,413,683 (49.77%) · i: 716,165 (0.54%) · n: 240,193 (0.18%) (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 131,435,811 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 38905ba2a3c44812562077f200d9276b53c1b77ef658714671b8464ce4e56e9a
the corpus checksum ledger names this file with the same digest
joined 131,439,270 to merged 131,435,811, minus 3,459 (minus 0.0026%)
boundary drops 3,459 · 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-07T14:45:40Z 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 11,656,474 149,626,601 0-44 7cb94482b1b2de8ec5eb3861015bbab24b5016fa607969da4b120f62e2054446 book 1,226,115 92,071,743 45-49 baed853b19e1eecb7a5afe8fb212fbcba5eefbc99eeb2fa54620b9275a6ed425 last_trade_price 57,012 3,273,516 50-50 752eccbeddd106b127d1ca52a4b60a09f9606dc43098a19f992a183aeacb41eb market_resolved 756 125,693 51-51 5a62710c1b2d4ed4d3f0fc160079691fa80755e99922532c57927c281aa5be2c new_market 684 68,194 52-52 8c8a31f1c3ac4210709eb525ef029191c254eb68c162776afe0a4499d2900252 price_change 118,491,402 1,307,679,678 53-505 1145a9eb7d3294ebf15fdd838b0e00794058bedf635a56e12de1099fe7678b03 tick_size_change 3,368 124,326 506-506 bc8d2683e3099e112bf2efa0024ca0543604f4304d9a07a165731a040a9c2922 EVENT MIX count share price_change 118,491,402 90.15% best_bid_ask 11,656,474 8.87% book 1,226,115 0.93% last_trade_price 57,012 0.04% tick_size_change 3,368 <0.01% market_resolved 756 <0.01% new_market 684 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,656,599 11,656,474 125 62 FULL book 1,228,133 1,226,115 2,018 248,410 FULL last_trade_price 57,012 57,012 0 1 FULL market_resolved 756 756 0 0 FULL new_market 684 684 0 0 FULL price_change 118,492,718 118,491,402 1,316 34 FULL tick_size_change 3,368 3,368 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,653,197 106,309 19ms 32ms 146ms 51.4s 0 transport_latency_assumed best_bid_ask i 11,654,901 57,387 22ms 36ms 144ms 6.2s 0 transport_latency_assumed best_bid_ask m 11,654,220 5,866,647 5ms 17ms 89ms 3.0s 0 transport_latency_assumed best_bid_ask n 11,648,380 2,921 44ms 68ms 291ms 24.9s 0 transport_latency_assumed best_bid_ask o 11,653,782 5,623,210 5ms 17ms 91ms 3.5s 0 transport_latency_assumed book h 620,425 359,629 10.3min 1.7d 45.9d 130.5d 0 book_staleness book i 189,498 48,039 99ms 12.5h 31.9d 130.5d 0 book_staleness book m 601,529 317,371 9.0min 1.7d 45.9d 130.6d 0 book_staleness book n 510,221 188,201 7.0min 1.6d 45.9d 130.6d 0 book_staleness book o 601,687 312,875 8.9min 1.7d 45.9d 130.6d 0 book_staleness last_trade_price h 56,828 661 21ms 108ms 710ms 50.4s 0 transport_latency_assumed last_trade_price i 56,768 266 27ms 277ms 3.0s 6.2s 0 transport_latency_assumed last_trade_price m 56,936 27,264 7ms 28ms 169ms 1.5s 0 transport_latency_assumed last_trade_price n 55,354 54 58ms 2.1s 12.5s 24.9s 0 transport_latency_assumed last_trade_price o 56,902 28,767 7ms 28ms 172ms 1.5s 0 transport_latency_assumed market_resolved h 756 1 20ms 24.2s 38.9s 41.3s 0 transport_latency_assumed market_resolved i 756 45 24ms 23.8s 37.7s 40.5s 0 transport_latency_assumed market_resolved m 756 406 7ms 23.8s 37.7s 40.5s 0 transport_latency_assumed market_resolved n 756 not meas. 46ms 39.5s 53.7s 56.5s 0 transport_latency_assumed market_resolved o 756 304 7ms 27.1s 41.0s 43.7s 0 transport_latency_assumed new_market h 429 86 94ms 16.1s 48.7s 1.7min 0 transport_latency_assumed new_market i 429 168 78ms 13.3s 14.8s 1.6min 0 transport_latency_assumed new_market m 429 187 43ms 15.2s 1.2min 1.7min 0 transport_latency_assumed new_market n 429 63 89ms 16.9s 1.5min 1.7min 0 transport_latency_assumed new_market o 429 180 44ms 15.4s 50.2s 1.7min 0 transport_latency_assumed price_change h 118,398,916 1,192,108 19ms 38ms 265ms 57.0s 0 transport_latency_assumed price_change i 118,395,398 610,236 22ms 48ms 612ms 6.2s 0 transport_latency_assumed price_change m 118,393,010 59,200,034 6ms 19ms 104ms 3.3s 0 transport_latency_assumed price_change n 117,970,018 48,954 45ms 103ms 3.9s 24.9s 0 transport_latency_assumed price_change o 118,430,354 57,440,070 6ms 19ms 105ms 3.5s 0 transport_latency_assumed tick_size_change h 3,368 32 19ms 35ms 155ms 251ms 0 transport_latency_assumed tick_size_change i 3,368 24 22ms 39ms 125ms 837ms 0 transport_latency_assumed tick_size_change m 3,368 1,774 6ms 17ms 58ms 139ms 0 transport_latency_assumed tick_size_change n 3,368 not meas. 44ms 65ms 163ms 8.1s 0 transport_latency_assumed tick_size_change o 3,368 1,538 6ms 19ms 69ms 169ms 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/11/2026-10-07T11.parquet sha256sum 2026-10-07T11.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.