Hour audit: 2026-10-09T15
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T15 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 131,279,357 rows · 1,592,569,296 bytes (1.48 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 130,411,280 · m: 130,404,875 · h: 130,345,223 · i: 130,052,473 · n: 129,712,419 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 65,271,289 (49.72%) · m: 62,697,269 (47.76%) · h: 1,705,313 (1.30%) · i: 1,265,688 (0.96%) · n: 339,798 (0.26%) (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 131,279,357 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2143860d5000f513c9cf37c44763e4623cd8a0ffd71fcf0dc3a98eb3693b40e4
no line in the corpus checksum ledger names this file
joined 131,287,433 to merged 131,279,357, minus 8,076 (minus 0.0062%)
boundary drops 8,076 · 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-10T04:50:53Z 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 6/8 pass, 1 finding, 1 not evaluated
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
FINDING the checksum ledger does not name this file
SKIPPED the hour's minutes have not been measured
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,119,588 159,832,182 0-46 2677139ebec9b1b4d682b7834b222f5e75d1963fbe7ca4172b988b9fdf1a7fe0 book 1,293,207 100,978,056 47-51 69146aa4b25cc26dfde704bbf820498b5b6fdd45f627d6f964a9b92502029769 last_trade_price 62,587 3,745,741 52-52 da8a50363ee471eb9389301321407c601299df819eab268fbd4993cdf6d77a3d market_resolved 1,397 221,268 53-53 47a69750e32389a7f0995e04d8246e35a89c5185246b675db48c3f74c609c40c new_market 2,376 213,090 54-54 2eebd93778d22f61885e61e25630ee0193cba506e30ff192ac42a7ca4684f4c5 price_change 117,795,330 1,325,906,298 55-504 caf2022fb583ddf4de4e210c5d355382fcf19a23d33fee94479d5743ba3a2d61 tick_size_change 4,872 177,954 505-505 23f091d55ab7b2f6c90b732b5f69b07ca27fd7bc9994254bb291ec29200e74d1 EVENT MIX count share price_change 117,795,330 89.73% best_bid_ask 12,119,588 9.23% book 1,293,207 0.99% last_trade_price 62,587 0.05% tick_size_change 4,872 <0.01% new_market 2,376 <0.01% market_resolved 1,397 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,119,719 12,119,588 131 91 FULL book 1,299,663 1,293,207 6,456 256,494 FULL last_trade_price 62,587 62,587 0 2 FULL market_resolved 1,408 1,397 11 25 FULL new_market 2,376 2,376 0 0 FULL price_change 117,796,808 117,795,330 1,478 302 FULL tick_size_change 4,872 4,872 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,114,536 133,089 19ms 43ms 427ms 45.7s 0 transport_latency_assumed best_bid_ask i 12,113,404 103,823 21ms 41ms 226ms 16.3s 0 transport_latency_assumed best_bid_ask m 12,117,549 5,840,572 6ms 21ms 163ms 7.4s 0 transport_latency_assumed best_bid_ask n 12,107,423 5,869 46ms 77ms 456ms 22.7s 0 transport_latency_assumed best_bid_ask o 12,116,883 6,036,235 6ms 22ms 172ms 8.1s 0 transport_latency_assumed book h 494,595 237,766 3.5min 1.5d 48.1d 132.7d 0 book_staleness book i 341,379 151,907 1.1min 1.0d 44.9d 132.7d 0 book_staleness book m 509,668 310,319 3.8min 1.5d 48.1d 132.7d 0 book_staleness book n 540,116 270,901 4.3min 1.5d 48.1d 132.7d 0 book_staleness book o 523,971 322,314 3.9min 1.5d 48.1d 132.7d 0 book_staleness last_trade_price h 62,386 589 22ms 237ms 1.6s 39.7s 0 transport_latency_assumed last_trade_price i 62,014 426 29ms 514ms 4.2s 16.2s 0 transport_latency_assumed last_trade_price m 62,544 29,904 7ms 32ms 226ms 2.3s 0 transport_latency_assumed last_trade_price n 59,805 36 61ms 1.5s 11.4s 22.8s 0 transport_latency_assumed last_trade_price o 62,394 31,632 7ms 33ms 284ms 4.2s 0 transport_latency_assumed market_resolved h 1,353 5 30ms 21.1s 50.4s 54.2s 0 transport_latency_assumed market_resolved i 1,367 181 32ms 11.1s 43.6s 56.3s 0 transport_latency_assumed market_resolved m 1,367 569 7ms 13.5s 45.2s 55.1s 0 transport_latency_assumed market_resolved n 1,364 19 64ms 5.6s 48.3s 48.4s 0 transport_latency_assumed market_resolved o 1,353 623 7ms 21.8s 50.9s 55.8s 0 transport_latency_assumed new_market h 1,357 271 187ms 41.8s 54.2s 1.1min 0 transport_latency_assumed new_market i 1,357 373 126ms 37.1s 54.3s 1.7min 0 transport_latency_assumed new_market m 1,357 854 81ms 40.5s 56.6s 1.8min 0 transport_latency_assumed new_market n 1,357 239 230ms 37.8s 55.2s 1.4min 0 transport_latency_assumed new_market o 1,357 639 97ms 37.7s 53.0s 1.6min 0 transport_latency_assumed price_change h 117,666,124 1,333,574 20ms 56ms 731ms 45.7s 0 transport_latency_assumed price_change i 117,528,080 1,008,974 22ms 62ms 1.2s 16.4s 0 transport_latency_assumed price_change m 117,707,518 56,512,687 6ms 24ms 172ms 7.5s 0 transport_latency_assumed price_change n 116,997,482 62,734 47ms 136ms 4.3s 22.8s 0 transport_latency_assumed price_change o 117,700,454 58,877,361 6ms 25ms 182ms 9.7s 0 transport_latency_assumed tick_size_change h 4,872 19 18ms 32ms 92ms 385ms 0 transport_latency_assumed tick_size_change i 4,872 4 21ms 41ms 83ms 176ms 0 transport_latency_assumed tick_size_change m 4,872 2,364 6ms 14ms 47ms 215ms 0 transport_latency_assumed tick_size_change n 4,872 not meas. 45ms 64ms 248ms 788ms 0 transport_latency_assumed tick_size_change o 4,868 2,485 6ms 13ms 43ms 148ms 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-09/15/2026-10-09T15.parquet sha256sum 2026-10-09T15.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.