Hour audit: 2026-09-25T08
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-09-25T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-25T08:00:00.000015241+00:00 · last event 2026-09-25T08:59:59.999981325+00:00
VOLUME 120,442,266 rows · 1,293,011,233 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 119,018,521 · i: 119,002,387 · g: 118,989,628 · c: 111,184,897 · h: 103,426,611 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 14,054,398 (11.67%) · i: 932,572 (0.77%) · g: 9,628 (0.01%) · c: 103,043,723 (85.55%) · h: 2,401,945 (1.99%) (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 120,442,266 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b7a6b2f0af2b00feccf15a49239540f2653168badd1475458fb604d4d8cd48d2
the corpus checksum ledger names this file with the same digest
joined 120,445,178 to merged 120,442,266, minus 2,912 (minus 0.0024%)
boundary drops 2,912 · 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-09-25T10:46:58Z as cghik
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 12,676,560 145,598,363 0-48 da09df002814659f65a6e04538f04d66d7f41c8b43d637632782a1f50689071d book 1,497,361 80,530,768 49-54 b52111797caaad22b14333df02bac4c476a7e2d23ee52dafc76dc55a3347b7e6 last_trade_price 48,061 2,741,213 55-55 dc91f704c2d9c5d2bc24ba11e74ef8959b68f4ad45c1765e3540da6b3135fc14 market_resolved 865 95,828 56-56 f52f173768a6279df2b46712d67fbf43f0eea0474e4921eedbc26a5458077d9e new_market 709 67,399 57-57 d4cc27f7a9218f5b47ccfbe31c14a95d8ce3ca4bd084c9400543d5b8657ca2a5 price_change 106,216,530 1,062,524,677 58-463 8f9819c1ee8edf9ac93302da72d35daf9f80dd2af9bd554597f923bc6650d87b tick_size_change 2,180 80,679 464-464 8cb54d3520078ab8a0b79642d4702c73386fba0270ed7265b32c8c6c87a25680 EVENT MIX count share price_change 106,216,530 88.19% best_bid_ask 12,676,560 10.53% book 1,497,361 1.24% last_trade_price 48,061 0.04% tick_size_change 2,180 <0.01% market_resolved 865 <0.01% new_market 709 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,676,838 12,676,560 278 2,353 FULL book 1,497,465 1,497,361 104 207,048 FULL last_trade_price 48,061 48,061 0 336 FULL market_resolved 865 865 0 0 FULL new_market 709 709 0 0 FULL price_change 106,219,060 106,216,530 2,530 896 FULL tick_size_change 2,180 2,180 0 79 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,769,764 11,000,954 5ms 11ms 83ms 2.1s 0 transport_latency_assumed best_bid_ask g 12,674,740 463 79ms 97ms 270ms 9.0s 0 transport_latency_assumed best_bid_ask h 10,944,845 106,760 19ms 35ms 101ms 51.2s 0 transport_latency_assumed best_bid_ask i 12,675,296 91,261 21ms 28ms 96ms 4.1s 0 transport_latency_assumed best_bid_ask k 12,675,785 1,477,122 12ms 18ms 77ms 11.3s 0 transport_latency_assumed book c 512,598 230,330 5.7min 3.6d 33.8d 118.4d 0 book_staleness book g 104,405 3,565 86ms 2.9s 3.5d 99.9d 0 book_staleness book h 1,335,496 1,246,250 12.2min 4.6d 43.6d 118.4d 0 book_staleness book i 99,757 3,266 24ms 108ms 2.2h 99.9d 0 book_staleness book k 100,647 13,950 15ms 60ms 1.0d 99.9d 0 book_staleness last_trade_price c 44,933 40,593 6ms 22ms 222ms 1.3s 0 transport_latency_assumed last_trade_price g 47,915 15 85ms 321ms 4.8s 9.1s 0 transport_latency_assumed last_trade_price h 39,622 798 20ms 53ms 252ms 17.8s 0 transport_latency_assumed last_trade_price i 47,824 517 23ms 68ms 443ms 4.1s 0 transport_latency_assumed last_trade_price k 47,907 6,138 13ms 32ms 208ms 1.4s 0 transport_latency_assumed market_resolved c 603 525 5ms 3.0min 7.3min 7.4min 0 transport_latency_assumed market_resolved g 563 not meas. 88ms 32.9s 54.5s 54.5s 0 transport_latency_assumed market_resolved h 681 203 41ms 7.2min 10.5min 11.0min 0 transport_latency_assumed market_resolved i 563 73 24ms 32.7s 55.3s 57.3s 0 transport_latency_assumed market_resolved k 563 64 14ms 58ms 49.3s 49.3s 0 transport_latency_assumed new_market c 429 224 65ms 17.7s 6.1min 6.6min 0 transport_latency_assumed new_market g 427 99 211ms 14.0s 21.7s 1.5min 0 transport_latency_assumed new_market h 468 171 139ms 5.3min 8.4min 8.4min 0 transport_latency_assumed new_market i 427 105 91ms 13.9s 20.0s 22.9s 0 transport_latency_assumed new_market k 427 110 92ms 15.2s 17.6s 1.7min 0 transport_latency_assumed price_change c 98,854,518 91,769,112 5ms 13ms 97ms 4.1s 0 transport_latency_assumed price_change g 106,159,398 5,486 79ms 106ms 537ms 9.1s 0 transport_latency_assumed price_change h 91,103,515 1,047,752 19ms 38ms 121ms 51.7s 0 transport_latency_assumed price_change i 106,176,340 837,350 22ms 31ms 138ms 4.4s 0 transport_latency_assumed price_change k 106,191,012 12,556,830 12ms 20ms 93ms 11.3s 0 transport_latency_assumed tick_size_change c 2,052 1,985 5ms 7ms 33ms 80ms 0 transport_latency_assumed tick_size_change g 2,180 not meas. 78ms 94ms 143ms 290ms 0 transport_latency_assumed tick_size_change h 1,984 11 19ms 32ms 83ms 256ms 0 transport_latency_assumed tick_size_change i 2,180 not meas. 21ms 25ms 52ms 154ms 0 transport_latency_assumed tick_size_change k 2,180 184 12ms 16ms 51ms 67ms 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-09-25/08/2026-09-25T08.parquet sha256sum 2026-09-25T08.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.