Hour audit: 2026-10-03T23
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-03T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T23:00:00.000270072+00:00 · last event 2026-10-03T23:59:59.999971591+00:00
VOLUME 147,934,665 rows · 1,716,075,817 bytes (1.60 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 143,708,984 · m: 143,668,582 · i: 124,979,322 · g: 111,471,902 · k: 94,749,883 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,927,343 (2.65%) · m: 131,516,892 (88.90%) · i: 2,280,090 (1.54%) · g: 719,242 (0.49%) · k: 9,491,098 (6.42%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 9a216d77c1b4b1b9d175b80a32f528a75454756141e88974c74cac6567278ca7
the corpus checksum ledger names this file with the same digest
joined 147,960,604 to merged 147,934,665, minus 25,939 (minus 0.0175%)
boundary drops 25,939 · 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-04T01:52:39Z as ghikm
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 13,044,528 158,143,150 0-49 9f247e75918e4835d301ee2bd370fd2e7cd78d1ab0a442c8b4eb8eef89ea84ab book 4,478,741 144,058,456 50-67 0acf90cd7258913e479377a1b4d6aaeb81084511c7b6e260dda14b748e3e9a1b last_trade_price 70,620 3,986,844 68-68 fa0d3acc73f94ef5a662a4f438ca5222584e6af29790db4c160c376d40f388af market_resolved 22,614 966,033 69-69 615e7b7eebd26440872c0c1f4d40feb3eac5dcc06547480a212ef683ec56290a new_market 27,336 914,737 70-70 6994ee082f848a8bee710085b6500239b49c8a4be0f2524e5aa50a09cbced390 price_change 130,278,166 1,405,869,538 71-567 89ed857068e30ea3fd66d49e101a5404dd5e8e59bd947c609d1b0b8700f9635c tick_size_change 12,660 456,976 568-568 ac5211a05373f96297be3e44fdecd282ba4d055c2b7144c4e93e344b2b10e312 EVENT MIX count share price_change 130,278,166 88.06% best_bid_ask 13,044,528 8.82% book 4,478,741 3.03% last_trade_price 70,620 0.05% new_market 27,336 0.02% market_resolved 22,614 0.02% tick_size_change 12,660 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,046,276 13,044,528 1,748 13,399 FULL book 4,482,223 4,478,741 3,482 208,827 FULL last_trade_price 70,622 70,620 2 1,495 FULL market_resolved 22,615 22,614 1 903 FULL new_market 27,894 27,336 558 1,467 FULL price_change 130,298,310 130,278,166 20,144 12,301 FULL tick_size_change 12,664 12,660 4 1,832 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,920,526 3,506 83ms 170ms 1.0s 24.9s 0 transport_latency_assumed best_bid_ask h 13,040,803 348,005 19ms 40ms 809ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,174,054 178,774 21ms 38ms 283ms 13.8s 0 transport_latency_assumed best_bid_ask k 8,282,394 553,958 14ms 32ms 258ms 58.6s 0 transport_latency_assumed best_bid_ask m 13,042,126 11,960,285 5ms 18ms 146ms 7.1s 0 transport_latency_assumed book g 2,496,145 680,670 36.3min 2.0d 42.5d 127.1d 0 book_staleness book h 344,529 82,216 29.5s 17.4h 42.4d 127.1d 0 book_staleness book i 1,554,806 250,360 28.0min 1.9d 42.4d 127.1d 0 book_staleness book k 3,623,677 3,288,339 41.3min 2.2d 45.9d 127.1d 0 book_staleness book m 281,536 177,156 160ms 9.1h 35.1d 127.1d 0 book_staleness last_trade_price g 55,255 10 92ms 1.5s 14.1s 23.9s 0 transport_latency_assumed last_trade_price h 70,390 2,748 21ms 90ms 697ms 52.7s 0 transport_latency_assumed last_trade_price i 59,422 1,267 24ms 106ms 868ms 4.5s 0 transport_latency_assumed last_trade_price k 42,417 3,353 16ms 60ms 446ms 32.9s 0 transport_latency_assumed last_trade_price m 70,539 63,242 7ms 27ms 202ms 4.3s 0 transport_latency_assumed market_resolved g 6,787 2,703 40.5s 13.8min 18.7min 19.4min 0 transport_latency_assumed market_resolved h 4,528 195 21ms 16.3s 51.1s 2.5min 0 transport_latency_assumed market_resolved i 5,798 490 31ms 9.2min 13.7min 14.3min 0 transport_latency_assumed market_resolved k 20,385 15,053 18.8min 43.7min 57.8min 1.1h 0 transport_latency_assumed market_resolved m 4,527 4,173 7ms 20.8s 53.5s 57.7s 0 transport_latency_assumed new_market g 4,745 517 429ms 9.0min 13.9min 14.8min 0 transport_latency_assumed new_market h 3,448 1,008 182ms 32.5s 57.5s 1.7min 0 transport_latency_assumed new_market i 5,104 1,571 262ms 7.8min 9.7min 9.8min 0 transport_latency_assumed new_market k 26,900 22,485 18.9min 46.8min 1.0h 1.0h 0 transport_latency_assumed new_market m 3,448 1,755 81ms 32.0s 59.8s 1.7min 0 transport_latency_assumed price_change g 98,979,548 31,828 83ms 213ms 2.5s 25.0s 0 transport_latency_assumed price_change h 130,232,622 3,492,782 20ms 44ms 859ms 1.1min 0 transport_latency_assumed price_change i 112,170,294 1,847,534 22ms 43ms 342ms 14.1s 0 transport_latency_assumed price_change k 82,745,998 5,607,464 14ms 34ms 274ms 1.0min 0 transport_latency_assumed price_change m 130,253,750 119,298,558 5ms 19ms 151ms 7.1s 0 transport_latency_assumed tick_size_change g 8,896 8 82ms 150ms 545ms 1.4s 0 transport_latency_assumed tick_size_change h 12,664 389 19ms 32ms 169ms 38.0s 0 transport_latency_assumed tick_size_change i 9,844 94 21ms 35ms 157ms 3.0s 0 transport_latency_assumed tick_size_change k 8,112 446 13ms 25ms 69ms 4.6s 0 transport_latency_assumed tick_size_change m 12,656 11,723 5ms 16ms 69ms 658ms 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-03/23/2026-10-03T23.parquet sha256sum 2026-10-03T23.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.