Hour audit: 2026-09-27T05
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-27T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T05:00:00.000009870+00:00 · last event 2026-09-27T05:59:59.999645334+00:00
VOLUME 78,050,555 rows · 800,228,038 bytes (763.16 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 77,978,750 · c: 77,973,510 · h: 77,969,168 · i: 77,944,335 · g: 77,884,696 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,037,203 (2.61%) · c: 74,590,367 (95.57%) · h: 560,380 (0.72%) · i: 837,877 (1.07%) · g: 24,728 (0.03%) (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 78,050,555 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 510276f8e74e17258471ad0423bb4189fccf8a600845820136599e388b689a87
the corpus checksum ledger names this file with the same digest
joined 78,052,201 to merged 78,050,555, minus 1,646 (minus 0.0021%)
boundary drops 1,646 · 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-27T14:07:45Z 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 9,962,252 110,377,330 0-38 74923a0c16fa06fb83c543066179d6d18600802a466361bed5740078d88be25b book 133,308 12,904,726 39-39 bfa9dd7639280a63db345a9346bf4584c3156e21ef32089b11b83aed3bdbfdbd last_trade_price 35,351 2,076,066 40-40 e32287a3bfb670cf63d93aace0cf221e3b19a197c94f7db23ca5395cd8e2d845 market_resolved 2,471 369,194 41-41 0fabf1ed4c1171f4f26eee58957f7c0ed13a65dde29cccdb56173369ef864ab3 new_market 3,517 351,071 42-42 2428c749736ba1d6f046fce5e8a52d69ce2b2464aa05260022eb397bc2b256e9 price_change 67,911,292 673,165,794 43-302 b22dc478a2fc9d70b82eefd943223198ceda8b5329f2809d6936e92cbe924869 tick_size_change 2,364 87,673 303-303 46d718febfaf402ccb5bc5bbbcb5f28c5d8f52dc821025aae20a765b63f29dac EVENT MIX count share price_change 67,911,292 87.01% best_bid_ask 9,962,252 12.76% book 133,308 0.17% last_trade_price 35,351 0.05% new_market 3,517 <0.01% market_resolved 2,471 <0.01% tick_size_change 2,364 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,962,490 9,962,252 238 190 FULL book 133,308 133,308 0 26,788 FULL last_trade_price 35,353 35,351 2 0 FULL market_resolved 2,471 2,471 0 33 FULL new_market 3,517 3,517 0 0 FULL price_change 67,912,698 67,911,292 1,406 142 FULL tick_size_change 2,364 2,364 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,960,206 9,562,109 4ms 7ms 142ms 9.1s 0 transport_latency_assumed best_bid_ask g 9,956,744 847 78ms 96ms 534ms 29.3s 0 transport_latency_assumed best_bid_ask h 9,958,628 62,853 18ms 22ms 406ms 59.6s 0 transport_latency_assumed best_bid_ask i 9,958,954 102,312 22ms 25ms 120ms 4.1s 0 transport_latency_assumed best_bid_ask k 9,958,908 234,131 12ms 15ms 185ms 16.5s 0 transport_latency_assumed book c 80,718 74,685 6ms 562ms 3.0h 101.8d 0 book_staleness book g 91,468 17,294 86ms 1.2h 19.8d 120.3d 0 book_staleness book h 88,669 14,222 22ms 13.5min 17.9d 101.8d 0 book_staleness book i 82,357 9,376 24ms 2.7s 4.5d 101.8d 0 book_staleness book k 90,110 17,731 15ms 39.0min 17.9d 120.3d 0 book_staleness last_trade_price c 35,328 33,561 5ms 9ms 192ms 1.5s 0 transport_latency_assumed last_trade_price g 35,005 2 80ms 215ms 7.3s 29.3s 0 transport_latency_assumed last_trade_price h 35,285 331 19ms 30ms 489ms 58.4s 0 transport_latency_assumed last_trade_price i 35,246 322 23ms 34ms 274ms 2.9s 0 transport_latency_assumed last_trade_price k 35,296 1,135 13ms 19ms 218ms 13.0s 0 transport_latency_assumed market_resolved c 2,279 1,894 5ms 25.0s 55.1s 58.4s 0 transport_latency_assumed market_resolved g 2,246 97 79ms 399ms 53.6s 53.7s 0 transport_latency_assumed market_resolved h 2,279 118 19ms 25.0s 53.2s 56.5s 0 transport_latency_assumed market_resolved i 2,279 42 23ms 24.8s 53.9s 58.4s 0 transport_latency_assumed market_resolved k 2,279 320 13ms 25.2s 52.9s 56.3s 0 transport_latency_assumed new_market c 2,259 1,356 79ms 31.6s 2.0min 2.3min 0 transport_latency_assumed new_market g 2,259 354 302ms 30.5s 1.9min 2.5min 0 transport_latency_assumed new_market h 2,259 414 164ms 32.3s 2.0min 2.4min 0 transport_latency_assumed new_market i 2,259 874 107ms 34.5s 2.0min 2.5min 0 transport_latency_assumed new_market k 2,259 519 170ms 30.3s 2.0min 2.4min 0 transport_latency_assumed price_change c 67,890,356 64,914,578 4ms 7ms 179ms 9.1s 0 transport_latency_assumed price_change g 67,794,610 6,134 78ms 106ms 1.1s 29.6s 0 transport_latency_assumed price_change h 67,879,684 482,410 18ms 24ms 487ms 59.6s 0 transport_latency_assumed price_change i 67,860,876 724,882 22ms 26ms 205ms 4.2s 0 transport_latency_assumed price_change k 67,887,534 1,783,288 12ms 16ms 220ms 16.5s 0 transport_latency_assumed tick_size_change c 2,364 2,184 5ms 11ms 249ms 399ms 0 transport_latency_assumed tick_size_change g 2,364 not meas. 78ms 101ms 1.0s 1.4s 0 transport_latency_assumed tick_size_change h 2,364 32 18ms 28ms 748ms 2.9s 0 transport_latency_assumed tick_size_change i 2,364 69 22ms 37ms 254ms 277ms 0 transport_latency_assumed tick_size_change k 2,364 79 12ms 24ms 439ms 812ms 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-27/05/2026-09-27T05.parquet sha256sum 2026-09-27T05.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.