Hour audit: 2026-10-08T23
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-08T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-08T23:00:00.000274787+00:00 · last event 2026-10-08T23:59:59.999629365+00:00
VOLUME 132,915,217 rows · 1,534,518,766 bytes (1.43 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 132,786,615 · o: 132,666,343 · n: 132,636,606 · i: 132,617,568 · h: 132,547,743 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 64,552,377 (48.57%) · o: 66,104,806 (49.73%) · n: 111,717 (0.08%) · i: 924,862 (0.70%) · h: 1,221,455 (0.92%) (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 132,915,217 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 737aeb1d35d83d1160c4ad509439bfacb79a3765ce92a498d0b654f8df791e55
the corpus checksum ledger names this file with the same digest
joined 132,921,875 to merged 132,915,217, minus 6,658 (minus 0.0050%)
boundary drops 6,658 · 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-09T01:30:20Z 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 12,702,154 159,288,900 0-48 0995920ec87b0be0da7c64454205c43416b9127d274d42206957c934296cee6f book 168,814 17,045,442 49-49 b8fb94db71569dadd154b8c7cb5ce75bc0a289cc7b556794c6c986d1af944a65 last_trade_price 62,454 3,516,183 50-50 026a6332b27256764f704355f285e6233ae11df5569980b3190f42af79e01b5d market_resolved 451 72,204 51-51 0b3dad961fc7cb4f1c83351a1c3d775116818c0423fc1541e54cf840dff305ba new_market 2,272 205,448 52-52 d2509ec771e7450166d71ebdce61b7e0acfdbcdfadb24dc1e9160b5fe94c0322 price_change 119,977,136 1,352,805,481 53-510 37ea7f74813ed32375ed20bbc60a10063744c947c20bebf2f7ecddbe0e4defef tick_size_change 1,936 72,541 511-511 0c22b54a550adf774a484542898596d91c75c2435a8a38d1d076bbf0f42deb66 EVENT MIX count share price_change 119,977,136 90.27% best_bid_ask 12,702,154 9.56% book 168,814 0.13% last_trade_price 62,454 0.05% new_market 2,272 <0.01% tick_size_change 1,936 <0.01% market_resolved 451 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,702,332 12,702,154 178 107 FULL book 168,814 168,814 0 13,980 FULL last_trade_price 62,454 62,454 0 0 FULL market_resolved 451 451 0 1 FULL new_market 2,272 2,272 0 0 FULL price_change 119,983,616 119,977,136 6,480 147 FULL tick_size_change 1,936 1,936 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,692,140 113,774 18ms 36ms 454ms 1.2min 0 transport_latency_assumed best_bid_ask i 12,693,851 83,709 21ms 36ms 176ms 29.0s 0 transport_latency_assumed best_bid_ask m 12,699,155 6,266,564 5ms 17ms 123ms 8.8s 0 transport_latency_assumed best_bid_ask n 12,695,155 6,997 45ms 68ms 367ms 19.6s 0 transport_latency_assumed best_bid_ask o 12,696,952 6,231,110 5ms 18ms 129ms 7.9s 0 transport_latency_assumed book h 136,173 11,119 25ms 1.2s 10.6h 132.0d 0 book_staleness book i 135,259 10,012 26ms 1.4s 11.1h 113.5d 0 book_staleness book m 133,806 62,483 7ms 95ms 6.5h 113.5d 0 book_staleness book n 134,145 11,463 54ms 6.9s 19.4h 132.1d 0 book_staleness book o 133,802 73,737 7ms 86ms 6.3h 113.5d 0 book_staleness last_trade_price h 61,574 442 22ms 298ms 1.7s 42.5s 0 transport_latency_assumed last_trade_price i 61,831 347 25ms 303ms 16.1s 29.0s 0 transport_latency_assumed last_trade_price m 62,070 27,987 6ms 31ms 203ms 3.9s 0 transport_latency_assumed last_trade_price n 60,439 128 53ms 1.3s 10.5s 19.6s 0 transport_latency_assumed last_trade_price o 62,053 33,550 6ms 28ms 226ms 5.6s 0 transport_latency_assumed market_resolved h 425 30 21ms 225ms 55.4s 55.4s 0 transport_latency_assumed market_resolved i 424 67 27ms 35.7s 49.9s 49.9s 0 transport_latency_assumed market_resolved m 425 150 6ms 37.4s 51.6s 51.6s 0 transport_latency_assumed market_resolved n 424 2 53ms 430ms 48.5s 48.6s 0 transport_latency_assumed market_resolved o 425 202 6ms 38.3s 52.5s 52.6s 0 transport_latency_assumed new_market h 1,315 384 238ms 1.7min 2.4min 2.9min 0 transport_latency_assumed new_market i 1,315 395 129ms 1.7min 2.6min 2.9min 0 transport_latency_assumed new_market m 1,315 616 84ms 1.7min 2.5min 2.9min 0 transport_latency_assumed new_market n 1,315 405 235ms 1.7min 2.4min 2.8min 0 transport_latency_assumed new_market o 1,315 472 116ms 1.7min 2.5min 2.9min 0 transport_latency_assumed price_change h 119,654,184 1,095,694 19ms 45ms 769ms 1.2min 0 transport_latency_assumed price_change i 119,722,952 830,324 22ms 45ms 481ms 29.0s 0 transport_latency_assumed price_change m 119,887,908 58,193,582 5ms 20ms 138ms 9.2s 0 transport_latency_assumed price_change n 119,743,192 92,722 45ms 85ms 1.2s 21.1s 0 transport_latency_assumed price_change o 119,769,864 59,764,814 5ms 20ms 145ms 9.4s 0 transport_latency_assumed tick_size_change h 1,932 12 19ms 41ms 391ms 1.0s 0 transport_latency_assumed tick_size_change i 1,936 8 22ms 46ms 496ms 1.2s 0 transport_latency_assumed tick_size_change m 1,936 995 5ms 17ms 75ms 199ms 0 transport_latency_assumed tick_size_change n 1,936 not meas. 45ms 65ms 132ms 235ms 0 transport_latency_assumed tick_size_change o 1,932 921 5ms 17ms 75ms 106ms 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/23/2026-10-08T23.parquet sha256sum 2026-10-08T23.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.