Hour audit: 2026-10-08T05
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-08T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T05:00:00.000004232+00:00 · last event 2026-10-08T05:59:59.999985243+00:00
VOLUME 117,451,224 rows · 1,341,847,212 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 116,961,496 · m: 116,951,724 · h: 116,915,902 · n: 116,794,673 · i: 116,576,027 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,591,508 (47.33%) · m: 59,920,120 (51.02%) · h: 1,152,187 (0.98%) · n: 170,047 (0.14%) · i: 617,362 (0.53%) (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 117,451,224 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 60cd239ac4561bec87177c44eded29c3db263125635ee18f935b7520d006d549
the corpus checksum ledger names this file with the same digest
joined 117,452,828 to merged 117,451,224, minus 1,604 (minus 0.0014%)
boundary drops 1,604 · 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-08T07:03:55Z 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 11,533,967 141,226,125 0-43 a2bb3fb13aade800cfc2b8062ba0187f9671e388ffeaffed5d0b31257f4fb4bc book 915,050 79,066,706 44-47 ccf80296add9660b71ee00762287abcbf3d8d7aa1319b3e134c9c211b288d5a9 last_trade_price 46,942 2,731,040 48-48 252150b70c0a66b8d6baf541dae456e3a88ec4f894a1101a3091498b3e3b3b7a market_resolved 1,966 310,855 49-49 95f74313ce79dbe16414a3161cf3258bf45712dd09926bd5b3ff68f7de60dee8 new_market 741 83,327 50-50 9e90ca9fe6040e592af37914a423d9cedd586032c931e8f02db0a0ee497e328d price_change 104,948,466 1,116,943,031 51-451 d3a4bebc1ae81b0addc400964fe7c9bd739c5b95e2e7f7b7a5e716304bd29e71 tick_size_change 4,092 147,923 452-452 58f24f7ff0407721a0af420d3a158549ede89c67b759cf5102676a7e5c3ae91d EVENT MIX count share price_change 104,948,466 89.35% best_bid_ask 11,533,967 9.82% book 915,050 0.78% last_trade_price 46,942 0.04% tick_size_change 4,092 <0.01% market_resolved 1,966 <0.01% new_market 741 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,534,053 11,533,967 86 59 FULL book 915,250 915,050 200 260,013 FULL last_trade_price 46,942 46,942 0 1 FULL market_resolved 1,966 1,966 0 0 FULL new_market 741 741 0 0 FULL price_change 104,949,784 104,948,466 1,318 89 FULL tick_size_change 4,092 4,092 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,529,757 81,996 18ms 30ms 173ms 1.0min 0 transport_latency_assumed best_bid_ask i 11,532,894 53,947 21ms 31ms 111ms 2.7s 0 transport_latency_assumed best_bid_ask m 11,531,823 5,936,402 4ms 14ms 77ms 4.1s 0 transport_latency_assumed best_bid_ask n 11,530,879 2,324 43ms 57ms 200ms 8.4s 0 transport_latency_assumed best_bid_ask o 11,531,958 5,459,298 4ms 14ms 78ms 5.1s 0 transport_latency_assumed book h 492,783 206,116 11.4min 1.9h 46.7d 131.3d 0 book_staleness book i 124,283 16,009 27ms 1.4h 28.9d 112.8d 0 book_staleness book m 493,261 279,472 11.6min 1.9h 46.7d 131.3d 0 book_staleness book n 398,070 141,959 6.8min 1.9h 46.7d 131.3d 0 book_staleness book o 486,526 271,494 11.6min 1.9h 46.7d 131.3d 0 book_staleness last_trade_price h 46,716 413 20ms 83ms 495ms 15.7s 0 transport_latency_assumed last_trade_price i 46,806 226 24ms 106ms 645ms 2.6s 0 transport_latency_assumed last_trade_price m 46,824 24,116 6ms 23ms 170ms 1.3s 0 transport_latency_assumed last_trade_price n 46,786 23 48ms 460ms 3.6s 8.4s 0 transport_latency_assumed last_trade_price o 46,804 22,164 6ms 22ms 155ms 1.3s 0 transport_latency_assumed market_resolved h 1,856 47 20ms 17.2s 54.3s 54.8s 0 transport_latency_assumed market_resolved i 1,856 59 23ms 20.1s 55.3s 56.1s 0 transport_latency_assumed market_resolved m 1,856 976 6ms 21.0s 55.5s 56.1s 0 transport_latency_assumed market_resolved n 1,856 57 45ms 125ms 49.7s 51.3s 0 transport_latency_assumed market_resolved o 1,856 827 6ms 16.4s 46.2s 57.3s 0 transport_latency_assumed new_market h 536 103 264ms 21.9s 23.7s 1.6min 0 transport_latency_assumed new_market i 536 107 92ms 21.9s 23.7s 1.6min 0 transport_latency_assumed new_market m 536 211 67ms 17.9s 50.6s 1.6min 0 transport_latency_assumed new_market n 536 44 149ms 16.3s 19.0s 1.5min 0 transport_latency_assumed new_market o 536 276 103ms 16.9s 24.0s 1.6min 0 transport_latency_assumed price_change h 104,840,162 863,460 18ms 36ms 271ms 1.8min 0 transport_latency_assumed price_change i 104,865,560 546,968 21ms 38ms 276ms 4.4s 0 transport_latency_assumed price_change m 104,873,332 53,676,970 5ms 16ms 90ms 6.5s 0 transport_latency_assumed price_change n 104,812,454 25,640 44ms 75ms 1.2s 11.7s 0 transport_latency_assumed price_change o 104,889,724 49,835,428 5ms 16ms 91ms 5.2s 0 transport_latency_assumed tick_size_change h 4,092 52 19ms 34ms 83ms 146ms 0 transport_latency_assumed tick_size_change i 4,092 46 22ms 41ms 110ms 254ms 0 transport_latency_assumed tick_size_change m 4,092 1,973 5ms 26ms 248ms 317ms 0 transport_latency_assumed tick_size_change n 4,092 not meas. 44ms 78ms 167ms 270ms 0 transport_latency_assumed tick_size_change o 4,092 2,021 5ms 16ms 87ms 306ms 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-08/05/2026-10-08T05.parquet sha256sum 2026-10-08T05.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.