Hour audit: 2026-10-05T16
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-05T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T16:00:00.000087222+00:00 · last event 2026-10-05T16:59:59.999833283+00:00
VOLUME 112,379,366 rows · 1,267,021,544 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 111,636,325 · i: 111,553,869 · n: 111,437,426 · o: 111,359,211 · m: 110,786,367 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 824,360 (0.73%) · i: 508,766 (0.45%) · n: 55,801 (0.05%) · o: 55,647,004 (49.52%) · m: 55,343,435 (49.25%) (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 112,379,366 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 238ef4a092d40365d296a67fd837be9b5d63cea85ec3a7e12ef1a3c325b00db3
the corpus checksum ledger names this file with the same digest
joined 112,380,568 to merged 112,379,366, minus 1,202 (minus 0.0011%)
boundary drops 1,202 · 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-05T18:00:31Z 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 9,640,940 124,451,370 0-36 bc0ae8a275807d447381990a260c0183ff43444a29dad84768aa937aafb0f577 book 141,023 15,661,922 37-37 7aefad767bb94d90a9b02fe6f19c885228e7bb7dabe4f352a17d626ef58ff8e9 last_trade_price 59,482 3,407,062 38-38 6552b02e83e65a7a6c233b1e34bb62fc2d108c5da79177922c1c7fd57b02be75 market_resolved 1,058 155,341 39-39 3847b268b0c20a0a67b10cc8bd55e8f9a5baf2162636ba04858d3b9a7239e73e new_market 2,584 257,874 40-40 b62c4befd81e2edda77255146c92978b8a678cc6e9cdcd8139948b25ec59ad4e price_change 102,531,563 1,121,704,975 41-432 d0b83e3c49c1fad38baff9f6eabb742b370f4770e2fb39c1fe35599081a98105 tick_size_change 2,716 100,777 433-433 0211bf5242bcbc8602cd960885c30dae106dd05c15b095f9716b561ef76a6f17 EVENT MIX count share price_change 102,531,563 91.24% best_bid_ask 9,640,940 8.58% book 141,023 0.13% last_trade_price 59,482 0.05% tick_size_change 2,716 <0.01% new_market 2,584 <0.01% market_resolved 1,058 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,641,054 9,640,940 114 3,802 FULL book 141,031 141,023 8 6,710 FULL last_trade_price 59,482 59,482 0 114 FULL market_resolved 1,058 1,058 0 19 FULL new_market 2,584 2,584 0 0 FULL price_change 102,532,643 102,531,563 1,080 7,016 FULL tick_size_change 2,716 2,716 0 22 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,582,301 64,468 18ms 31ms 329ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,578,024 39,766 22ms 34ms 178ms 4.0s 0 transport_latency_assumed best_bid_ask m 9,516,944 4,742,754 5ms 15ms 102ms 9.6s 0 transport_latency_assumed best_bid_ask n 9,591,201 2,625 45ms 69ms 386ms 22.1s 0 transport_latency_assumed best_bid_ask o 9,550,530 4,791,327 5ms 15ms 95ms 3.8s 0 transport_latency_assumed book h 125,863 5,885 24ms 231ms 3.6h 110.2d 0 book_staleness book i 124,424 4,694 26ms 405ms 1.5h 110.2d 0 book_staleness book m 123,311 64,711 8ms 42ms 32.0min 110.3d 0 book_staleness book n 125,555 6,718 57ms 3.4s 7.3h 110.3d 0 book_staleness book o 122,884 59,015 8ms 39ms 2.9min 110.3d 0 book_staleness last_trade_price h 59,381 535 21ms 105ms 699ms 50.4s 0 transport_latency_assumed last_trade_price i 58,991 247 25ms 213ms 1.7s 4.0s 0 transport_latency_assumed last_trade_price m 58,672 30,820 6ms 22ms 182ms 1.5s 0 transport_latency_assumed last_trade_price n 58,136 8 56ms 928ms 9.5s 22.1s 0 transport_latency_assumed last_trade_price o 58,980 27,872 7ms 24ms 164ms 1.4s 0 transport_latency_assumed market_resolved h 948 40 22ms 111ms 53.7s 1.2min 0 transport_latency_assumed market_resolved i 946 150 26ms 35.2s 50.3s 2.4min 0 transport_latency_assumed market_resolved m 941 419 7ms 38.8s 54.9s 2.5min 0 transport_latency_assumed market_resolved n 948 2 49ms 321ms 53.0s 2.5min 0 transport_latency_assumed market_resolved o 943 447 6ms 132ms 55.3s 2.2min 0 transport_latency_assumed new_market h 1,668 373 9.0s 43.3s 1.0min 1.6min 0 transport_latency_assumed new_market i 1,668 355 8.4s 42.6s 1.0min 1.8min 0 transport_latency_assumed new_market m 1,668 799 111ms 43.3s 1.0min 1.9min 0 transport_latency_assumed new_market n 1,668 158 397ms 41.2s 58.9s 1.7min 0 transport_latency_assumed new_market o 1,668 899 180ms 41.9s 57.5s 1.8min 0 transport_latency_assumed price_change h 101,863,448 753,047 19ms 39ms 508ms 1.1min 0 transport_latency_assumed price_change i 101,787,112 463,549 22ms 46ms 648ms 4.0s 0 transport_latency_assumed price_change m 101,082,151 50,502,541 5ms 17ms 115ms 9.7s 0 transport_latency_assumed price_change n 101,657,222 46,290 45ms 114ms 3.7s 22.3s 0 transport_latency_assumed price_change o 101,621,510 50,766,136 5ms 17ms 106ms 3.8s 0 transport_latency_assumed tick_size_change h 2,716 12 18ms 27ms 73ms 2.0s 0 transport_latency_assumed tick_size_change i 2,704 5 22ms 31ms 70ms 86ms 0 transport_latency_assumed tick_size_change m 2,680 1,391 5ms 12ms 37ms 52ms 0 transport_latency_assumed tick_size_change n 2,696 not meas. 45ms 58ms 111ms 584ms 0 transport_latency_assumed tick_size_change o 2,696 1,308 5ms 14ms 42ms 229ms 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-05/16/2026-10-05T16.parquet sha256sum 2026-10-05T16.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.