Hour audit: 2026-10-04T00
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-04T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T00:00:00.000025403+00:00 · last event 2026-10-04T00:59:59.999996160+00:00
VOLUME 144,067,743 rows · 1,644,349,287 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 140,007,146 · h: 140,001,780 · i: 127,862,937 · g: 104,704,586 · k: 98,533,800 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 130,267,474 (90.42%) · h: 3,298,599 (2.29%) · i: 1,220,018 (0.85%) · g: 1,955,027 (1.36%) · k: 7,326,625 (5.09%) (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 144,067,743 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d3cb56717e5a13849647ca5f773d3cd5201357eead8aecc50070c364b5d500fb
the corpus checksum ledger names this file with the same digest
joined 144,092,499 to merged 144,067,743, minus 24,756 (minus 0.0172%)
boundary drops 24,756 · 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-04T02:53:48Z as ghikm
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 13,333,662 156,468,197 0-50 3fe335c7ba8bad19f8ccef203890ab516a8c07b9c75e56ceb121d8e3f8085fe5 book 4,119,039 137,875,266 51-66 2ed080f7eaeeb59c43c9be92fd35c7464f08db4c5f2f78c5fcddcbc1d121fbd5 last_trade_price 60,293 3,390,571 67-67 f1322b3141dd9c169ba3307e3dc0b67ce9cf62825fe2fced6578b8d9909ff53e market_resolved 39,290 1,385,802 68-68 617c0ffebd0a62ea0e4cb06a4aa1f3aa5521f745f302ec9d83a68202196e31bc new_market 28,995 911,505 69-69 d732ed72a1a6f8f0d162ea2897af85a9cd9deaed3dd6ea8be961a3ff5ac058b1 price_change 126,481,068 1,342,483,440 70-552 ce4372b62438132c9e6d5869e26326733256418cca599178a5230eb5f6770596 tick_size_change 5,396 198,277 553-553 461da5103ab4ff43947f544ae3bf599b5dc89b79b00e78e8d56e8d3fbbc49f0e EVENT MIX count share price_change 126,481,068 87.79% best_bid_ask 13,333,662 9.26% book 4,119,039 2.86% last_trade_price 60,293 0.04% market_resolved 39,290 0.03% new_market 28,995 0.02% tick_size_change 5,396 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,333,713 13,333,662 51 13,212 FULL book 4,143,089 4,119,039 24,050 230,606 FULL last_trade_price 60,293 60,293 0 1,162 FULL market_resolved 39,290 39,290 0 5,143 FULL new_market 28,998 28,995 3 4,906 FULL price_change 126,481,720 126,481,068 652 13,932 FULL tick_size_change 5,396 5,396 0 645 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,749,560 336 81ms 98ms 231ms 8.6s 0 transport_latency_assumed best_bid_ask h 13,332,636 306,427 18ms 26ms 94ms 21.3s 0 transport_latency_assumed best_bid_ask i 12,119,756 90,207 21ms 29ms 82ms 1.7s 0 transport_latency_assumed best_bid_ask k 9,173,004 525,350 14ms 24ms 77ms 1.5s 0 transport_latency_assumed best_bid_ask m 13,332,802 12,411,342 5ms 13ms 65ms 2.6s 0 transport_latency_assumed book g 2,773,644 1,943,634 40.2min 2.0d 45.9d 127.1d 0 book_staleness book h 150,932 11,745 22ms 46.6min 24.7d 108.6d 0 book_staleness book i 1,115,462 215,326 26.2min 2.0d 42.4d 127.1d 0 book_staleness book k 3,303,015 1,827,762 42.2min 2.2d 46.1d 127.1d 0 book_staleness book m 158,102 120,572 8ms 1.6h 26.6d 127.1d 0 book_staleness last_trade_price g 43,494 9 84ms 237ms 4.2s 8.6s 0 transport_latency_assumed last_trade_price h 60,224 1,896 19ms 36ms 235ms 4.8s 0 transport_latency_assumed last_trade_price i 54,784 598 22ms 39ms 326ms 1.8s 0 transport_latency_assumed last_trade_price k 40,826 2,844 15ms 33ms 263ms 1.8s 0 transport_latency_assumed last_trade_price m 60,181 54,946 6ms 18ms 145ms 1.8s 0 transport_latency_assumed market_resolved g 8,590 5,575 13.3min 31.6min 40.3min 42.4min 0 transport_latency_assumed market_resolved h 2,496 151 19ms 56ms 52.4s 55.2s 0 transport_latency_assumed market_resolved i 3,164 263 25ms 9.6min 12.6min 12.8min 0 transport_latency_assumed market_resolved k 38,343 31,031 53.9min 1.4h 1.7h 1.9h 0 transport_latency_assumed market_resolved m 2,497 2,270 6ms 38ms 53.6s 58.0s 0 transport_latency_assumed new_market g 3,601 3,071 23.1min 33.7min 33.9min 35.4min 0 transport_latency_assumed new_market h 472 84 71ms 15.7s 45.5s 1.5min 0 transport_latency_assumed new_market i 499 82 62ms 4.9min 8.3min 10.0min 0 transport_latency_assumed new_market k 28,942 25,483 1.1h 1.6h 1.8h 1.8h 0 transport_latency_assumed new_market m 472 275 38ms 13.5s 1.1min 1.8min 0 transport_latency_assumed price_change g 92,121,529 2,402 81ms 103ms 387ms 8.7s 0 transport_latency_assumed price_change h 126,449,624 2,978,204 18ms 28ms 117ms 21.5s 0 transport_latency_assumed price_change i 114,564,360 913,494 21ms 31ms 111ms 2.5s 0 transport_latency_assumed price_change k 85,945,942 4,913,948 14ms 25ms 89ms 1.7s 0 transport_latency_assumed price_change m 126,447,696 117,673,020 5ms 14ms 68ms 3.7s 0 transport_latency_assumed tick_size_change g 4,168 not meas. 81ms 100ms 188ms 419ms 0 transport_latency_assumed tick_size_change h 5,396 92 18ms 26ms 90ms 387ms 0 transport_latency_assumed tick_size_change i 4,912 48 21ms 28ms 68ms 206ms 0 transport_latency_assumed tick_size_change k 3,728 207 13ms 23ms 74ms 258ms 0 transport_latency_assumed tick_size_change m 5,396 5,049 5ms 14ms 61ms 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-04/00/2026-10-04T00.parquet sha256sum 2026-10-04T00.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.