Hour audit: 2026-10-09T10
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-09T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T10:00:00.000021107+00:00 · last event 2026-10-09T10:59:59.999963215+00:00
VOLUME 118,025,097 rows · 1,415,825,898 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 117,294,300 · m: 116,945,751 · o: 116,934,160 · h: 116,913,423 · n: 111,839,197 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,239,825 (1.05%) · m: 59,325,313 (50.26%) · o: 55,770,805 (47.25%) · h: 1,256,613 (1.06%) · n: 432,541 (0.37%) (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,025,097 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 977c3ef332503d7c92ebf972e8c3c3fd698f5e3326521cb2a0c2808a36ae8b75
no line in the corpus checksum ledger names this file
joined 118,034,177 to merged 118,025,097, minus 9,080 (minus 0.0077%)
boundary drops 9,080 · 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-10T01:56:53Z 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,474,550 157,132,503 0-47 d72184165490392a996907cf0e47bff482371a42ba29e1125285942e4d863a43 book 1,275,363 94,326,212 48-52 9585e7b2eb5ac3c03e0b1e56bd2d8a103dba060af84a5530a44f19e590911c76 last_trade_price 50,471 2,978,294 53-53 36ee2f59d6f0a9aed427de030abb4b172bf7720574b61f73cac86c03a9128c2f market_resolved 390 63,695 54-54 9f56f8fa5e6564fc2303f7903673413b2373cc967ff51c3a7f862471ad5c90e2 new_market 1,907 182,657 55-55 cfe0303b799f75c9e9ce2a833597f21d181f684cadd240f2b23b04179b8cb101 price_change 104,218,244 1,159,645,179 56-453 8f6b347d7dbf9b974c932446415f5a63079b6697ed2c97325ff87b4806402ee2 tick_size_change 4,172 153,289 454-454 b401da627283064bc225216a6eb353d230e01db589bb8171b0578e320c9204e9 EVENT MIX count share price_change 104,218,244 88.30% best_bid_ask 12,474,550 10.57% book 1,275,363 1.08% last_trade_price 50,471 0.04% tick_size_change 4,172 <0.01% new_market 1,907 <0.01% market_resolved 390 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,475,332 12,474,550 782 544 FULL book 1,276,419 1,275,363 1,056 268,434 FULL last_trade_price 50,471 50,471 0 94 FULL market_resolved 390 390 0 2 FULL new_market 1,907 1,907 0 0 FULL price_change 104,225,486 104,218,244 7,242 786 FULL tick_size_change 4,172 4,172 0 16 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,471,241 110,810 18ms 33ms 372ms 2.1min 0 transport_latency_assumed best_bid_ask i 12,466,728 78,256 21ms 33ms 176ms 5.9s 0 transport_latency_assumed best_bid_ask m 12,472,632 6,350,107 5ms 15ms 126ms 7.2s 0 transport_latency_assumed best_bid_ask n 11,917,557 6,045 44ms 61ms 297ms 22.1s 0 transport_latency_assumed best_bid_ask o 12,472,195 5,929,332 5ms 16ms 147ms 6.5s 0 transport_latency_assumed book h 254,290 113,360 53.3s 22.5h 44.7d 132.5d 0 book_staleness book i 738,741 487,500 10.2min 1.3d 47.9d 132.5d 0 book_staleness book m 238,528 140,191 32.5s 19.6h 44.6d 132.5d 0 book_staleness book n 752,237 369,626 11.1min 1.3d 47.9d 132.5d 0 book_staleness book o 266,783 164,686 1.2min 22.8h 44.7d 132.5d 0 book_staleness last_trade_price h 50,234 614 20ms 106ms 828ms 45.2s 0 transport_latency_assumed last_trade_price i 49,917 258 25ms 263ms 2.1s 5.9s 0 transport_latency_assumed last_trade_price m 50,271 24,745 7ms 28ms 224ms 5.1s 0 transport_latency_assumed last_trade_price n 47,087 39 48ms 465ms 6.0s 22.1s 0 transport_latency_assumed last_trade_price o 50,280 24,815 6ms 29ms 244ms 5.4s 0 transport_latency_assumed market_resolved h 374 4 24ms 98ms 39.2s 40.6s 0 transport_latency_assumed market_resolved i 374 21 31ms 150ms 26.4s 49.9s 0 transport_latency_assumed market_resolved m 374 182 6ms 29ms 29.1s 52.6s 0 transport_latency_assumed market_resolved n 375 13 49ms 385ms 5.4min 6.4min 0 transport_latency_assumed market_resolved o 374 170 6ms 31ms 34.4s 56.9s 0 transport_latency_assumed new_market h 1,194 213 180ms 18.6s 59.7s 1.6min 0 transport_latency_assumed new_market i 1,194 256 115ms 17.9s 46.3s 1.6min 0 transport_latency_assumed new_market m 1,194 692 72ms 18.3s 56.7s 1.6min 0 transport_latency_assumed new_market n 1,194 150 183ms 18.7s 42.7s 1.7min 0 transport_latency_assumed new_market o 1,194 596 78ms 19.3s 1.1min 1.9min 0 transport_latency_assumed price_change h 104,131,918 1,031,588 18ms 39ms 522ms 2.1min 0 transport_latency_assumed price_change i 104,033,174 673,526 21ms 44ms 536ms 5.9s 0 transport_latency_assumed price_change m 104,178,584 52,807,358 5ms 18ms 143ms 8.0s 0 transport_latency_assumed price_change n 99,116,635 56,668 45ms 83ms 1.3s 22.3s 0 transport_latency_assumed price_change o 104,139,162 49,649,104 5ms 18ms 160ms 6.8s 0 transport_latency_assumed tick_size_change h 4,172 24 18ms 39ms 290ms 5.8s 0 transport_latency_assumed tick_size_change i 4,172 8 22ms 57ms 104ms 127ms 0 transport_latency_assumed tick_size_change m 4,168 2,038 5ms 13ms 70ms 530ms 0 transport_latency_assumed tick_size_change n 4,112 not meas. 44ms 51ms 81ms 327ms 0 transport_latency_assumed tick_size_change o 4,172 2,102 5ms 10ms 43ms 220ms 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/10/2026-10-09T10.parquet sha256sum 2026-10-09T10.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.