Hour audit: 2026-10-09T04
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-09T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T04:00:00.000068469+00:00 · last event 2026-10-09T04:59:59.999834285+00:00
VOLUME 108,511,749 rows · 1,221,929,349 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 108,330,638 · o: 108,321,593 · m: 108,301,150 · h: 108,291,097 · n: 108,244,876 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 837,527 (0.77%) · o: 51,806,367 (47.74%) · m: 54,808,694 (50.51%) · h: 974,983 (0.90%) · n: 84,178 (0.08%) (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 108,511,749 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 402e4f37bc2f6b9a34bf8c0dc2c034611c837f1c3282dc0b8ae07bce61f72c45
no line in the corpus checksum ledger names this file
joined 108,512,779 to merged 108,511,749, minus 1,030 (minus 0.0009%)
boundary drops 1,030 · 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-09T22:54:52Z 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,058,710 149,400,854 0-46 bf35109f99f00ca1804877734d71078ed20cdb31d86be22abfa7ae5b97c525c9 book 237,147 24,569,631 47-47 6fb8d6cbafcbefe609e4b10ba578501336ab70af2f4e9384ec031d78b4d88f52 last_trade_price 47,051 2,714,620 48-48 c404642956800e68ce32c5de9621d8bad5d48f8fd19585e5f501c53ce76d6db0 market_resolved 1,809 273,758 49-49 b6ecf109dcd58b6c7cb45c38cc44bc43d946313701280f29b6822fd1f7542a01 new_market 1,766 176,367 50-50 df0cd6e96478ada891730eef814367fbeb4700f79d5df9e72f881f84ca76d4ec price_change 96,162,434 1,043,451,935 51-417 40c2f13d4db950890de3bf2a7ff3653d060df5ee3f6f104fab358b9c947c8bf9 tick_size_change 2,832 104,800 418-418 5040d7a7812bd64c677fb8d07ad429719bb943b47224a46acb5dfddac36a479f EVENT MIX count share price_change 96,162,434 88.62% best_bid_ask 12,058,710 11.11% book 237,147 0.22% last_trade_price 47,051 0.04% tick_size_change 2,832 <0.01% market_resolved 1,809 <0.01% new_market 1,766 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,058,826 12,058,710 116 67 FULL book 237,174 237,147 27 55,286 FULL last_trade_price 47,052 47,051 1 1 FULL market_resolved 1,809 1,809 0 0 FULL new_market 1,766 1,766 0 6 FULL price_change 96,163,320 96,162,434 886 317 FULL tick_size_change 2,832 2,832 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,053,174 87,445 18ms 32ms 630ms 1.1min 0 transport_latency_assumed best_bid_ask i 12,057,609 80,521 21ms 31ms 145ms 5.4s 0 transport_latency_assumed best_bid_ask m 12,057,563 6,207,448 4ms 14ms 145ms 7.0s 0 transport_latency_assumed best_bid_ask n 12,056,445 6,250 44ms 61ms 292ms 6.4s 0 transport_latency_assumed best_bid_ask o 12,055,940 5,677,046 4ms 14ms 153ms 14.0s 0 transport_latency_assumed book h 139,797 43,150 32ms 4.9h 31.8d 132.3d 0 book_staleness book i 111,747 16,058 25ms 3.5min 5.6d 113.8d 0 book_staleness book m 118,573 68,402 7ms 27.0min 22.3d 113.8d 0 book_staleness book n 110,302 14,066 50ms 2.4min 5.8d 132.3d 0 book_staleness book o 146,227 95,471 11ms 7.1h 33.6d 132.3d 0 book_staleness last_trade_price h 46,757 676 20ms 73ms 772ms 27.2s 0 transport_latency_assumed last_trade_price i 46,929 440 23ms 99ms 557ms 3.2s 0 transport_latency_assumed last_trade_price m 46,930 23,061 6ms 29ms 313ms 6.6s 0 transport_latency_assumed last_trade_price n 46,674 60 47ms 289ms 2.5s 6.0s 0 transport_latency_assumed last_trade_price o 46,801 22,814 6ms 28ms 277ms 6.6s 0 transport_latency_assumed market_resolved h 1,706 78 20ms 2.0s 46.4s 57.6s 0 transport_latency_assumed market_resolved i 1,706 262 23ms 28.7s 56.7s 57.5s 0 transport_latency_assumed market_resolved m 1,706 736 5ms 26.5s 52.4s 57.8s 0 transport_latency_assumed market_resolved n 1,706 16 45ms 339ms 49.7s 49.8s 0 transport_latency_assumed market_resolved o 1,706 717 5ms 29.0s 50.2s 55.1s 0 transport_latency_assumed new_market h 1,141 239 247ms 21.4s 41.3s 1.7min 0 transport_latency_assumed new_market i 1,147 425 130ms 21.0s 40.4s 1.4min 0 transport_latency_assumed new_market m 1,144 568 124ms 20.6s 42.8s 1.7min 0 transport_latency_assumed new_market n 1,141 130 234ms 20.3s 40.5s 1.5min 0 transport_latency_assumed new_market o 1,143 404 112ms 19.2s 38.7s 1.7min 0 transport_latency_assumed price_change h 96,045,690 843,374 18ms 38ms 713ms 1.1min 0 transport_latency_assumed price_change i 96,108,668 739,802 21ms 38ms 280ms 5.7s 0 transport_latency_assumed price_change m 96,072,402 48,507,088 5ms 16ms 173ms 10.4s 0 transport_latency_assumed price_change n 96,025,776 63,656 44ms 75ms 709ms 6.7s 0 transport_latency_assumed price_change o 96,066,944 46,008,514 5ms 16ms 173ms 14.1s 0 transport_latency_assumed tick_size_change h 2,832 21 18ms 28ms 57ms 618ms 0 transport_latency_assumed tick_size_change i 2,832 19 21ms 30ms 392ms 406ms 0 transport_latency_assumed tick_size_change m 2,832 1,391 4ms 12ms 74ms 236ms 0 transport_latency_assumed tick_size_change n 2,832 not meas. 44ms 57ms 161ms 3.0s 0 transport_latency_assumed tick_size_change o 2,832 1,401 4ms 12ms 80ms 245ms 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/04/2026-10-09T04.parquet sha256sum 2026-10-09T04.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.