Hour audit: 2026-09-22T20
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-22T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T20:00:00.000029377+00:00 · last event 2026-09-22T20:59:59.921292154+00:00
VOLUME 112,267,136 rows · 1,249,091,657 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured k: 111,227,783 · h: 111,163,529 · i: 107,212,116 · f: 106,987,875 · c: 105,559,992 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 11,812,133 (10.52%) · h: 3,911,992 (3.48%) · i: 3,300,457 (2.94%) · f: 530,018 (0.47%) · c: 92,712,536 (82.58%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 15768698ffc81fcae1063d5c5dc794e711d7a8b87d4650b48b5d8db0a933375e
the corpus checksum ledger names this file with the same digest
joined 112,272,285 to merged 112,267,136, minus 5,149 (minus 0.0046%)
boundary drops 5,149 · 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-23T01:15:01Z as cfhik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 11,377,188 136,775,313 0-43 be43a6ab5406bb06519e07ea4887f8418ffd43a5d176a2f512d2addd7eed8196 book 1,435,789 83,719,476 44-49 8e75d442c37568f5d49aeaf1915ef336fe23f68822f099f2241d9b6ef44b1261 last_trade_price 55,349 3,195,977 50-50 449026d22c6fa9dca04c90aedaf571d728773999805450211e59580853ac3143 market_resolved 1,063 148,992 51-51 75a44ba527b6d36deabfe4dce5750eb07196428fac837b736fe1b30fcdf11286 new_market 10,885 1,089,517 52-52 ba8347ff0a7d3e3eec3d8f0743f9b6b27ce751bbab388676ba808f29104059ac price_change 99,383,406 1,022,752,437 53-432 1a7e9cdda3e09092d5bb515a168adb130e95ef526333aff8e6e1f2549a7ddde7 tick_size_change 3,456 128,863 433-433 2375cdf1c86af53ea0d13acb03bebdb8528b2669e4285bc05b436d765a4e0168 EVENT MIX count share price_change 99,383,406 88.52% best_bid_ask 11,377,188 10.13% book 1,435,789 1.28% last_trade_price 55,349 0.05% new_market 10,885 <0.01% tick_size_change 3,456 <0.01% market_resolved 1,063 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,377,345 11,377,188 157 3,740 FULL book 1,439,649 1,435,789 3,860 173,888 FULL last_trade_price 55,349 55,349 0 275 FULL market_resolved 1,063 1,063 0 36 FULL new_market 10,885 10,885 0 77 FULL price_change 99,384,538 99,383,406 1,132 4,829 FULL tick_size_change 3,456 3,456 0 93 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,764,706 9,526,421 5ms 28ms 255ms 10.8s 0 transport_latency_assumed best_bid_ask f 10,924,298 13,947 49ms 112ms 508ms 24.3s 0 transport_latency_assumed best_bid_ask h 11,369,845 366,856 18ms 51ms 695ms 1.6min 0 transport_latency_assumed best_bid_ask i 11,009,668 330,987 21ms 40ms 197ms 4.2s 0 transport_latency_assumed best_bid_ask k 11,371,969 1,138,977 13ms 38ms 337ms 1.2min 0 transport_latency_assumed book c 788,901 601,041 4.5min 3.3d 41.2d 115.9d 0 book_staleness book f 750,012 392,928 5.3min 3.1d 41.1d 115.9d 0 book_staleness book h 453,711 202,891 2.2min 1.6d 34.0d 115.9d 0 book_staleness book i 170,286 29,586 83ms 18.9min 17.3d 115.9d 0 book_staleness book k 462,179 209,343 2.2min 1.6d 33.2d 115.9d 0 book_staleness last_trade_price c 51,983 45,450 6ms 50ms 386ms 4.4s 0 transport_latency_assumed last_trade_price f 52,509 64 94ms 1.9s 11.0s 24.3s 0 transport_latency_assumed last_trade_price h 54,786 1,700 20ms 153ms 1.3s 1.6min 0 transport_latency_assumed last_trade_price i 53,251 1,378 24ms 241ms 1.3s 2.9s 0 transport_latency_assumed last_trade_price k 55,030 6,757 14ms 84ms 544ms 51.4s 0 transport_latency_assumed market_resolved c 888 754 5ms 109ms 4.8min 5.1min 0 transport_latency_assumed market_resolved f 925 73 54ms 49.5s 5.0min 5.0min 0 transport_latency_assumed market_resolved h 919 42 19ms 182ms 57.3s 1.0min 0 transport_latency_assumed market_resolved i 913 92 23ms 248ms 1.2min 2.4min 0 transport_latency_assumed market_resolved k 919 102 14ms 96ms 50.6s 57.7s 0 transport_latency_assumed new_market c 6,835 3,660 73ms 2.7min 6.7min 441.1d 0 transport_latency_assumed new_market f 6,977 835 158ms 2.8min 6.7min 441.1d 0 transport_latency_assumed new_market h 6,912 2,608 93ms 2.5min 6.0min 441.0d 0 transport_latency_assumed new_market i 6,912 2,035 99ms 2.6min 6.0min 441.1d 0 transport_latency_assumed new_market k 6,912 1,747 115ms 2.6min 6.1min 441.1d 0 transport_latency_assumed price_change c 93,943,383 82,532,362 5ms 33ms 278ms 10.8s 0 transport_latency_assumed price_change f 95,249,774 122,150 50ms 163ms 2.3s 24.4s 0 transport_latency_assumed price_change h 99,273,900 3,337,813 18ms 63ms 763ms 1.6min 0 transport_latency_assumed price_change i 95,967,782 2,936,216 21ms 53ms 325ms 4.3s 0 transport_latency_assumed price_change k 99,327,318 10,454,865 13ms 45ms 368ms 1.2min 0 transport_latency_assumed tick_size_change c 3,296 2,848 5ms 42ms 306ms 698ms 0 transport_latency_assumed tick_size_change f 3,380 21 49ms 124ms 474ms 721ms 0 transport_latency_assumed tick_size_change h 3,456 82 18ms 73ms 428ms 55.6s 0 transport_latency_assumed tick_size_change i 3,304 163 21ms 46ms 178ms 367ms 0 transport_latency_assumed tick_size_change k 3,456 342 13ms 63ms 296ms 521ms 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-22/20/2026-09-22T20.parquet sha256sum 2026-09-22T20.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.