Hour audit: 2026-10-09T21
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-09T21 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 116,098,655 rows · 1,284,257,322 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 115,952,419 · o: 115,541,881 · m: 115,397,708 · h: 115,316,192 · n: 115,292,764 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 799,241 (0.69%) · o: 55,495,199 (47.80%) · m: 59,345,954 (51.12%) · h: 393,147 (0.34%) · n: 65,114 (0.06%) (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 116,098,655 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3ab2fec850da9df108a0df331f28436d28685f5772fcf335951aa0851ffd0d82
no line in the corpus checksum ledger names this file
joined 116,099,722 to merged 116,098,655, minus 1,067 (minus 0.0009%)
boundary drops 1,067 · 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:12:14Z 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,461,464 152,237,673 0-47 feeb5b4625cd07288dbf3109fd823a46a2c3a6be3571d67368bc9e5a2ad40515 book 261,428 26,183,228 48-48 617395e61155c9320a6cae4a729ba5111c52a9a6b8e792ddf64bae47c293c1d1 last_trade_price 67,054 3,678,335 49-49 5b0833f7a3a980909be1a10f61705a49b7fa9520c9d34e23e39bb7eec312025a market_resolved 3,219 509,906 50-50 19629dc4c96822935e443e766a03572d01f96f51eff22d87d330fc8400d8828d new_market 792 81,851 51-51 da68d8c716fc09f1653204d8b7634a3ee2d79a5709e15fb7c1da3f7755d248a3 price_change 103,300,798 1,100,099,437 52-446 f46257e99c53a2a9c114d63fca1c2ea36a83d51d4a8850eb9a3cc0c6a11eadf1 tick_size_change 3,900 143,871 447-447 eed85f03fde38eb8086ad32e0b0fe1e0f0731f9a7e3d775fed054449442b21da EVENT MIX count share price_change 103,300,798 88.98% best_bid_ask 12,461,464 10.73% book 261,428 0.23% last_trade_price 67,054 0.06% tick_size_change 3,900 <0.01% market_resolved 3,219 <0.01% new_market 792 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,461,640 12,461,464 176 60 FULL book 261,490 261,428 62 59,205 FULL last_trade_price 67,055 67,054 1 0 FULL market_resolved 3,219 3,219 0 0 FULL new_market 792 792 0 0 FULL price_change 103,301,626 103,300,798 828 1,814 FULL tick_size_change 3,900 3,900 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,459,734 35,403 18ms 24ms 161ms 51.6s 0 transport_latency_assumed best_bid_ask i 12,459,690 33,971 21ms 38ms 85ms 3.0s 0 transport_latency_assumed best_bid_ask m 12,460,476 6,490,245 5ms 10ms 53ms 8.4s 0 transport_latency_assumed best_bid_ask n 12,459,504 3,939 43ms 52ms 169ms 8.3s 0 transport_latency_assumed best_bid_ask o 12,460,810 5,897,906 5ms 10ms 57ms 5.6s 0 transport_latency_assumed book h 145,810 11,718 21ms 339ms 1.7d 114.5d 0 book_staleness book i 204,157 68,187 39ms 5.7h 32.5d 133.0d 0 book_staleness book m 152,824 84,533 7ms 41.4s 2.6d 114.5d 0 book_staleness book n 152,992 17,680 47ms 50.2s 1.9d 125.2d 0 book_staleness book o 149,114 79,310 7ms 329ms 1.7d 133.0d 0 book_staleness last_trade_price h 66,822 273 19ms 50ms 572ms 47.6s 0 transport_latency_assumed last_trade_price i 66,829 131 23ms 177ms 1.6s 3.0s 0 transport_latency_assumed last_trade_price m 66,951 34,285 6ms 13ms 151ms 2.9s 0 transport_latency_assumed last_trade_price n 66,777 70 46ms 409ms 3.9s 6.0s 0 transport_latency_assumed last_trade_price o 66,970 32,295 6ms 13ms 154ms 4.1s 0 transport_latency_assumed market_resolved h 3,129 14 19ms 83ms 52.6s 55.6s 0 transport_latency_assumed market_resolved i 3,129 244 23ms 119ms 48.4s 57.0s 0 transport_latency_assumed market_resolved m 3,129 1,500 5ms 21ms 45.3s 54.0s 0 transport_latency_assumed market_resolved n 3,129 2 45ms 202ms 48.7s 56.3s 0 transport_latency_assumed market_resolved o 3,129 1,459 5ms 15ms 54.0s 57.3s 0 transport_latency_assumed new_market h 506 159 62ms 13.4s 48.4s 1.7min 0 transport_latency_assumed new_market i 506 186 45ms 10.5s 20.5s 1.5min 0 transport_latency_assumed new_market m 506 286 32ms 12.6s 40.9s 1.4min 0 transport_latency_assumed new_market n 506 47 231ms 11.5s 20.3s 1.3min 0 transport_latency_assumed new_market o 506 114 89ms 12.9s 1.1min 1.7min 0 transport_latency_assumed price_change h 102,636,291 345,576 18ms 26ms 252ms 51.6s 0 transport_latency_assumed price_change i 103,214,208 696,522 21ms 39ms 256ms 3.3s 0 transport_latency_assumed price_change m 102,709,922 52,732,990 5ms 10ms 69ms 9.8s 0 transport_latency_assumed price_change n 102,605,956 43,376 44ms 59ms 506ms 8.4s 0 transport_latency_assumed price_change o 102,857,452 49,482,334 5ms 10ms 72ms 6.0s 0 transport_latency_assumed tick_size_change h 3,900 4 18ms 23ms 101ms 299ms 0 transport_latency_assumed tick_size_change i 3,900 not meas. 21ms 33ms 63ms 300ms 0 transport_latency_assumed tick_size_change m 3,900 2,115 5ms 9ms 28ms 67ms 0 transport_latency_assumed tick_size_change n 3,900 not meas. 43ms 56ms 276ms 482ms 0 transport_latency_assumed tick_size_change o 3,900 1,781 5ms 9ms 35ms 236ms 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/21/2026-10-09T21.parquet sha256sum 2026-10-09T21.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.