Hour audit: 2026-10-10T01
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-10T01 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 141,842,783 rows · 1,661,590,081 bytes (1.55 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 141,011,814 · m: 140,902,329 · i: 140,747,372 · h: 140,715,899 · n: 134,384,057 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 72,652,996 (51.22%) · m: 67,433,960 (47.54%) · i: 377,464 (0.27%) · h: 721,914 (0.51%) · n: 656,449 (0.46%) (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 141,842,783 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2fb8573b89cf963325df4d53d69412a240145619178befb5a24321519d54e216
no line in the corpus checksum ledger names this file
joined 141,857,179 to merged 141,842,783, minus 14,396 (minus 0.0101%)
boundary drops 14,396 · 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-10T10:14:40Z 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,870,723 158,830,140 0-49 0a9ef60389d94b4eb2fdc83330356fd608d2cac90afcb33f1ad5ae851f103e42 book 1,091,380 86,378,217 50-54 86ceac416a3669a2956ff5cd0d41979c35656eb275f2f08f07078f58bdf8d9b1 last_trade_price 47,353 2,751,647 55-55 19e3b391ed75718f66f0ef011136fc45c7e262e01bc6ee7e0c88f48f17d2fb71 market_resolved 789 114,456 56-56 ffb7170b22cd7279652630ad351e4ee5888e0a6e503c6530ffd074a4d3bd3add new_market 498 52,824 57-57 7246fcf0ffa57811524252851d0644a0710399dedf6109cbecdee03bc1b01150 price_change 127,828,252 1,411,708,362 58-545 3e8d4002d6d6b6bbae839e7f7c4e27c3aee3e67a0428910ae1f0139d8cbca3bc tick_size_change 3,788 138,593 546-546 d10ecbcf1649d79b2f7a06bd97325eb5452f9df308a22c6da27ae150eda93256 EVENT MIX count share price_change 127,828,252 90.12% best_bid_ask 12,870,723 9.07% book 1,091,380 0.77% last_trade_price 47,353 0.03% tick_size_change 3,788 <0.01% market_resolved 789 <0.01% new_market 498 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,871,439 12,870,723 716 631 FULL book 1,095,960 1,091,380 4,580 271,249 FULL last_trade_price 47,353 47,353 0 112 FULL market_resolved 789 789 0 4 FULL new_market 498 498 0 0 FULL price_change 127,837,352 127,828,252 9,100 1,097 FULL tick_size_change 3,788 3,788 0 12 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,868,264 50,066 18ms 26ms 103ms 55.8s 0 transport_latency_assumed best_bid_ask i 12,869,838 30,699 21ms 32ms 78ms 1.4s 0 transport_latency_assumed best_bid_ask m 12,869,687 6,156,955 5ms 11ms 60ms 4.3s 0 transport_latency_assumed best_bid_ask n 12,195,456 2,608 44ms 56ms 130ms 8.1s 0 transport_latency_assumed best_bid_ask o 12,869,481 6,630,395 4ms 11ms 60ms 3.5s 0 transport_latency_assumed book h 315,193 117,576 2.7min 1.2d 48.5d 133.1d 0 book_staleness book i 106,345 6,224 23ms 8.4s 1.9d 114.6d 0 book_staleness book m 304,979 168,351 2.2min 1.2d 48.5d 133.1d 0 book_staleness book n 832,167 624,397 13.7min 1.9d 48.5d 133.1d 0 book_staleness book o 313,528 174,832 2.5min 1.2d 48.5d 133.1d 0 book_staleness last_trade_price h 47,324 393 19ms 37ms 307ms 28.0s 0 transport_latency_assumed last_trade_price i 47,200 219 22ms 39ms 327ms 1.5s 0 transport_latency_assumed last_trade_price m 47,320 22,250 6ms 15ms 144ms 1.5s 0 transport_latency_assumed last_trade_price n 45,111 35 46ms 110ms 908ms 4.2s 0 transport_latency_assumed last_trade_price o 47,284 24,456 5ms 15ms 117ms 1.5s 0 transport_latency_assumed market_resolved h 703 1 20ms 65ms 32.6s 32.6s 0 transport_latency_assumed market_resolved i 703 41 22ms 78ms 22.1s 22.1s 0 transport_latency_assumed market_resolved m 703 341 5ms 13ms 22.5s 22.6s 0 transport_latency_assumed market_resolved n 699 86 47ms 3.0min 6.0min 6.0min 0 transport_latency_assumed market_resolved o 703 320 5ms 17ms 38.3s 38.4s 0 transport_latency_assumed new_market h 330 52 87ms 9.8s 14.5s 1.6min 0 transport_latency_assumed new_market i 330 95 45ms 8.9s 1.0min 1.6min 0 transport_latency_assumed new_market m 330 172 39ms 9.8s 12.4s 1.4min 0 transport_latency_assumed new_market n 342 47 117ms 10.0s 6.4min 6.4min 0 transport_latency_assumed new_market o 330 132 48ms 9.2s 1.0min 1.7min 0 transport_latency_assumed price_change h 127,480,297 553,814 18ms 27ms 136ms 56.0s 0 transport_latency_assumed price_change i 127,719,168 340,182 21ms 31ms 100ms 1.8s 0 transport_latency_assumed price_change m 127,675,522 61,084,010 5ms 11ms 69ms 4.7s 0 transport_latency_assumed price_change n 121,306,542 29,276 44ms 59ms 193ms 8.2s 0 transport_latency_assumed price_change o 127,776,700 65,820,970 5ms 11ms 67ms 3.5s 0 transport_latency_assumed tick_size_change h 3,788 12 17ms 24ms 82ms 164ms 0 transport_latency_assumed tick_size_change i 3,788 4 21ms 28ms 51ms 129ms 0 transport_latency_assumed tick_size_change m 3,788 1,881 4ms 10ms 34ms 165ms 0 transport_latency_assumed tick_size_change n 3,740 not meas. 44ms 51ms 98ms 344ms 0 transport_latency_assumed tick_size_change o 3,788 1,891 4ms 10ms 47ms 226ms 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-10/01/2026-10-10T01.parquet sha256sum 2026-10-10T01.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.