Hour audit: 2026-10-03T19
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-03T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T19:00:00.000026260+00:00 · last event 2026-10-03T19:59:59.999998509+00:00
VOLUME 140,445,818 rows · 1,622,039,126 bytes (1.51 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 138,270,959 · h: 138,202,212 · i: 126,053,406 · g: 120,097,474 · k: 119,854,332 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 126,757,495 (90.25%) · h: 2,981,070 (2.12%) · i: 2,051,377 (1.46%) · g: 999,600 (0.71%) · k: 7,656,276 (5.45%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 82fdaa9da758fe637f367108f783564e8c6eae1aefff4e37d6814fdd6bcbcc9c
the corpus checksum ledger names this file with the same digest
joined 140,452,451 to merged 140,445,818, minus 6,633 (minus 0.0047%)
boundary drops 6,633 · 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-03T21:53:30Z 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 12,134,853 148,314,128 0-46 8306988823e8580aa27fb397b6ed36a3e765e5269e82f0bfcb3e0f14ff2a7b03 book 2,225,093 108,298,943 47-55 d1fa9bb8c25aaf7243c70ce6f1f1845b8c9e767ae0c077fb2b0104f054c90327 last_trade_price 57,341 3,392,874 56-56 39d31afd03c17b4dac45b56990897959eceea151424fa8e7cea9fc31c5efdbc3 market_resolved 6,181 705,263 57-57 5edf7fe28d673c19aafb8cffdb8ae4e6a9b0d00da6eacfa4c1b78bc1d43b9de7 new_market 8,304 633,934 58-58 4124e94b6d75cae4123e6cf52338e1f602d6ce90b53eae26396e063ae14c42ce price_change 126,004,374 1,358,739,609 59-539 3fa413ccce65127047e2dfab87c395b70051fcec70e19498a65c7714301f99aa tick_size_change 9,672 356,620 540-540 f90fa50a6d543a7bc0f3f7324b6932c18d700f0ed5055db102c55183a1f9cf37 EVENT MIX count share price_change 126,004,374 89.72% best_bid_ask 12,134,853 8.64% book 2,225,093 1.58% last_trade_price 57,341 0.04% tick_size_change 9,672 <0.01% new_market 8,304 <0.01% market_resolved 6,181 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,135,476 12,134,853 623 6,378 FULL book 2,226,055 2,225,093 962 233,698 FULL last_trade_price 57,341 57,341 0 624 FULL market_resolved 6,181 6,181 0 611 FULL new_market 8,306 8,304 2 281 FULL price_change 126,009,420 126,004,374 5,046 6,288 FULL tick_size_change 9,672 9,672 0 511 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,451,731 2,573 81ms 127ms 885ms 38.4s 0 transport_latency_assumed best_bid_ask h 12,128,890 250,980 19ms 41ms 1.4s 1.9min 0 transport_latency_assumed best_bid_ask i 11,000,355 109,006 21ms 38ms 371ms 50.6s 0 transport_latency_assumed best_bid_ask k 10,458,433 624,515 14ms 31ms 277ms 1.1min 0 transport_latency_assumed best_bid_ask m 12,133,439 11,147,779 5ms 17ms 201ms 9.2s 0 transport_latency_assumed book g 1,579,994 964,562 27.4min 1.8d 42.2d 126.9d 0 book_staleness book h 130,277 8,410 26ms 2.8s 1.2d 126.9d 0 book_staleness book i 1,137,369 737,069 24.4min 1.8d 42.2d 126.9d 0 book_staleness book k 1,592,397 405,659 26.4min 1.8d 42.2d 126.9d 0 book_staleness book m 127,710 109,393 9ms 330ms 5.7h 108.4d 0 book_staleness last_trade_price g 48,509 19 86ms 366ms 9.8s 38.5s 0 transport_latency_assumed last_trade_price h 57,172 1,566 21ms 105ms 1.9s 1.1min 0 transport_latency_assumed last_trade_price i 51,550 658 24ms 74ms 832ms 28.1s 0 transport_latency_assumed last_trade_price k 47,982 3,657 16ms 44ms 350ms 36.2s 0 transport_latency_assumed last_trade_price m 57,257 51,441 7ms 27ms 260ms 2.2s 0 transport_latency_assumed market_resolved g 4,263 632 89ms 8.8min 16.6min 17.4min 0 transport_latency_assumed market_resolved h 3,745 122 20ms 59ms 47.4s 1.0min 0 transport_latency_assumed market_resolved i 4,763 1,386 26ms 11.3min 13.8min 14.6min 0 transport_latency_assumed market_resolved k 4,157 558 18ms 6.0min 9.7min 10.5min 0 transport_latency_assumed market_resolved m 3,745 3,483 6ms 50ms 45.2s 58.4s 0 transport_latency_assumed new_market g 5,964 2,110 48.4s 13.3min 13.8min 1.3h 0 transport_latency_assumed new_market h 3,526 1,085 293ms 43.8s 1.1min 1.6min 0 transport_latency_assumed new_market i 4,153 1,400 350ms 6.5min 8.9min 9.2min 0 transport_latency_assumed new_market k 3,804 1,897 148ms 5.0min 6.8min 9.3min 0 transport_latency_assumed new_market m 3,526 1,812 130ms 46.2s 1.0min 1.9min 0 transport_latency_assumed price_change g 107,998,537 29,700 81ms 159ms 1.7s 38.7s 0 transport_latency_assumed price_change h 125,868,930 2,718,780 19ms 50ms 2.0s 2.1min 0 transport_latency_assumed price_change i 113,846,264 1,201,768 22ms 43ms 456ms 51.2s 0 transport_latency_assumed price_change k 107,739,207 6,619,618 15ms 34ms 293ms 1.1min 0 transport_latency_assumed price_change m 125,935,610 115,434,508 5ms 19ms 213ms 12.0s 0 transport_latency_assumed tick_size_change g 8,476 4 80ms 104ms 950ms 1.8s 0 transport_latency_assumed tick_size_change h 9,672 127 19ms 51ms 1.1s 37.3s 0 transport_latency_assumed tick_size_change i 8,952 90 22ms 50ms 568ms 7.1s 0 transport_latency_assumed tick_size_change k 8,352 372 14ms 28ms 581ms 2.8s 0 transport_latency_assumed tick_size_change m 9,672 9,079 5ms 18ms 356ms 1.1s 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/19/2026-10-03T19.parquet sha256sum 2026-10-03T19.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.