Hour audit: 2026-09-23T21
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-23T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T21:00:00.000009004+00:00 · last event 2026-09-23T21:59:59.999959992+00:00
VOLUME 113,080,904 rows · 1,216,432,893 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 111,207,779 · g: 110,839,437 · h: 110,306,828 · k: 107,099,862 · c: 93,132,259 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,150,393 (1.02%) · g: 35,368 (0.03%) · h: 2,941,542 (2.60%) · k: 22,275,980 (19.70%) · c: 86,677,621 (76.65%) (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 113,080,904 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1f426cca7c973834bfbb308112c50d7b7a999ecd9bec80e008707b3269750947
the corpus checksum ledger names this file with the same digest
joined 113,082,787 to merged 113,080,904, minus 1,883 (minus 0.0017%)
boundary drops 1,883 · 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-24T05:38:03Z 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 10,956,348 128,324,349 0-41 3fd6774e18e84f4a88723710d8bbdc0e84f3915d595285e61f062c585299f201 book 1,907,954 83,730,857 42-49 ecd6d0c24b5abacb03d92ab623fa159f57121e4232a3bd4b789fe81ecd77363a last_trade_price 51,213 2,921,684 50-50 4f7039988e6cd6675308e8a41519010b52a11a58313cab4f8da4712ef9a36d3a market_resolved 884 110,329 51-51 888e54b821cc55a6e315f1b0cc681d07a934d456ae06c0164c2ef4bd0165ffc1 new_market 1,171 115,569 52-52 91ff3d51166a4f449eb280bd30b4234adab4e7d4fb1080d670592a5028a89bd7 price_change 100,160,898 999,849,024 53-435 630baf4d8f7b22014b7798bb7f3ef92c62f9cf268b62df07ca9274ed146cf3be tick_size_change 2,436 91,116 436-436 00b3db6976769e740b0ac2f1242dfea522073746f861fabd699650a3fc8686dd EVENT MIX count share price_change 100,160,898 88.57% best_bid_ask 10,956,348 9.69% book 1,907,954 1.69% last_trade_price 51,213 0.05% tick_size_change 2,436 <0.01% new_market 1,171 <0.01% market_resolved 884 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,956,532 10,956,348 184 2,842 FULL book 1,907,980 1,907,954 26 196,380 FULL last_trade_price 51,214 51,213 1 351 FULL market_resolved 884 884 0 11 FULL new_market 1,171 1,171 0 3 FULL price_change 100,162,570 100,160,898 1,672 1,103 FULL tick_size_change 2,436 2,436 0 95 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,055,333 8,454,699 5ms 11ms 91ms 2.7s 0 transport_latency_assumed best_bid_ask g 10,947,056 1,317 80ms 105ms 427ms 26.7s 0 transport_latency_assumed best_bid_ask h 10,912,908 294,191 18ms 29ms 252ms 9.8s 0 transport_latency_assumed best_bid_ask i 10,953,983 103,092 21ms 29ms 124ms 8.6s 0 transport_latency_assumed best_bid_ask k 10,454,423 2,103,049 12ms 18ms 79ms 3.3s 0 transport_latency_assumed book c 1,753,719 1,695,705 8.5min 4.3d 43.1d 117.0d 0 book_staleness book g 106,651 4,207 93ms 7.8s 2.0d 98.4d 0 book_staleness book h 118,966 20,397 28ms 2.2h 23.9h 2.9d 0 book_staleness book i 113,148 7,249 25ms 2.2s 3.4d 117.0d 0 book_staleness book k 542,873 180,396 4.1min 2.3d 38.1d 117.0d 0 book_staleness last_trade_price c 42,238 38,585 6ms 24ms 222ms 1.3s 0 transport_latency_assumed last_trade_price g 49,017 172 92ms 2.7s 13.3s 26.4s 0 transport_latency_assumed last_trade_price h 47,815 941 21ms 375ms 1.8s 9.6s 0 transport_latency_assumed last_trade_price i 50,763 721 25ms 355ms 1.9s 4.0s 0 transport_latency_assumed last_trade_price k 49,060 10,794 13ms 48ms 317ms 1.1s 0 transport_latency_assumed market_resolved c 774 661 7ms 8.7min 14.6min 15.6min 0 transport_latency_assumed market_resolved g 659 2 90ms 9.3s 56.3s 56.3s 0 transport_latency_assumed market_resolved h 659 26 20ms 4.7s 50.1s 50.1s 0 transport_latency_assumed market_resolved i 659 69 23ms 5.2s 49.6s 49.6s 0 transport_latency_assumed market_resolved k 648 126 16ms 51.0s 4.5min 4.5min 0 transport_latency_assumed new_market c 879 392 97ms 6.0min 12.9min 447.0d 0 transport_latency_assumed new_market g 728 66 210ms 17.9s 2.0min 447.0d 0 transport_latency_assumed new_market h 728 217 68ms 19.2s 2.0min 447.0d 0 transport_latency_assumed new_market i 728 132 81ms 14.2s 1.8min 447.0d 0 transport_latency_assumed new_market k 725 364 54ms 26.3s 3.9min 447.0d 0 transport_latency_assumed price_change c 82,277,204 76,485,568 5ms 13ms 110ms 3.1s 0 transport_latency_assumed price_change g 99,732,894 29,604 81ms 138ms 3.4s 27.0s 0 transport_latency_assumed price_change h 99,223,316 2,625,742 18ms 38ms 707ms 9.8s 0 transport_latency_assumed price_change i 100,086,062 1,039,114 21ms 36ms 329ms 8.7s 0 transport_latency_assumed price_change k 96,049,753 19,980,870 12ms 20ms 113ms 3.7s 0 transport_latency_assumed tick_size_change c 2,112 2,011 5ms 10ms 32ms 83ms 0 transport_latency_assumed tick_size_change g 2,432 not meas. 80ms 99ms 307ms 434ms 0 transport_latency_assumed tick_size_change h 2,436 28 19ms 36ms 201ms 301ms 0 transport_latency_assumed tick_size_change i 2,436 16 21ms 29ms 93ms 442ms 0 transport_latency_assumed tick_size_change k 2,380 381 12ms 19ms 52ms 267ms 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-23/21/2026-09-23T21.parquet sha256sum 2026-09-23T21.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.