Hour audit: 2026-10-07T04
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-07T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T04:00:00.000418122+00:00 · last event 2026-10-07T04:59:59.999118992+00:00
VOLUME 110,191,116 rows · 1,221,935,975 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 110,016,922 · m: 110,000,136 · n: 109,975,826 · i: 109,953,358 · h: 109,947,369 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 56,699,387 (51.46%) · m: 51,482,463 (46.72%) · n: 111,294 (0.10%) · i: 931,141 (0.85%) · h: 966,831 (0.88%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 60df980ab1c31c688e2b7c81e41fc34b263b2d5d5b4f2731525dc8b7671418f6
the corpus checksum ledger names this file with the same digest
joined 110,194,098 to merged 110,191,116, minus 2,982 (minus 0.0027%)
boundary drops 2,982 · 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-07T06:01: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 11,718,624 146,169,611 0-44 636eab93de7040e6e3109b6c2a0b2ddeb33c852073ca5e8197002d711e4da84f book 207,396 21,235,598 45-45 9acd5d5143decb6674e50bcab01765538a2549955bcc137a7a8a1a4573b2bed8 last_trade_price 46,409 2,636,938 46-46 dadca749e9720ad05ab2852dc944ba005d41c7740c76bc1558ab18babe378c24 market_resolved 935 142,013 47-47 5c0a663e4f2064a45e8912c4d477ee8f477a3d71e2bc75a3cff125a5bd3b9365 new_market 3,200 289,074 48-48 f76d1377f89f9bf8be4a9282aecaa1ff94a2e7bbb67b0e73367f9aa6e512bcd4 price_change 98,212,360 1,050,125,887 49-423 15ce45e857be44f17e23ea4688684db79923a82f50f84dbc9c97d810cb55bd23 tick_size_change 2,192 81,721 424-424 ead0eecb3ce3b4395ce5cd61ae99f37e9ea9bdb4e39cbcdca823a86a771f3282 EVENT MIX count share price_change 98,212,360 89.13% best_bid_ask 11,718,624 10.63% book 207,396 0.19% last_trade_price 46,409 0.04% new_market 3,200 <0.01% tick_size_change 2,192 <0.01% market_resolved 935 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,719,058 11,718,624 434 104 FULL book 207,398 207,396 2 47,563 FULL last_trade_price 46,409 46,409 0 0 FULL market_resolved 935 935 0 0 FULL new_market 3,200 3,200 0 0 FULL price_change 98,214,906 98,212,360 2,546 88 FULL tick_size_change 2,192 2,192 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,710,394 84,721 18ms 32ms 1.4s 2.5min 0 transport_latency_assumed best_bid_ask i 11,715,266 90,920 21ms 31ms 220ms 4.1s 0 transport_latency_assumed best_bid_ask m 11,715,744 5,429,914 4ms 14ms 187ms 10.3s 0 transport_latency_assumed best_bid_ask n 11,716,671 8,136 43ms 60ms 448ms 10.0s 0 transport_latency_assumed best_bid_ask o 11,716,177 6,104,933 4ms 14ms 196ms 30.9s 0 transport_latency_assumed book h 154,510 56,681 43ms 10.6h 31.6d 130.3d 0 book_staleness book i 102,245 7,052 24ms 620ms 11.3h 111.7d 0 book_staleness book m 117,281 62,714 8ms 15.7min 15.2d 130.2d 0 book_staleness book n 104,045 8,144 48ms 2.7s 1.4d 111.7d 0 book_staleness book o 119,786 72,805 7ms 24.9min 17.6d 111.7d 0 book_staleness last_trade_price h 46,016 634 20ms 77ms 1.7s 58.4s 0 transport_latency_assumed last_trade_price i 46,066 535 23ms 97ms 705ms 1.8s 0 transport_latency_assumed last_trade_price m 46,100 20,310 6ms 27ms 263ms 9.4s 0 transport_latency_assumed last_trade_price n 46,209 111 47ms 196ms 2.7s 9.9s 0 transport_latency_assumed last_trade_price o 46,168 24,819 6ms 24ms 251ms 12.7s 0 transport_latency_assumed market_resolved h 888 4 20ms 23.7s 44.9s 45.0s 0 transport_latency_assumed market_resolved i 888 113 23ms 18.7s 41.7s 41.8s 0 transport_latency_assumed market_resolved m 888 379 5ms 19.1s 42.0s 42.0s 0 transport_latency_assumed market_resolved n 888 47 45ms 218ms 48.5s 48.5s 0 transport_latency_assumed market_resolved o 888 392 5ms 29.3s 52.3s 52.3s 0 transport_latency_assumed new_market h 1,907 513 319ms 34.3s 40.7s 1.7min 0 transport_latency_assumed new_market i 1,907 563 156ms 35.1s 40.9s 1.7min 0 transport_latency_assumed new_market m 1,907 937 148ms 34.5s 41.0s 1.4min 0 transport_latency_assumed new_market n 1,907 318 290ms 32.3s 40.0s 1.7min 0 transport_latency_assumed new_market o 1,907 869 136ms 33.7s 41.4s 1.6min 0 transport_latency_assumed price_change h 98,031,462 824,266 18ms 39ms 1.3s 2.6min 0 transport_latency_assumed price_change i 98,084,794 831,954 21ms 39ms 350ms 4.2s 0 transport_latency_assumed price_change m 98,116,024 45,967,136 4ms 16ms 197ms 16.9s 0 transport_latency_assumed price_change n 98,103,914 94,534 44ms 77ms 866ms 10.3s 0 transport_latency_assumed price_change o 98,129,804 50,494,470 4ms 16ms 207ms 31.4s 0 transport_latency_assumed tick_size_change h 2,192 12 18ms 25ms 113ms 2.9s 0 transport_latency_assumed tick_size_change i 2,192 4 21ms 34ms 132ms 257ms 0 transport_latency_assumed tick_size_change m 2,192 1,073 4ms 12ms 50ms 306ms 0 transport_latency_assumed tick_size_change n 2,192 4 44ms 55ms 180ms 512ms 0 transport_latency_assumed tick_size_change o 2,192 1,099 4ms 12ms 117ms 569ms 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-07/04/2026-10-07T04.parquet sha256sum 2026-10-07T04.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.