Hour audit: 2026-10-09T06
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-09T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T06:00:00.000013307+00:00 · last event 2026-10-09T06:59:59.999986643+00:00
VOLUME 107,870,894 rows · 1,225,225,936 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 107,769,620 · h: 107,528,483 · m: 107,516,326 · n: 107,453,635 · o: 107,452,119 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 769,780 (0.71%) · h: 878,555 (0.81%) · m: 54,447,584 (50.47%) · n: 44,065 (0.04%) · o: 51,730,910 (47.96%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,870,894 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b625a613f436f708becc437dc94464653d9b52cc3f0b745dcb5a703a5861a7aa
no line in the corpus checksum ledger names this file
joined 107,871,848 to merged 107,870,894, minus 954 (minus 0.0009%)
boundary drops 954 · 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-09T23:53: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 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,506,470 142,730,248 0-43 c06dc518e3d507392759d093676b076b5e7a094dd792786e71fc63637770445f book 360,864 38,015,375 44-45 d0ab656dec6039793ea3993a74ef0b822bc4e7ea6e7c701ae4a1c15ad003cc38 last_trade_price 47,462 2,765,866 46-46 e255d9a45ccf6b7a6da54a5b5b348248abe5a464e1ead0237f6974611e0a443b market_resolved 876 143,096 47-47 ac559ff1e8b5212d74096df088159ae37a54a6ea7c3a1ed35e7c84a506e0d292 new_market 1,048 100,723 48-48 29e7fbfcc60623342baae01806b91499de845471939c037854a1c045e031bf5f price_change 95,951,814 1,040,151,700 49-415 5271e6fdf283eff84eba0a6102da0c52445d3a9dcf635bfd8b187999f85e12c0 tick_size_change 2,360 87,154 416-416 497d8636bd283525b5102295fc8e36ae8538324467e366a80b255bb6006d4fba EVENT MIX count share price_change 95,951,814 88.95% best_bid_ask 11,506,470 10.67% book 360,864 0.33% last_trade_price 47,462 0.04% tick_size_change 2,360 <0.01% new_market 1,048 <0.01% market_resolved 876 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,506,566 11,506,470 96 97 FULL book 360,967 360,864 103 114,452 FULL last_trade_price 47,463 47,462 1 1 FULL market_resolved 876 876 0 0 FULL new_market 1,048 1,048 0 0 FULL price_change 95,952,568 95,951,814 754 219 FULL tick_size_change 2,360 2,360 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,502,008 75,292 18ms 33ms 249ms 1.1min 0 transport_latency_assumed best_bid_ask i 11,504,298 51,498 21ms 31ms 118ms 4.1s 0 transport_latency_assumed best_bid_ask m 11,505,219 5,839,001 4ms 14ms 78ms 7.1s 0 transport_latency_assumed best_bid_ask n 11,504,206 2,678 44ms 60ms 199ms 9.3s 0 transport_latency_assumed best_bid_ask o 11,504,431 5,538,001 5ms 14ms 86ms 1.2min 0 transport_latency_assumed book h 123,524 24,203 27ms 1.2h 29.9d 113.9d 0 book_staleness book i 317,048 220,216 3.7min 1.1d 47.7d 132.3d 0 book_staleness book m 103,851 53,283 7ms 127ms 1.0d 113.9d 0 book_staleness book n 104,757 8,416 49ms 3.2s 1.1d 113.8d 0 book_staleness book o 103,302 54,746 7ms 96ms 1.1d 114.3d 0 book_staleness last_trade_price h 47,337 496 20ms 100ms 566ms 42.8s 0 transport_latency_assumed last_trade_price i 47,294 209 25ms 151ms 704ms 3.0s 0 transport_latency_assumed last_trade_price m 47,262 23,007 6ms 25ms 187ms 1.8s 0 transport_latency_assumed last_trade_price n 47,310 46 49ms 395ms 3.9s 8.4s 0 transport_latency_assumed last_trade_price o 47,198 23,704 6ms 23ms 159ms 3.5s 0 transport_latency_assumed market_resolved h 864 7 21ms 101ms 49.7s 49.8s 0 transport_latency_assumed market_resolved i 864 5 23ms 158ms 46.8s 55.9s 0 transport_latency_assumed market_resolved m 864 471 5ms 34ms 46.9s 55.9s 0 transport_latency_assumed market_resolved n 864 not meas. 46ms 269ms 52.8s 52.9s 0 transport_latency_assumed market_resolved o 864 393 5ms 23ms 39.5s 49.8s 0 transport_latency_assumed new_market h 656 164 184ms 32.2s 1.0min 48.8min 0 transport_latency_assumed new_market i 656 194 85ms 15.0s 1.4min 33.7min 0 transport_latency_assumed new_market m 656 306 65ms 31.2s 1.2min 28.7min 0 transport_latency_assumed new_market n 656 129 206ms 33.1s 3.6min 32.7min 0 transport_latency_assumed new_market o 656 255 55ms 32.5s 1.6min 29.7min 0 transport_latency_assumed price_change h 95,851,734 778,368 18ms 38ms 339ms 1.1min 0 transport_latency_assumed price_change i 95,897,100 497,642 22ms 39ms 310ms 4.2s 0 transport_latency_assumed price_change m 95,856,118 48,530,420 5ms 16ms 99ms 8.1s 0 transport_latency_assumed price_change n 95,793,482 32,796 44ms 73ms 835ms 9.4s 0 transport_latency_assumed price_change o 95,793,308 46,112,588 5ms 16ms 103ms 1.2min 0 transport_latency_assumed tick_size_change h 2,360 25 19ms 41ms 262ms 27.5s 0 transport_latency_assumed tick_size_change i 2,360 16 22ms 42ms 194ms 881ms 0 transport_latency_assumed tick_size_change m 2,356 1,096 5ms 17ms 104ms 198ms 0 transport_latency_assumed tick_size_change n 2,360 not meas. 45ms 94ms 202ms 234ms 0 transport_latency_assumed tick_size_change o 2,360 1,223 5ms 14ms 68ms 214ms 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/06/2026-10-09T06.parquet sha256sum 2026-10-09T06.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.