Hour audit: 2026-10-09T23
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-09T23 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 121,814,081 rows · 1,329,725,949 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 121,684,708 · o: 121,456,569 · m: 121,285,897 · h: 121,242,102 · n: 121,211,411 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 621,392 (0.51%) · o: 60,685,527 (49.82%) · m: 60,113,945 (49.35%) · h: 331,883 (0.27%) · n: 61,334 (0.05%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 121,814,081 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a894d0edcb29eaa1d1a50839a422fa56f69ecc22e609793dd549e1fa29ed9e3b
no line in the corpus checksum ledger names this file
joined 121,814,767 to merged 121,814,081, minus 686 (minus 0.0006%)
boundary drops 686 · 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-10T09:10: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 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,688,253 154,301,315 0-48 bf938ef486492763c3f7fe598fbfcae0414c5f4e7385d63b6bf6c9325a8881d7 book 126,091 11,812,431 49-49 38d7b10864f80d0225583ef65a6be410c6231050882204398158bf821552ad41 last_trade_price 54,901 3,053,685 50-50 b0d80d34ca822194d735d571dd3f68655f931f0eeab769d8725c39365a9fa5bf market_resolved 2,401 374,245 51-51 0df11564e2be7f56848202a31cf041a466277b8713e57780e96d8338decfc18b new_market 1,137 106,339 52-52 9334440aff8592db30105dad65ea45354d1c4ba2920344ccc14bbdbf16917b99 price_change 108,938,134 1,158,572,664 53-468 cafdd13a271c391d62a2bcdd6a2054ef1e885adcf6799add494d4243e05c40f7 tick_size_change 3,164 117,129 469-469 ad6a7fdfd4dedc69bc396006191ac8de36aa5df7e6927a4af61230510321be32 EVENT MIX count share price_change 108,938,134 89.43% best_bid_ask 12,688,253 10.42% book 126,091 0.10% last_trade_price 54,901 0.05% tick_size_change 3,164 <0.01% market_resolved 2,401 <0.01% new_market 1,137 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,688,337 12,688,253 84 120 FULL book 126,091 126,091 0 6,701 FULL last_trade_price 54,901 54,901 0 1 FULL market_resolved 2,401 2,401 0 0 FULL new_market 1,137 1,137 0 0 FULL price_change 108,938,736 108,938,134 602 1,477 FULL tick_size_change 3,164 3,164 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,685,737 29,339 18ms 24ms 173ms 56.6s 0 transport_latency_assumed best_bid_ask i 12,686,105 30,552 20ms 26ms 83ms 7.8s 0 transport_latency_assumed best_bid_ask m 12,687,765 6,386,980 4ms 9ms 51ms 9.7s 0 transport_latency_assumed best_bid_ask n 12,683,994 4,661 44ms 52ms 174ms 10.1s 0 transport_latency_assumed best_bid_ask o 12,687,780 6,236,721 4ms 9ms 54ms 6.6s 0 transport_latency_assumed book h 116,951 7,575 23ms 214ms 13.7h 114.5d 0 book_staleness book i 112,282 2,558 23ms 94ms 8.4min 114.5d 0 book_staleness book m 112,548 55,311 6ms 20ms 3.2min 114.5d 0 book_staleness book n 112,113 3,969 45ms 328ms 3.5h 114.4d 0 book_staleness book o 112,054 56,678 6ms 19ms 7.7s 114.5d 0 book_staleness last_trade_price h 54,659 368 21ms 46ms 1.1s 20.2s 0 transport_latency_assumed last_trade_price i 54,671 182 23ms 64ms 871ms 7.8s 0 transport_latency_assumed last_trade_price m 54,866 26,987 6ms 15ms 375ms 9.7s 0 transport_latency_assumed last_trade_price n 53,899 238 45ms 177ms 3.7s 10.2s 0 transport_latency_assumed last_trade_price o 54,855 27,126 6ms 15ms 157ms 2.7s 0 transport_latency_assumed market_resolved h 2,318 6 20ms 79ms 42.6s 45.6s 0 transport_latency_assumed market_resolved i 2,318 215 22ms 155ms 50.1s 55.1s 0 transport_latency_assumed market_resolved m 2,318 1,070 5ms 53ms 51.1s 53.0s 0 transport_latency_assumed market_resolved n 2,318 1 46ms 201ms 44.6s 49.3s 0 transport_latency_assumed market_resolved o 2,318 1,109 5ms 14ms 48.1s 51.7s 0 transport_latency_assumed new_market h 660 401 39ms 16.9s 40.3s 1.7min 0 transport_latency_assumed new_market i 660 133 113ms 13.9s 49.6s 1.6min 0 transport_latency_assumed new_market m 660 299 94ms 22.4s 51.8s 1.7min 0 transport_latency_assumed new_market n 660 41 247ms 14.0s 45.6s 1.5min 0 transport_latency_assumed new_market o 660 263 85ms 12.9s 26.0s 1.4min 0 transport_latency_assumed price_change h 108,378,613 294,182 18ms 28ms 239ms 1.8min 0 transport_latency_assumed price_change i 108,825,508 587,752 21ms 28ms 152ms 7.8s 0 transport_latency_assumed price_change m 108,424,576 53,641,722 4ms 10ms 63ms 43.1s 0 transport_latency_assumed price_change n 108,355,263 52,424 44ms 56ms 307ms 10.2s 0 transport_latency_assumed price_change o 108,595,738 54,362,054 4ms 10ms 68ms 8.1s 0 transport_latency_assumed tick_size_change h 3,164 12 18ms 24ms 78ms 619ms 0 transport_latency_assumed tick_size_change i 3,164 not meas. 21ms 32ms 78ms 136ms 0 transport_latency_assumed tick_size_change m 3,164 1,576 4ms 8ms 28ms 82ms 0 transport_latency_assumed tick_size_change n 3,164 not meas. 44ms 56ms 127ms 456ms 0 transport_latency_assumed tick_size_change o 3,164 1,576 5ms 9ms 31ms 268ms 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/23/2026-10-09T23.parquet sha256sum 2026-10-09T23.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.