Hour audit: 2026-10-09T22
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-09T22 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 114,854,479 rows · 1,248,765,374 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 114,718,523 · o: 114,407,460 · m: 114,241,977 · n: 114,172,698 · h: 114,160,954 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 869,797 (0.76%) · o: 58,504,514 (50.94%) · m: 54,984,585 (47.87%) · n: 102,952 (0.09%) · h: 392,631 (0.34%) (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 114,854,479 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b9f93043283074c8902d568e99ded3313b6d496a443f68b3e86b0b78030264ef
no line in the corpus checksum ledger names this file
joined 114,855,691 to merged 114,854,479, minus 1,212 (minus 0.0011%)
boundary drops 1,212 · 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-10T08:39:57Z 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,160,188 148,255,731 0-46 24c70d4e77d25b0e4d594170c89e7fdb414423a7cf4ac198dfc8acf7a33b41d9 book 182,098 19,350,551 47-47 51699f2cb432a66807790f25bf3fe9d1a1f954441556e75b6b648665769fb840 last_trade_price 46,933 2,707,154 48-48 4ee3d7c2f4a0930787e7a9b9bcd53c238c5fbddfb7b87a290d3aacf0731468b1 market_resolved 4,255 664,714 49-49 40bb579e96292b5bb81ec24270308ae5f99556a7c5197b725a41b62d298be5b5 new_market 1,803 176,546 50-50 9d5d73e1df9b74fe2b6656ea1cfe011799e442efb6d3a529f088a06d797796f7 price_change 102,454,894 1,076,141,291 51-441 db7f0d9e60f714bb6b620a4eb6446f1268f858e7f49d610cd56e601324518bc6 tick_size_change 4,308 160,985 442-442 eafa657925424b928f9dcfcd6eb3a1a692ddd072a895e40ed7c03a8a146a0d96 EVENT MIX count share price_change 102,454,894 89.20% best_bid_ask 12,160,188 10.59% book 182,098 0.16% last_trade_price 46,933 0.04% tick_size_change 4,308 <0.01% market_resolved 4,255 <0.01% new_market 1,803 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,160,278 12,160,188 90 127 FULL book 182,132 182,098 34 40,541 FULL last_trade_price 46,933 46,933 0 0 FULL market_resolved 4,255 4,255 0 1 FULL new_market 1,803 1,803 0 0 FULL price_change 102,455,982 102,454,894 1,088 1,645 FULL tick_size_change 4,308 4,308 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,154,862 32,060 18ms 24ms 457ms 1.7min 0 transport_latency_assumed best_bid_ask i 12,156,136 50,385 20ms 27ms 112ms 6.3s 0 transport_latency_assumed best_bid_ask m 12,159,006 5,879,577 4ms 9ms 90ms 1.0min 0 transport_latency_assumed best_bid_ask n 12,157,780 7,923 43ms 53ms 278ms 27.2s 0 transport_latency_assumed best_bid_ask o 12,159,230 6,190,243 4ms 9ms 99ms 24.3s 0 transport_latency_assumed book h 123,415 29,315 24ms 1.4h 30.6d 114.5d 0 book_staleness book i 134,334 39,175 28ms 4.4h 32.5d 133.0d 0 book_staleness book m 102,316 53,989 6ms 99ms 1.0d 114.5d 0 book_staleness book n 103,173 8,685 47ms 1.3s 1.7d 114.5d 0 book_staleness book o 100,114 50,934 6ms 41ms 10.7h 114.5d 0 book_staleness last_trade_price h 46,564 242 20ms 52ms 1.0s 54.1s 0 transport_latency_assumed last_trade_price i 46,694 200 23ms 88ms 974ms 6.3s 0 transport_latency_assumed last_trade_price m 46,833 22,989 6ms 13ms 228ms 9.0s 0 transport_latency_assumed last_trade_price n 46,735 86 46ms 198ms 2.3s 27.1s 0 transport_latency_assumed last_trade_price o 46,810 23,416 6ms 14ms 185ms 5.0s 0 transport_latency_assumed market_resolved h 4,100 10 20ms 96ms 51.4s 54.7s 0 transport_latency_assumed market_resolved i 4,099 362 22ms 166ms 49.3s 55.6s 0 transport_latency_assumed market_resolved m 4,100 1,807 5ms 31ms 52.1s 58.8s 0 transport_latency_assumed market_resolved n 4,100 3 45ms 208ms 50.3s 57.3s 0 transport_latency_assumed market_resolved o 4,100 2,073 5ms 13ms 46.7s 54.8s 0 transport_latency_assumed new_market h 1,124 450 66ms 14.8s 21.8s 1.5min 0 transport_latency_assumed new_market i 1,124 417 52ms 13.4s 20.5s 1.8min 0 transport_latency_assumed new_market m 1,124 546 55ms 12.9s 21.4s 1.6min 0 transport_latency_assumed new_market n 1,124 167 276ms 14.9s 41.2s 1.7min 0 transport_latency_assumed new_market o 1,124 223 119ms 13.4s 34.3s 1.7min 0 transport_latency_assumed price_change h 101,826,581 330,554 18ms 27ms 629ms 1.7min 0 transport_latency_assumed price_change i 102,371,832 779,258 21ms 30ms 244ms 6.3s 0 transport_latency_assumed price_change m 101,924,290 49,023,694 5ms 10ms 118ms 1.0min 0 transport_latency_assumed price_change n 101,855,478 86,088 44ms 59ms 486ms 27.2s 0 transport_latency_assumed price_change o 102,091,774 52,235,300 5ms 10ms 124ms 25.5s 0 transport_latency_assumed tick_size_change h 4,308 not meas. 17ms 26ms 417ms 25.6s 0 transport_latency_assumed tick_size_change i 4,304 not meas. 21ms 26ms 56ms 84ms 0 transport_latency_assumed tick_size_change m 4,308 1,983 5ms 9ms 30ms 154ms 0 transport_latency_assumed tick_size_change n 4,308 not meas. 43ms 58ms 188ms 642ms 0 transport_latency_assumed tick_size_change o 4,308 2,325 4ms 8ms 26ms 72ms 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/22/2026-10-09T22.parquet sha256sum 2026-10-09T22.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.