Hour audit: 2026-10-03T09
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-03T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T09:00:00.000034677+00:00 · last event 2026-10-03T09:59:59.999862104+00:00
VOLUME 106,694,071 rows · 1,090,649,739 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 106,616,640 · m: 106,606,572 · h: 106,590,738 · i: 106,585,609 · g: 106,521,086 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,632,531 (3.40%) · m: 101,950,913 (95.55%) · h: 748,655 (0.70%) · i: 316,329 (0.30%) · g: 45,643 (0.04%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,694,071 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0f1a87812bb16f23e18558f141f2546bb541309fd0449f363855bdcaa9ce5e2a
the corpus checksum ledger names this file with the same digest
joined 106,696,495 to merged 106,694,071, minus 2,424 (minus 0.0023%)
boundary drops 2,424 · 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-03T11:44:41Z 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 9,039,115 105,479,261 0-34 ee2ab57d536fb4333c10be8a286561fb4175b8baf73989334db646c6ee8460a4 book 143,538 14,875,587 35-35 d9bbb527ec802411ebf276b683555b543679892285f7d2507383861216b9c6f4 last_trade_price 53,156 3,007,466 36-36 0422639cde649d9c8ac851d7a69d27c218e6a2f1853057212a7d44fc7cf882ae market_resolved 545 90,250 37-37 2659af9a42291592549122d4b76619073dec69379b6390bb3fbff253984fd55e new_market 345 40,151 38-38 790d8dfdfecb4ff97842ede69d7d98c0176ab50ce1d4f97b6efda6f3248534ee price_change 97,454,900 965,849,441 39-410 370bf95837bb8e1521bc56f9faa7945380ccc453e56b8eee1a05fead07470f34 tick_size_change 2,472 90,065 411-411 69a0ca90ac7848d412c1ce48bd55497a578f6b28b9813a16d8fdeafa5bbd0fb8 EVENT MIX count share price_change 97,454,900 91.34% best_bid_ask 9,039,115 8.47% book 143,538 0.13% last_trade_price 53,156 0.05% tick_size_change 2,472 <0.01% market_resolved 545 <0.01% new_market 345 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,039,345 9,039,115 230 64 FULL book 143,560 143,538 22 16,161 FULL last_trade_price 53,160 53,156 4 0 FULL market_resolved 545 545 0 0 FULL new_market 345 345 0 0 FULL price_change 97,457,068 97,454,900 2,168 231 FULL tick_size_change 2,472 2,472 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,035,082 293 77ms 95ms 235ms 12.8s 0 transport_latency_assumed best_bid_ask h 9,038,756 52,685 18ms 23ms 75ms 30.2s 0 transport_latency_assumed best_bid_ask i 9,038,567 19,603 21ms 27ms 71ms 4.0s 0 transport_latency_assumed best_bid_ask k 9,038,400 287,587 13ms 20ms 60ms 19.5s 0 transport_latency_assumed best_bid_ask m 9,038,917 8,678,947 4ms 9ms 43ms 4.5s 0 transport_latency_assumed book g 134,601 29,981 93ms 2.2h 24.6d 108.0d 0 book_staleness book h 107,590 2,728 21ms 42ms 653ms 107.9d 0 book_staleness book i 108,700 2,741 23ms 58ms 30.6min 107.9d 0 book_staleness book k 107,870 6,301 16ms 35ms 37.0s 108.0d 0 book_staleness book m 109,582 101,787 6ms 21ms 3.9h 27.8d 0 book_staleness last_trade_price g 52,055 10 86ms 279ms 10.9s 12.8s 0 transport_latency_assumed last_trade_price h 53,124 933 19ms 33ms 269ms 3.8s 0 transport_latency_assumed last_trade_price i 53,064 341 23ms 44ms 552ms 2.4s 0 transport_latency_assumed last_trade_price k 53,020 2,922 14ms 27ms 225ms 2.0s 0 transport_latency_assumed last_trade_price m 53,117 48,950 6ms 16ms 154ms 1.0s 0 transport_latency_assumed market_resolved g 531 not meas. 81ms 380ms 48.8s 48.8s 0 transport_latency_assumed market_resolved h 531 4 20ms 74ms 53.0s 53.0s 0 transport_latency_assumed market_resolved i 531 not meas. 23ms 36.1s 46.3s 56.2s 0 transport_latency_assumed market_resolved k 531 25 15ms 57ms 55.3s 55.3s 0 transport_latency_assumed market_resolved m 531 516 5ms 38.0s 53.2s 53.2s 0 transport_latency_assumed new_market g 259 15 113ms 390ms 38.4s 1.2min 0 transport_latency_assumed new_market h 259 47 40ms 224ms 1.4min 1.7min 0 transport_latency_assumed new_market i 259 56 36ms 10.0s 32.7s 1.6min 0 transport_latency_assumed new_market k 259 35 48ms 502ms 1.5min 1.7min 0 transport_latency_assumed new_market m 259 192 26ms 8.0s 14.5s 1.6min 0 transport_latency_assumed price_change g 97,296,086 15,344 78ms 99ms 567ms 12.8s 0 transport_latency_assumed price_change h 97,388,006 692,254 18ms 25ms 149ms 32.7s 0 transport_latency_assumed price_change i 97,382,016 293,584 22ms 28ms 189ms 4.4s 0 transport_latency_assumed price_change k 97,414,088 3,335,558 13ms 21ms 109ms 19.5s 0 transport_latency_assumed price_change m 97,401,694 93,118,160 4ms 10ms 64ms 8.0s 0 transport_latency_assumed tick_size_change g 2,472 not meas. 77ms 90ms 118ms 204ms 0 transport_latency_assumed tick_size_change h 2,472 4 18ms 24ms 41ms 55ms 0 transport_latency_assumed tick_size_change i 2,472 4 21ms 26ms 52ms 68ms 0 transport_latency_assumed tick_size_change k 2,472 103 13ms 20ms 32ms 199ms 0 transport_latency_assumed tick_size_change m 2,472 2,361 4ms 9ms 32ms 82ms 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-03/09/2026-10-03T09.parquet sha256sum 2026-10-03T09.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.