Hour audit: 2026-10-06T23
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-06T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T23:00:00.000016235+00:00 · last event 2026-10-06T23:59:59.999986012+00:00
VOLUME 110,579,122 rows · 1,218,405,675 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 110,511,904 · i: 110,497,676 · m: 110,488,638 · n: 110,445,101 · h: 110,178,962 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 54,144,044 (48.96%) · i: 510,307 (0.46%) · m: 55,389,321 (50.09%) · n: 33,970 (0.03%) · h: 501,480 (0.45%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 13a07e6c918b02697e7c6c1090c9ce4ae73332f6eeda11e1ae11ff92791f093a
no line in the corpus checksum ledger names this file
joined 110,580,139 to merged 110,579,122, minus 1,017 (minus 0.0009%)
boundary drops 1,017 · 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-07T01:03:19Z 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,452,093 140,089,154 0-43 44fb602f998074a6af3c7eb8a3067201ec969ed37aa89376c7298f407dc67e23 book 130,247 12,586,119 44-44 2eb6bc1566bec91008724ad2c56c6dd296dbc4957fb61d8f7f68bed0c84e49a9 last_trade_price 52,230 2,936,303 45-45 58e801f6c5c01207963e9b28bb8711261d4ef77499101cfbb8107ce0d0129ba2 market_resolved 1,285 209,307 46-46 087e6648f93dbb6dce63c41838ecbb6fae71e3040416439112905538df89db7a new_market 1,813 173,980 47-47 1485f272664ae9e534517886872c5561e3da8400d1741819748dc1cc27eb1433 price_change 98,939,234 1,061,066,374 48-425 738e06c03bc212df08fb0960c51c323987dfa453c9feb19eeec5bf392daee47f tick_size_change 2,220 82,946 426-426 327be6ea8227e1defce44c3789799ce6b0cda17b8f097b8d596587c30b0f60bf EVENT MIX count share price_change 98,939,234 89.47% best_bid_ask 11,452,093 10.36% book 130,247 0.12% last_trade_price 52,230 0.05% tick_size_change 2,220 <0.01% new_market 1,813 <0.01% market_resolved 1,285 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,452,188 11,452,093 95 101 FULL book 130,275 130,247 28 6,702 FULL last_trade_price 52,230 52,230 0 0 FULL market_resolved 1,285 1,285 0 0 FULL new_market 1,813 1,813 0 0 FULL price_change 98,940,128 98,939,234 894 53 FULL tick_size_change 2,220 2,220 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,438,245 47,845 17ms 25ms 344ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,450,588 50,337 21ms 27ms 107ms 5.6s 0 transport_latency_assumed best_bid_ask m 11,450,074 5,764,008 4ms 10ms 86ms 7.9s 0 transport_latency_assumed best_bid_ask n 11,449,638 2,347 44ms 55ms 267ms 16.3s 0 transport_latency_assumed best_bid_ask o 11,450,929 5,587,556 4ms 11ms 93ms 6.3s 0 transport_latency_assumed book h 112,001 9,468 21ms 554ms 8.7h 122.3d 0 book_staleness book i 109,476 4,301 23ms 128ms 2.3h 111.5d 0 book_staleness book m 108,488 55,450 6ms 34ms 53.8min 111.5d 0 book_staleness book n 111,560 6,172 48ms 873ms 12.7h 111.6d 0 book_staleness book o 109,448 54,856 6ms 40ms 4.2h 111.5d 0 book_staleness last_trade_price h 50,750 415 19ms 64ms 1.2s 32.4s 0 transport_latency_assumed last_trade_price i 52,092 309 23ms 68ms 993ms 4.8s 0 transport_latency_assumed last_trade_price m 51,810 26,133 6ms 19ms 169ms 1.5s 0 transport_latency_assumed last_trade_price n 51,795 40 48ms 190ms 2.3s 4.7s 0 transport_latency_assumed last_trade_price o 51,993 25,333 6ms 21ms 190ms 3.3s 0 transport_latency_assumed market_resolved h 1,258 4 20ms 292ms 41.3s 53.4s 0 transport_latency_assumed market_resolved i 1,258 122 24ms 242ms 39.7s 47.0s 0 transport_latency_assumed market_resolved m 1,258 587 5ms 107ms 40.5s 47.8s 0 transport_latency_assumed market_resolved n 1,258 13 48ms 232ms 53.3s 55.0s 0 transport_latency_assumed market_resolved o 1,258 559 5ms 33ms 42.6s 56.6s 0 transport_latency_assumed new_market h 1,110 208 205ms 31.6s 2.3min 2.7min 0 transport_latency_assumed new_market i 1,110 380 86ms 1.2min 2.2min 2.5min 0 transport_latency_assumed new_market m 1,110 698 67ms 28.8s 2.3min 2.7min 0 transport_latency_assumed new_market n 1,110 102 218ms 30.0s 2.4min 2.7min 0 transport_latency_assumed new_market o 1,110 425 88ms 30.0s 2.2min 2.5min 0 transport_latency_assumed price_change h 98,573,390 443,532 18ms 27ms 451ms 1.1min 0 transport_latency_assumed price_change i 98,880,932 454,850 21ms 30ms 184ms 5.7s 0 transport_latency_assumed price_change m 98,873,678 49,541,282 4ms 11ms 94ms 8.3s 0 transport_latency_assumed price_change n 98,827,520 25,292 45ms 62ms 453ms 16.6s 0 transport_latency_assumed price_change o 98,894,946 48,474,278 4ms 12ms 101ms 8.8s 0 transport_latency_assumed tick_size_change h 2,208 8 17ms 25ms 257ms 3.6s 0 transport_latency_assumed tick_size_change i 2,220 8 21ms 25ms 80ms 194ms 0 transport_latency_assumed tick_size_change m 2,220 1,163 4ms 8ms 128ms 226ms 0 transport_latency_assumed tick_size_change n 2,220 4 45ms 61ms 342ms 466ms 0 transport_latency_assumed tick_size_change o 2,220 1,037 4ms 9ms 86ms 215ms 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/23/2026-10-06T23.parquet sha256sum 2026-10-06T23.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.