Hour audit: 2026-10-09T03
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-09T03:00:00.000048464+00:00 · last event 2026-10-09T03:59:59.999665027+00:00
VOLUME 115,110,187 rows · 1,287,757,118 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured h: 115,004,640 · m: 114,982,323 · n: 114,979,653 · o: 114,978,547 · i: 114,882,516 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,101,304 (0.96%) · m: 58,388,482 (50.72%) · n: 75,090 (0.07%) · o: 54,915,913 (47.71%) · i: 629,398 (0.55%) (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 115,110,187 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a322fa503ba63cbe29d8f38be8dbadf408537da0cdb9b757e2d340a612144a8d
no line in the corpus checksum ledger names this file
joined 115,111,251 to merged 115,110,187, minus 1,064 (minus 0.0009%)
boundary drops 1,064 · 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-09T22:25:50Z 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 7/8 pass, 1 finding
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
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 12,253,254 151,572,698 0-46 4234bc64ef1a3b42e69163831d54cb92389f78a69632ecd0d69b28addfd4b4ce book 145,098 16,374,078 47-47 a11202f3b2a88709eec9800381ae8db2adb54bef8e3cd91bebfec0d785b46b8d last_trade_price 46,705 2,673,612 48-48 0dbfcd798270fd9470e6a0aa63dcdd1a97412a1764141042c17818ea2eb53703 market_resolved 1,649 245,846 49-49 51d9c81521bd63aca0324a7f26fe6048316d10d4b9e826dca74cd5b3e9e9f86f new_market 423 46,771 50-50 a62cd200c022ad829ec2ff2f2124bb3dd2e35e7056e47e19b91cb6bc4f1127d7 price_change 102,658,214 1,115,354,965 51-442 725d17e648c8e62ad0daa94f384101d24fc254a6167ec7927e25a983ce7cf9e3 tick_size_change 4,844 177,731 443-443 e8250e1b723f04edea21c662ce0e7124207b18e3327da4dbba522fa31d5ebf7c EVENT MIX count share price_change 102,658,214 89.18% best_bid_ask 12,253,254 10.64% book 145,098 0.13% last_trade_price 46,705 0.04% tick_size_change 4,844 <0.01% market_resolved 1,649 <0.01% new_market 423 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,253,392 12,253,254 138 62 FULL book 145,098 145,098 0 20,203 FULL last_trade_price 46,705 46,705 0 0 FULL market_resolved 1,649 1,649 0 0 FULL new_market 423 423 0 0 FULL price_change 102,659,140 102,658,214 926 157 FULL tick_size_change 4,844 4,844 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,251,986 97,203 18ms 29ms 141ms 32.6s 0 transport_latency_assumed best_bid_ask i 12,247,782 54,046 21ms 31ms 129ms 4.9s 0 transport_latency_assumed best_bid_ask m 12,251,809 6,303,124 4ms 14ms 96ms 4.6s 0 transport_latency_assumed best_bid_ask n 12,251,911 4,241 44ms 60ms 183ms 6.4s 0 transport_latency_assumed best_bid_ask o 12,251,764 5,794,640 5ms 14ms 96ms 4.6s 0 transport_latency_assumed book h 100,625 7,939 22ms 180ms 23.2h 113.7d 0 book_staleness book i 108,499 15,719 24ms 2.9min 2.1d 113.7d 0 book_staleness book m 102,160 52,588 7ms 122ms 23.3h 113.7d 0 book_staleness book n 105,705 12,149 47ms 25.6s 1.1d 132.2d 0 book_staleness book o 102,510 56,703 7ms 146ms 23.6h 132.2d 0 book_staleness last_trade_price h 46,477 609 20ms 55ms 441ms 13.3s 0 transport_latency_assumed last_trade_price i 46,203 248 23ms 97ms 769ms 4.8s 0 transport_latency_assumed last_trade_price m 46,506 22,020 6ms 25ms 161ms 1.3s 0 transport_latency_assumed last_trade_price n 46,577 59 46ms 177ms 1.6s 6.5s 0 transport_latency_assumed last_trade_price o 46,433 23,769 6ms 22ms 161ms 1.4s 0 transport_latency_assumed market_resolved h 1,518 99 19ms 30.7s 53.8s 1.0min 0 transport_latency_assumed market_resolved i 1,518 92 23ms 36.2s 52.4s 52.5s 0 transport_latency_assumed market_resolved m 1,518 822 5ms 36.2s 52.4s 52.5s 0 transport_latency_assumed market_resolved n 1,518 17 45ms 26.1s 55.1s 55.7s 0 transport_latency_assumed market_resolved o 1,518 619 5ms 33.2s 55.1s 55.1s 0 transport_latency_assumed new_market h 292 52 50ms 8.6s 20.7s 1.7min 0 transport_latency_assumed new_market i 292 69 45ms 8.6s 11.6s 1.6min 0 transport_latency_assumed new_market m 292 139 39ms 9.1s 20.6s 1.8min 0 transport_latency_assumed new_market n 292 22 88ms 8.6s 19.1s 1.8min 0 transport_latency_assumed new_market o 292 141 37ms 9.5s 19.2s 1.6min 0 transport_latency_assumed price_change h 102,598,898 995,378 18ms 34ms 323ms 32.6s 0 transport_latency_assumed price_change i 102,473,378 559,216 21ms 37ms 400ms 4.9s 0 transport_latency_assumed price_change m 102,575,194 52,007,318 5ms 17ms 152ms 4.8s 0 transport_latency_assumed price_change n 102,568,806 58,602 44ms 69ms 687ms 6.6s 0 transport_latency_assumed price_change o 102,571,186 49,037,700 5ms 17ms 150ms 5.0s 0 transport_latency_assumed tick_size_change h 4,844 24 18ms 26ms 55ms 1.8s 0 transport_latency_assumed tick_size_change i 4,844 8 21ms 29ms 59ms 258ms 0 transport_latency_assumed tick_size_change m 4,844 2,471 4ms 12ms 45ms 130ms 0 transport_latency_assumed tick_size_change n 4,844 not meas. 44ms 59ms 147ms 234ms 0 transport_latency_assumed tick_size_change o 4,844 2,341 5ms 12ms 37ms 142ms 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/03/2026-10-09T03.parquet sha256sum 2026-10-09T03.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.