Hour audit: 2026-10-06T19
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T19:00:00.000009953+00:00 · last event 2026-10-06T19:59:59.999987003+00:00
VOLUME 118,965,065 rows · 1,388,809,824 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 118,722,328 · m: 118,702,983 · o: 118,643,498 · i: 118,262,074 · n: 118,142,805 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,253,752 (1.05%) · m: 58,500,947 (49.17%) · o: 57,485,500 (48.32%) · i: 1,567,684 (1.32%) · n: 157,182 (0.13%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 118,965,065 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9706fc9265d633e9de2048fc9071941120bdc0003a7c44ed64b78c3c0d9ae19c
no line in the corpus checksum ledger names this file
joined 118,967,131 to merged 118,965,065, minus 2,066 (minus 0.0017%)
boundary drops 2,066 · 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-06T21:04:15Z 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 7/8 pass, 1 finding
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
FINDING the checksum ledger does not name 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,283,338 143,783,495 0-43 b03e9d3328883420e7f56715afcd7532204773e567f037aa35d16f81f6928609 book 325,375 32,702,219 44-45 d32dc1f1dbc190544a3c03cb2382213482eac5c7633b6a0555a1708e0decd9b9 last_trade_price 61,425 3,557,142 46-46 dedbd118a6ccfb29228562f861449598ab81d80a1b315367def70be1ef152278 market_resolved 1,030 151,461 47-47 44d84576b47d3f5ff5a6131d23093bc826ca91bed7df6f93ae9b8ffbcace33e1 new_market 6,025 605,722 48-48 b6da21b4d46af2f8a3cf1127f7861ba0a23516c9a59ce29d49fa9c3bb3a8dad1 price_change 107,284,136 1,206,515,099 49-458 261ecbdc42daff48716d94644629c25d752c2ed65c9aace5790ed264be250753 tick_size_change 3,736 136,232 459-459 27576f6b49d42e174dbf3eb054f11ba8d112a061ba4aaca25d7b0c65c7a5fdd4 EVENT MIX count share price_change 107,284,136 90.18% best_bid_ask 11,283,338 9.48% book 325,375 0.27% last_trade_price 61,425 0.05% new_market 6,025 <0.01% tick_size_change 3,736 <0.01% market_resolved 1,030 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,283,490 11,283,338 152 480 FULL book 326,235 325,375 860 82,700 FULL last_trade_price 61,425 61,425 0 2 FULL market_resolved 1,030 1,030 0 0 FULL new_market 6,025 6,025 0 0 FULL price_change 107,285,190 107,284,136 1,054 72 FULL tick_size_change 3,736 3,736 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,278,138 107,086 19ms 50ms 1.3s 1.8min 0 transport_latency_assumed best_bid_ask i 11,269,688 148,018 21ms 40ms 280ms 14.6s 0 transport_latency_assumed best_bid_ask m 11,278,829 5,609,755 5ms 20ms 233ms 26.7s 0 transport_latency_assumed best_bid_ask n 11,272,487 8,877 45ms 93ms 568ms 31.4s 0 transport_latency_assumed best_bid_ask o 11,276,038 5,409,602 5ms 22ms 280ms 16.8s 0 transport_latency_assumed book h 196,942 63,798 68ms 4.0h 29.4d 129.9d 0 book_staleness book i 145,951 20,408 32ms 1.1min 3.2d 129.9d 0 book_staleness book m 167,436 95,245 11ms 1.1h 27.4d 129.9d 0 book_staleness book n 168,780 41,612 111ms 1.5h 28.0d 129.9d 0 book_staleness book o 172,791 104,312 12ms 1.6h 21.8d 111.4d 0 book_staleness last_trade_price h 61,236 792 22ms 251ms 2.6s 58.7s 0 transport_latency_assumed last_trade_price i 60,041 682 27ms 224ms 5.2s 14.0s 0 transport_latency_assumed last_trade_price m 61,082 29,075 7ms 39ms 338ms 4.2s 0 transport_latency_assumed last_trade_price n 59,060 221 53ms 590ms 12.2s 30.7s 0 transport_latency_assumed last_trade_price o 60,955 30,655 7ms 42ms 382ms 5.1s 0 transport_latency_assumed market_resolved h 934 50 22ms 30.0s 54.2s 57.8s 0 transport_latency_assumed market_resolved i 934 156 24ms 36.9s 48.6s 48.7s 0 transport_latency_assumed market_resolved m 934 409 7ms 38.1s 50.0s 50.0s 0 transport_latency_assumed market_resolved n 934 46 47ms 237ms 55.7s 55.8s 0 transport_latency_assumed market_resolved o 934 369 7ms 40.5s 55.7s 55.8s 0 transport_latency_assumed new_market h 3,836 675 234ms 34.1s 51.6s 1.5min 0 transport_latency_assumed new_market i 3,836 948 129ms 33.1s 49.1s 1.5min 0 transport_latency_assumed new_market m 3,836 2,134 81ms 32.2s 48.8s 1.7min 0 transport_latency_assumed new_market n 3,836 646 299ms 34.1s 50.4s 1.6min 0 transport_latency_assumed new_market o 3,836 1,622 115ms 33.2s 48.9s 1.9min 0 transport_latency_assumed price_change h 107,177,510 1,081,308 20ms 71ms 1.7s 1.8min 0 transport_latency_assumed price_change i 106,777,888 1,397,396 22ms 55ms 1.1s 14.7s 0 transport_latency_assumed price_change m 107,187,130 52,762,566 6ms 23ms 243ms 27.5s 0 transport_latency_assumed price_change n 106,633,972 105,780 46ms 151ms 3.5s 31.5s 0 transport_latency_assumed price_change o 107,125,208 51,937,086 6ms 25ms 290ms 59.5s 0 transport_latency_assumed tick_size_change h 3,732 43 19ms 91ms 1.1s 35.1s 0 transport_latency_assumed tick_size_change i 3,736 76 21ms 55ms 164ms 3.0s 0 transport_latency_assumed tick_size_change m 3,736 1,763 6ms 26ms 255ms 332ms 0 transport_latency_assumed tick_size_change n 3,736 not meas. 45ms 113ms 410ms 13.0s 0 transport_latency_assumed tick_size_change o 3,736 1,854 5ms 24ms 277ms 359ms 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-06/19/2026-10-06T19.parquet sha256sum 2026-10-06T19.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.