Hour audit: 2026-09-08T20
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-08T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T20:00:00.000050870+00:00 · last event 2026-09-08T20:59:59.999933360+00:00
VOLUME 103,411,209 rows · 1,127,736,165 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 102,512,077 · f: 102,452,190 · e: 102,393,671 · g: 102,308,402 · c: 93,993,067 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,696,053 (13.24%) · f: 639,544 (0.62%) · e: 1,469,296 (1.42%) · g: 69,656 (0.07%) · c: 87,536,660 (84.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 103,411,209 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 20a86467206ec7a8d5be36087d16bca005ce064040901e3654f0966e720e5d30
the corpus checksum ledger names this file with the same digest
joined 103,414,370 to merged 103,411,209, minus 3,161 (minus 0.0031%)
boundary drops 3,161 · 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-08T21:56:45Z as cefgh
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 9,351,414 108,436,259 0-35 acc3c2b72019ba8b6b1b0e51f8a4abaf54c7bdfffc78a44440f95ecdfe604b1d book 958,839 68,042,646 36-39 733455f4f9c6701d77fb54219e31b9f987f1f09d2c13a127af678c9ecfb23b61 last_trade_price 64,987 3,629,787 40-40 ef52e0dd00e5fc39fea7aa270b4ddce604a7a00241299d3a85966c70b083f302 market_resolved 1,032 147,022 41-41 9aac9182b6a807ab00887e68b31ae920002fe9d9611dc2a542d077ee03ef3822 new_market 6,781 682,765 42-42 f045fe472789b6ab170a361a76870d018823dbe4d6fe71ed915fb7c1b951bc2f price_change 93,020,328 945,337,537 43-397 3460630c604983ebbbef7f553c261f4f8375a3ba6ed2b16a4c7273c9d86b95b0 tick_size_change 7,828 282,482 398-398 f7a5dd7137106e9c441edb75f2b734bbdd6f3a60d2514260f60f3258c1e33b66 EVENT MIX count share price_change 93,020,328 89.95% best_bid_ask 9,351,414 9.04% book 958,839 0.93% last_trade_price 64,987 0.06% tick_size_change 7,828 <0.01% new_market 6,781 <0.01% market_resolved 1,032 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,351,719 9,351,414 305 1,893 FULL book 958,862 958,839 23 191,093 FULL last_trade_price 64,994 64,987 7 139 FULL market_resolved 1,032 1,032 0 23 FULL new_market 6,781 6,781 0 0 FULL price_change 93,023,154 93,020,328 2,826 1,530 FULL tick_size_change 7,828 7,828 0 95 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,421,162 7,869,954 5ms 18ms 292ms 19.2s 0 transport_latency_assumed best_bid_ask e 9,346,227 137,304 42ms 69ms 397ms 19.4s 0 transport_latency_assumed best_bid_ask f 9,346,204 54,238 46ms 77ms 408ms 29.4s 0 transport_latency_assumed best_bid_ask g 9,342,722 4,165 88ms 181ms 919ms 35.4s 0 transport_latency_assumed best_bid_ask h 9,349,581 1,285,753 18ms 42ms 720ms 1.0min 0 transport_latency_assumed book c 921,143 904,432 12.0min 21.1h 28.1d 101.9d 0 book_staleness book e 145,016 6,008 47ms 2.1s 1.7h 83.3d 0 book_staleness book f 163,042 9,703 57ms 2.3min 1.4d 83.4d 0 book_staleness book g 179,692 18,412 143ms 1.1h 3.3d 101.9d 0 book_staleness book h 143,553 20,284 24ms 344ms 7.3min 83.3d 0 book_staleness last_trade_price c 59,468 55,175 11ms 63ms 443ms 5.0s 0 transport_latency_assumed last_trade_price e 64,395 908 53ms 482ms 5.9s 19.5s 0 transport_latency_assumed last_trade_price f 64,317 379 57ms 364ms 4.9s 29.5s 0 transport_latency_assumed last_trade_price g 63,662 129 106ms 806ms 8.9s 35.4s 0 transport_latency_assumed last_trade_price h 64,812 8,396 24ms 124ms 1.4s 55.2s 0 transport_latency_assumed market_resolved c 965 891 6ms 3.9min 9.4min 11.0min 0 transport_latency_assumed market_resolved e 906 54 43ms 429ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 906 3 48ms 439ms 59.7s 1.0min 0 transport_latency_assumed market_resolved g 906 not meas. 93ms 603ms 53.7s 57.8s 0 transport_latency_assumed market_resolved h 906 84 19ms 151ms 52.5s 56.4s 0 transport_latency_assumed new_market c 4,317 2,414 182ms 2.6min 7.4min 11.3min 0 transport_latency_assumed new_market e 4,234 912 222ms 1.5min 3.9min 4.5min 0 transport_latency_assumed new_market f 4,234 1,047 234ms 1.4min 3.9min 4.5min 0 transport_latency_assumed new_market g 4,234 479 377ms 1.6min 4.0min 4.5min 0 transport_latency_assumed new_market h 4,234 1,929 172ms 1.3min 3.9min 4.2min 0 transport_latency_assumed price_change c 84,578,564 78,697,259 5ms 23ms 323ms 19.2s 0 transport_latency_assumed price_change e 92,825,065 1,323,944 42ms 97ms 732ms 19.5s 0 transport_latency_assumed price_change f 92,865,659 574,128 47ms 103ms 625ms 29.5s 0 transport_latency_assumed price_change g 92,709,358 46,467 88ms 247ms 2.0s 35.4s 0 transport_latency_assumed price_change h 92,941,163 12,378,530 18ms 49ms 760ms 1.0min 0 transport_latency_assumed tick_size_change c 7,448 6,535 5ms 65ms 408ms 2.6s 0 transport_latency_assumed tick_size_change e 7,828 166 42ms 150ms 495ms 1.6s 0 transport_latency_assumed tick_size_change f 7,828 46 47ms 164ms 548ms 1.2s 0 transport_latency_assumed tick_size_change g 7,828 4 90ms 436ms 909ms 1.7s 0 transport_latency_assumed tick_size_change h 7,828 1,077 19ms 128ms 1.0s 8.5s 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-08/20/2026-09-08T20.parquet sha256sum 2026-09-08T20.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.