Hour audit: 2026-10-03T00
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-03T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T00:00:00.000006196+00:00 · last event 2026-10-03T00:59:59.999955051+00:00
VOLUME 115,277,684 rows · 1,216,419,350 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 115,171,203 · h: 115,167,195 · k: 115,161,220 · m: 115,140,615 · g: 115,085,535 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 488,702 (0.42%) · h: 1,205,619 (1.05%) · k: 4,497,673 (3.90%) · m: 109,057,380 (94.60%) · g: 28,310 (0.02%) (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,277,684 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3c3097a967eb08e612d5a8a1ce17d2cb9954a745f9d18c920ef590446b9442c6
the corpus checksum ledger names this file with the same digest
joined 115,279,839 to merged 115,277,684, minus 2,155 (minus 0.0019%)
boundary drops 2,155 · 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-03T02:46:40Z as ghikm
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 8/8 pass
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
PASS the checksum ledger names 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 10,815,276 125,616,933 0-41 f678267bd4bd9a501fe2b02c1eedf48b481e9c41981a054fd21274d2b02a6448 book 189,445 19,447,098 42-42 ad35ce9009c0c158296d7af83c9704a7d5ffdaccda131f819e2be486ff310a97 last_trade_price 48,570 2,785,176 43-43 a8719c53adba79ba323156fe713a4975a0acdaa6c82f7365614825f1df834280 market_resolved 1,411 210,195 44-44 0f02deda58ca83908e48cc26ffcdcd5acc5ead1164c693a78ea06b736bae73db new_market 370 39,948 45-45 ce9b454eb36e646ee63d321d673af13c1bf3131d9407839acbdc00bfb4a2f954 price_change 104,219,060 1,066,875,437 46-443 1b0e8968ef4eee2ac94644d7ed052a1cfba2a0a3ea7e74eb6209ec2242039ada tick_size_change 3,552 129,767 444-444 7799e274f53fbdb10b09e301e8ae0353ea4f04c4294cdc19d1cc0527fbe2ad42 EVENT MIX count share price_change 104,219,060 90.41% best_bid_ask 10,815,276 9.38% book 189,445 0.16% last_trade_price 48,570 0.04% tick_size_change 3,552 <0.01% market_resolved 1,411 <0.01% new_market 370 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,815,498 10,815,276 222 56 FULL book 189,567 189,445 122 42,232 FULL last_trade_price 48,571 48,570 1 0 FULL market_resolved 1,411 1,411 0 0 FULL new_market 370 370 0 0 FULL price_change 104,220,870 104,219,060 1,810 177 FULL tick_size_change 3,552 3,552 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,813,830 600 79ms 96ms 238ms 11.3s 0 transport_latency_assumed best_bid_ask h 10,814,523 97,839 17ms 23ms 81ms 7.7s 0 transport_latency_assumed best_bid_ask i 10,814,550 34,962 21ms 27ms 79ms 4.0s 0 transport_latency_assumed best_bid_ask k 10,814,742 401,382 13ms 22ms 76ms 5.8s 0 transport_latency_assumed best_bid_ask m 10,813,709 10,280,493 5ms 10ms 55ms 3.1s 0 transport_latency_assumed book g 114,213 15,849 88ms 6.6min 7.0d 107.6d 0 book_staleness book h 111,891 15,302 22ms 2.8min 7.2d 126.1d 0 book_staleness book i 114,489 16,949 23ms 7.1min 13.4d 107.6d 0 book_staleness book k 115,850 22,250 17ms 13.3min 12.7d 107.6d 0 book_staleness book m 127,284 119,095 8ms 2.6h 23.6d 126.1d 0 book_staleness last_trade_price g 48,443 5 83ms 200ms 3.3s 5.5s 0 transport_latency_assumed last_trade_price h 48,394 791 19ms 32ms 291ms 7.7s 0 transport_latency_assumed last_trade_price i 48,459 348 22ms 38ms 259ms 3.4s 0 transport_latency_assumed last_trade_price k 48,515 2,943 15ms 30ms 189ms 1.4s 0 transport_latency_assumed last_trade_price m 48,361 44,483 6ms 16ms 136ms 1.4s 0 transport_latency_assumed market_resolved g 1,314 53 80ms 233ms 46.8s 47.0s 0 transport_latency_assumed market_resolved h 1,314 12 19ms 21.9s 50.6s 54.7s 0 transport_latency_assumed market_resolved i 1,314 127 22ms 24.7s 56.1s 58.4s 0 transport_latency_assumed market_resolved k 1,314 76 14ms 18.9s 46.8s 50.4s 0 transport_latency_assumed market_resolved m 1,314 1,143 5ms 23.6s 53.2s 58.5s 0 transport_latency_assumed new_market g 249 15 107ms 12.4s 46.9s 1.3min 0 transport_latency_assumed new_market h 249 40 40ms 12.2s 51.5s 1.7min 0 transport_latency_assumed new_market i 249 76 48ms 16.1s 1.5min 1.7min 0 transport_latency_assumed new_market k 249 47 44ms 8.8s 1.2min 1.5min 0 transport_latency_assumed new_market m 249 192 21ms 8.0s 1.4min 1.7min 0 transport_latency_assumed price_change g 104,103,938 11,788 79ms 101ms 506ms 11.7s 0 transport_latency_assumed price_change h 104,187,272 1,091,604 18ms 25ms 163ms 7.7s 0 transport_latency_assumed price_change i 104,188,590 436,236 21ms 29ms 196ms 4.1s 0 transport_latency_assumed price_change k 104,176,998 4,070,900 13ms 24ms 125ms 7.1s 0 transport_latency_assumed price_change m 104,146,146 98,608,532 5ms 11ms 80ms 3.2s 0 transport_latency_assumed tick_size_change g 3,548 not meas. 79ms 94ms 310ms 398ms 0 transport_latency_assumed tick_size_change h 3,552 31 18ms 23ms 55ms 173ms 0 transport_latency_assumed tick_size_change i 3,552 4 21ms 26ms 64ms 146ms 0 transport_latency_assumed tick_size_change k 3,552 75 13ms 20ms 64ms 239ms 0 transport_latency_assumed tick_size_change m 3,552 3,442 4ms 8ms 40ms 130ms 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-03/00/2026-10-03T00.parquet sha256sum 2026-10-03T00.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.