Hour audit: 2026-10-09T08
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-09T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T08:00:00.000101521+00:00 · last event 2026-10-09T08:59:59.999914624+00:00
VOLUME 119,386,269 rows · 1,434,675,725 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 118,273,154 · o: 118,253,812 · h: 118,227,229 · i: 117,794,461 · n: 112,846,348 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 59,636,136 (49.95%) · o: 56,687,229 (47.48%) · h: 1,404,978 (1.18%) · i: 874,871 (0.73%) · n: 783,055 (0.66%) (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 119,386,269 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 764d4681d3ede5e656e02ca2b36f45ba64a5688643171fac7d0810bd6aae514f
no line in the corpus checksum ledger names this file
joined 119,387,865 to merged 119,386,269, minus 1,596 (minus 0.0013%)
boundary drops 1,596 · 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-10T00:53:51Z 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 12,034,821 154,283,335 0-45 07948eaa5186d79a94b563fc784d744390fddb07a8848b7cfdc7edea49461874 book 1,611,343 106,708,647 46-52 05f8c40f20f7382eccb542e13d282931abdaea383c9f15aefa0d01f0c9ab9162 last_trade_price 67,359 3,846,155 53-53 2778ffe129c17070bc3371c3dc300d339b3f1ec3f948fc3fce341b240e1430f8 market_resolved 627 96,528 54-54 2937b87a2f5ac2777d87637a4f93668430e475fca0242961be338e176c7977d0 new_market 2,459 228,729 55-55 3a56c83bc127c0c82177fac5384651c5f10399b3f40fa8c77fe37e8f85e541d4 price_change 105,666,300 1,168,025,950 56-459 84d5470ee69b0a01c09ff3448ea3c55f85be2904764f4c63be71f319f8be7572 tick_size_change 3,360 124,775 460-460 f7834905baa69447802e0ed02027abab991451460f08187d45eab435b5a8b44b EVENT MIX count share price_change 105,666,300 88.51% best_bid_ask 12,034,821 10.08% book 1,611,343 1.35% last_trade_price 67,359 0.06% tick_size_change 3,360 <0.01% new_market 2,459 <0.01% market_resolved 627 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,034,931 12,034,821 110 728 FULL book 1,611,395 1,611,343 52 269,207 FULL last_trade_price 67,359 67,359 0 101 FULL market_resolved 627 627 0 0 FULL new_market 2,459 2,459 0 0 FULL price_change 105,667,734 105,666,300 1,434 829 FULL tick_size_change 3,360 3,360 0 46 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,029,262 105,855 18ms 36ms 493ms 1.4min 0 transport_latency_assumed best_bid_ask i 12,032,760 84,773 21ms 34ms 195ms 4.7s 0 transport_latency_assumed best_bid_ask m 12,031,994 6,070,055 5ms 17ms 147ms 5.8s 0 transport_latency_assumed best_bid_ask n 11,442,847 6,346 44ms 66ms 445ms 22.2s 0 transport_latency_assumed best_bid_ask o 12,030,959 5,767,792 5ms 17ms 174ms 8.9s 0 transport_latency_assumed book h 576,380 269,550 4.6min 1.2d 47.8d 132.4d 0 book_staleness book i 150,365 8,021 27ms 2.1s 1.2d 132.4d 0 book_staleness book m 590,636 314,260 5.0min 1.2d 47.8d 132.4d 0 book_staleness book n 1,118,944 707,594 14.0min 1.2d 47.8d 132.4d 0 book_staleness book o 592,478 311,918 5.0min 1.2d 47.8d 132.4d 0 book_staleness last_trade_price h 67,100 484 21ms 162ms 840ms 46.2s 0 transport_latency_assumed last_trade_price i 67,125 307 26ms 361ms 1.8s 4.7s 0 transport_latency_assumed last_trade_price m 67,221 33,623 6ms 27ms 202ms 3.8s 0 transport_latency_assumed last_trade_price n 60,950 29 54ms 1.7s 12.1s 22.2s 0 transport_latency_assumed last_trade_price o 67,058 32,916 6ms 31ms 276ms 4.3s 0 transport_latency_assumed market_resolved h 582 5 24ms 106ms 1.6s 47.7s 0 transport_latency_assumed market_resolved i 582 19 24ms 142ms 54.0s 54.1s 0 transport_latency_assumed market_resolved m 582 276 5ms 26ms 54.2s 54.2s 0 transport_latency_assumed market_resolved n 602 32 53ms 448ms 6.7min 6.8min 0 transport_latency_assumed market_resolved o 582 295 5ms 19ms 246ms 35.6s 0 transport_latency_assumed new_market h 1,475 223 216ms 32.7s 37.9s 1.2min 0 transport_latency_assumed new_market i 1,475 374 126ms 22.2s 36.6s 2.0min 0 transport_latency_assumed new_market m 1,475 793 113ms 32.5s 39.4s 1.7min 0 transport_latency_assumed new_market n 1,585 222 278ms 34.6s 6.2min 6.2min 0 transport_latency_assumed new_market o 1,475 847 103ms 32.9s 35.5s 2.0min 0 transport_latency_assumed price_change h 105,549,070 1,028,848 18ms 43ms 652ms 1.4min 0 transport_latency_assumed price_change i 105,538,794 781,366 21ms 45ms 433ms 4.7s 0 transport_latency_assumed price_change m 105,577,886 53,215,412 5ms 19ms 163ms 5.8s 0 transport_latency_assumed price_change n 100,218,244 68,832 45ms 95ms 2.2s 22.3s 0 transport_latency_assumed price_change o 105,557,900 50,571,842 5ms 20ms 192ms 10.5s 0 transport_latency_assumed tick_size_change h 3,360 13 18ms 35ms 110ms 22.5s 0 transport_latency_assumed tick_size_change i 3,360 11 21ms 35ms 97ms 238ms 0 transport_latency_assumed tick_size_change m 3,360 1,717 5ms 13ms 105ms 628ms 0 transport_latency_assumed tick_size_change n 3,176 not meas. 44ms 60ms 182ms 652ms 0 transport_latency_assumed tick_size_change o 3,360 1,619 5ms 14ms 76ms 256ms 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-09/08/2026-10-09T08.parquet sha256sum 2026-10-09T08.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.