Hour audit: 2026-09-27T07
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-27T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T07:00:00.000112051+00:00 · last event 2026-09-27T07:59:59.999987265+00:00
VOLUME 90,606,338 rows · 898,222,950 bytes (856.61 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 90,567,275 · c: 90,559,091 · h: 90,552,872 · i: 90,546,228 · g: 90,545,585 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,675,869 (2.95%) · c: 86,648,735 (95.63%) · h: 537,400 (0.59%) · i: 728,637 (0.80%) · g: 15,697 (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 90,606,338 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b434e58e64c5d0b33c3719021bb200c75b21d7178eb80ce05415a5ceee5ffebb
the corpus checksum ledger names this file with the same digest
joined 90,607,941 to merged 90,606,338, minus 1,603 (minus 0.0018%)
boundary drops 1,603 · 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:48:12Z 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,790,366 107,655,880 0-37 1fce5396c742843000c6ad1fed7e35ff2aa39e1e5f7328e833515afae36bd256 book 109,562 10,526,537 38-38 df1d7f5ca06fdd323d98455101ec78a9111b1acf9175c82726279602f6116afe last_trade_price 43,555 2,519,005 39-39 2e15a0eb3f2141c8d3a064724fd341c9a79bdcf4008301ee1e75358eefbe4701 market_resolved 1,596 230,651 40-40 0525630476f5cd8f2f17820aac14be3b22a74a10f803c8c57cb1249cae78812d new_market 2,331 224,991 41-41 cdae8be6ba190cc71252f7d1570e6a2a91658197801edd28e124a813d2e175ff price_change 80,656,796 775,950,825 42-349 0387e335a1433cd03816f9b777bcf297f9b5e2a757a93f725d762070c7ce4888 tick_size_change 2,132 79,654 350-350 89a2482218e148f054f828b7836e1aafd72114a55cd27a072dc2f10b4e65d372 EVENT MIX count share price_change 80,656,796 89.02% best_bid_ask 9,790,366 10.81% book 109,562 0.12% last_trade_price 43,555 0.05% new_market 2,331 <0.01% tick_size_change 2,132 <0.01% market_resolved 1,596 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,790,579 9,790,366 213 281 FULL book 109,562 109,562 0 8,464 FULL last_trade_price 43,556 43,555 1 0 FULL market_resolved 1,599 1,596 3 3 FULL new_market 2,331 2,331 0 0 FULL price_change 80,658,182 80,656,796 1,386 103 FULL tick_size_change 2,132 2,132 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,788,847 9,388,380 4ms 7ms 118ms 9.0s 0 transport_latency_assumed best_bid_ask g 9,787,357 730 77ms 92ms 467ms 22.0s 0 transport_latency_assumed best_bid_ask h 9,788,219 53,183 18ms 21ms 279ms 52.2s 0 transport_latency_assumed best_bid_ask i 9,788,420 76,548 21ms 24ms 96ms 7.9s 0 transport_latency_assumed best_bid_ask k 9,788,194 271,525 12ms 15ms 139ms 21.9s 0 transport_latency_assumed book c 94,336 87,328 6ms 61ms 3.7h 101.9d 0 book_staleness book g 98,612 8,889 82ms 3.8s 5.3d 101.9d 0 book_staleness book h 91,024 2,688 21ms 56ms 2.0min 101.8d 0 book_staleness book i 91,006 3,483 23ms 57ms 13.5s 101.8d 0 book_staleness book k 92,785 7,174 15ms 54ms 3.2h 102.3d 0 book_staleness last_trade_price c 43,471 40,898 5ms 11ms 257ms 4.3s 0 transport_latency_assumed last_trade_price g 43,427 6 80ms 190ms 2.7s 22.0s 0 transport_latency_assumed last_trade_price h 43,437 351 19ms 31ms 400ms 43.6s 0 transport_latency_assumed last_trade_price i 43,538 499 22ms 34ms 247ms 6.1s 0 transport_latency_assumed last_trade_price k 43,432 1,801 13ms 21ms 254ms 11.0s 0 transport_latency_assumed market_resolved c 1,452 1,245 5ms 25.2s 44.8s 58.8s 0 transport_latency_assumed market_resolved g 1,452 76 78ms 227ms 45.4s 48.2s 0 transport_latency_assumed market_resolved h 1,449 8 19ms 23.2s 50.3s 50.4s 0 transport_latency_assumed market_resolved i 1,449 3 22ms 23.8s 51.0s 51.1s 0 transport_latency_assumed market_resolved k 1,449 264 13ms 21.3s 48.8s 48.9s 0 transport_latency_assumed new_market c 1,461 692 111ms 18.7s 43.9s 1.7min 0 transport_latency_assumed new_market g 1,461 150 328ms 23.7s 58.7s 1.7min 0 transport_latency_assumed new_market h 1,461 438 181ms 21.7s 55.5s 1.5min 0 transport_latency_assumed new_market i 1,461 644 139ms 24.1s 44.0s 1.1min 0 transport_latency_assumed new_market k 1,461 407 186ms 16.2s 42.8s 1.3min 0 transport_latency_assumed price_change c 80,627,392 77,128,230 4ms 8ms 126ms 9.1s 0 transport_latency_assumed price_change g 80,611,144 5,846 77ms 95ms 660ms 22.0s 0 transport_latency_assumed price_change h 80,625,150 480,722 18ms 22ms 287ms 52.2s 0 transport_latency_assumed price_change i 80,618,222 647,420 21ms 25ms 143ms 7.9s 0 transport_latency_assumed price_change k 80,637,822 2,394,578 12ms 16ms 144ms 21.9s 0 transport_latency_assumed tick_size_change c 2,132 1,962 4ms 11ms 128ms 215ms 0 transport_latency_assumed tick_size_change g 2,132 not meas. 78ms 193ms 608ms 891ms 0 transport_latency_assumed tick_size_change h 2,132 10 18ms 25ms 573ms 5.6s 0 transport_latency_assumed tick_size_change i 2,132 40 21ms 25ms 95ms 159ms 0 transport_latency_assumed tick_size_change k 2,132 120 12ms 16ms 162ms 862ms 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/07/2026-09-27T07.parquet sha256sum 2026-09-27T07.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.