Hour audit: 2026-10-04T11
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-04T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T11:00:00.000042823+00:00 · last event 2026-10-04T11:59:59.999954452+00:00
VOLUME 103,022,744 rows · 1,135,615,346 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 102,976,320 · h: 102,972,610 · i: 102,962,457 · o: 102,960,773 · n: 102,909,049 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 55,509,766 (53.88%) · h: 430,448 (0.42%) · i: 277,356 (0.27%) · o: 46,759,219 (45.39%) · n: 45,955 (0.04%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 c0ea8a419d2f6052c7c4e3f79c04af55250ad2bfb63c33098352dc5fc53ccd36
the corpus checksum ledger names this file with the same digest
joined 103,023,567 to merged 103,022,744, minus 823 (minus 0.0008%)
boundary drops 823 · 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-04T12:59:12Z 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,571,814 109,617,426 0-32 bdb8f2a2fb7fd5bbf0607a80b77f37e1c43dfce0eb92fd2545e4f3598326101d book 119,402 12,514,302 33-33 6ce14192776c118b68b3705ad20d9dd3b85463e6647f0d81c1f6adeef73450be last_trade_price 54,176 3,093,980 34-34 13ee16e5f7afad1e4ce0498ce01404d69ebb2eca5815b2ad02bc72825e89b49d market_resolved 870 124,369 35-35 c66ab7f1300364c0bcd0e34d6de27348167f51f5f3a5675d4ab30ed997f8290c new_market 2,794 268,578 36-36 84de89c0baf8baec51ccdfdcd5b67e3fa1edeec98391210302a3d72ac2ae66af price_change 94,269,832 1,008,677,458 37-396 919b16d8276d9beab0bccfa46ce9f4d35a342dad2ade0788f72431654e592b4e tick_size_change 3,856 142,979 397-397 30540b004ecc213fa1d172800766a847a3759b6f1d918388d95b1d4eaa53b664 EVENT MIX count share price_change 94,269,832 91.50% best_bid_ask 8,571,814 8.32% book 119,402 0.12% last_trade_price 54,176 0.05% tick_size_change 3,856 <0.01% new_market 2,794 <0.01% market_resolved 870 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,571,896 8,571,814 82 274 FULL book 119,404 119,402 2 2,818 FULL last_trade_price 54,177 54,176 1 0 FULL market_resolved 870 870 0 0 FULL new_market 2,794 2,794 0 0 FULL price_change 94,270,570 94,269,832 738 666 FULL tick_size_change 3,856 3,856 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,570,065 32,987 18ms 26ms 364ms 1.0min 0 transport_latency_assumed best_bid_ask i 8,570,180 21,424 21ms 27ms 204ms 14.3s 0 transport_latency_assumed best_bid_ask m 8,570,606 4,613,533 4ms 11ms 117ms 9.0s 0 transport_latency_assumed best_bid_ask n 8,569,792 3,394 46ms 59ms 322ms 16.0s 0 transport_latency_assumed best_bid_ask o 8,570,676 3,900,476 5ms 11ms 122ms 7.8s 0 transport_latency_assumed book h 112,774 3,104 22ms 66ms 14.4s 108.9d 0 book_staleness book i 112,654 2,304 23ms 80ms 7.9s 109.1d 0 book_staleness book m 112,542 61,384 7ms 23ms 8.7s 55.8d 0 book_staleness book n 113,594 2,206 50ms 349ms 8.3min 127.5d 0 book_staleness book o 112,946 50,404 7ms 26ms 1.0min 109.0d 0 book_staleness last_trade_price h 54,105 352 20ms 39ms 526ms 54.3s 0 transport_latency_assumed last_trade_price i 54,135 196 23ms 54ms 451ms 4.7s 0 transport_latency_assumed last_trade_price m 54,086 29,580 6ms 15ms 161ms 1.4s 0 transport_latency_assumed last_trade_price n 54,060 28 50ms 167ms 3.7s 16.0s 0 transport_latency_assumed last_trade_price o 54,047 24,020 6ms 16ms 198ms 1.9s 0 transport_latency_assumed market_resolved h 778 65 20ms 262ms 52.5s 54.3s 0 transport_latency_assumed market_resolved i 778 18 23ms 35.9s 50.3s 50.3s 0 transport_latency_assumed market_resolved m 778 368 6ms 39.4s 55.7s 55.7s 0 transport_latency_assumed market_resolved n 778 5 48ms 33.8s 47.7s 47.7s 0 transport_latency_assumed market_resolved o 778 414 6ms 39.0s 55.7s 55.8s 0 transport_latency_assumed new_market h 1,720 544 319ms 35.8s 1.0min 1.7min 0 transport_latency_assumed new_market i 1,720 356 249ms 36.2s 1.0min 1.7min 0 transport_latency_assumed new_market m 1,720 917 104ms 36.1s 1.0min 1.6min 0 transport_latency_assumed new_market n 1,720 186 8.6s 37.4s 1.0min 1.7min 0 transport_latency_assumed new_market o 1,720 791 140ms 36.9s 1.0min 1.7min 0 transport_latency_assumed price_change h 94,229,312 393,362 18ms 28ms 448ms 1.0min 0 transport_latency_assumed price_change i 94,219,134 253,014 21ms 31ms 293ms 19.1s 0 transport_latency_assumed price_change m 94,232,732 50,801,956 5ms 11ms 104ms 11.5s 0 transport_latency_assumed price_change n 94,165,249 40,130 46ms 66ms 645ms 16.0s 0 transport_latency_assumed price_change o 94,216,750 42,781,370 5ms 11ms 110ms 10.3s 0 transport_latency_assumed tick_size_change h 3,856 34 18ms 32ms 865ms 15.0s 0 transport_latency_assumed tick_size_change i 3,856 44 21ms 35ms 231ms 496ms 0 transport_latency_assumed tick_size_change m 3,856 2,028 5ms 16ms 126ms 389ms 0 transport_latency_assumed tick_size_change n 3,856 6 46ms 70ms 324ms 639ms 0 transport_latency_assumed tick_size_change o 3,856 1,744 5ms 14ms 244ms 602ms 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-04/11/2026-10-04T11.parquet sha256sum 2026-10-04T11.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.