Hour audit: 2026-09-09T14
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-09T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T14:00:00.000001077+00:00 · last event 2026-09-09T14:59:59.999991995+00:00
VOLUME 121,801,916 rows · 1,336,446,552 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 118,403,233 · e: 118,361,305 · h: 118,279,278 · g: 118,088,167 · c: 80,833,911 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 1,039,801 (0.85%) · e: 2,745,116 (2.25%) · h: 42,163,974 (34.62%) · g: 100,004 (0.08%) · c: 75,753,021 (62.19%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 121,801,916 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5769d7865d439410501ad016f08bc406dc558773e0fe97a6d8b03d23260b1daa
the corpus checksum ledger names this file with the same digest
joined 121,809,463 to merged 121,801,916, minus 7,547 (minus 0.0062%)
boundary drops 7,547 · 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-09T17:08:13Z 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 10,545,842 122,724,443 0-40 6ff7031552efe47e1c1fbe5a64e3385f93f8f655314eddbf885c845a391607b8 book 3,498,258 118,925,628 41-54 00cd576ac8d514ebf6bd1e8d331a6b10f38a90d03f7b2458607044a1443998b2 last_trade_price 78,268 4,397,136 55-55 e23a066d1d75afa0aeabbfd0481dbf268065c5248216116ce93678c79f84f42f market_resolved 2,236 209,336 56-56 0a03d2e36b182e8daa9f638122b9c32865ba147a76aaa470e05aed67a881c0b7 new_market 3,222 271,442 57-57 f496a5532297245117f783a044a60859886c34d6c456c372710ca8c21afc6431 price_change 107,670,846 1,088,412,915 58-468 777f0a033481e84e543a62072a177f00325b628a726ab412ab80e4e8405878b6 tick_size_change 3,244 118,613 469-469 6c2e96e6aafbf3f06222e0a7d3213c3b70b9a670fbbca52fb1bad8870a5013a3 EVENT MIX count share price_change 107,670,846 88.40% best_bid_ask 10,545,842 8.66% book 3,498,258 2.87% last_trade_price 78,268 0.06% tick_size_change 3,244 <0.01% new_market 3,222 <0.01% market_resolved 2,236 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,546,086 10,545,842 244 4,652 FULL book 3,502,506 3,498,258 4,248 191,709 FULL last_trade_price 78,268 78,268 0 684 FULL market_resolved 2,249 2,236 13 102 FULL new_market 3,222 3,222 0 0 FULL price_change 107,673,888 107,670,846 3,042 4,457 FULL tick_size_change 3,244 3,244 0 215 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,932,333 6,495,758 6ms 16ms 129ms 4.3s 0 transport_latency_assumed best_bid_ask e 10,540,783 236,282 42ms 61ms 327ms 24.4s 0 transport_latency_assumed best_bid_ask f 10,541,550 83,354 47ms 72ms 345ms 23.5s 0 transport_latency_assumed best_bid_ask g 10,537,426 6,071 85ms 126ms 726ms 44.1s 0 transport_latency_assumed best_bid_ask h 10,544,944 3,724,377 17ms 35ms 274ms 52.1s 0 transport_latency_assumed book c 3,380,161 3,334,744 28.3min 24.0h 32.0d 102.7d 0 book_staleness book e 316,151 46,606 2.1s 6.5h 18.0d 102.7d 0 book_staleness book f 300,532 40,213 508ms 6.2h 18.0d 102.7d 0 book_staleness book g 187,131 10,951 97ms 3.5min 2.1d 101.1d 0 book_staleness book h 184,097 65,744 23ms 20.9s 1.5d 84.2d 0 book_staleness last_trade_price c 49,715 45,930 11ms 44ms 261ms 5.3s 0 transport_latency_assumed last_trade_price e 77,456 1,721 49ms 312ms 11.2s 24.4s 0 transport_latency_assumed last_trade_price f 77,538 678 56ms 256ms 10.7s 23.6s 0 transport_latency_assumed last_trade_price g 76,607 213 98ms 507ms 10.4s 44.2s 0 transport_latency_assumed last_trade_price h 78,129 29,726 23ms 75ms 467ms 12.6s 0 transport_latency_assumed market_resolved c 1,883 1,818 3.6min 14.3min 19.3min 20.9min 0 transport_latency_assumed market_resolved e 1,209 29 43ms 152ms 478ms 1.0min 0 transport_latency_assumed market_resolved f 1,209 10 49ms 193ms 520ms 1.0min 0 transport_latency_assumed market_resolved g 1,209 not meas. 86ms 263ms 813ms 12.9s 0 transport_latency_assumed market_resolved h 1,209 379 19ms 66ms 229ms 1.0min 0 transport_latency_assumed new_market c 2,364 1,458 1.0min 5.6min 11.2min 16.3min 0 transport_latency_assumed new_market e 1,666 380 200ms 45.9s 1.8min 2.7min 0 transport_latency_assumed new_market f 1,666 337 196ms 41.2s 1.8min 2.6min 0 transport_latency_assumed new_market g 1,666 253 318ms 41.1s 1.8min 2.4min 0 transport_latency_assumed new_market h 1,666 794 119ms 42.0s 1.8min 2.6min 0 transport_latency_assumed price_change c 70,465,071 65,871,005 6ms 17ms 150ms 6.1s 0 transport_latency_assumed price_change e 107,420,796 2,460,039 42ms 74ms 613ms 24.9s 0 transport_latency_assumed price_change f 107,477,494 915,156 47ms 85ms 568ms 23.6s 0 transport_latency_assumed price_change g 107,280,884 82,516 85ms 159ms 1.8s 44.8s 0 transport_latency_assumed price_change h 107,465,989 38,342,130 18ms 39ms 305ms 52.2s 0 transport_latency_assumed tick_size_change c 2,384 2,308 6ms 12ms 55ms 185ms 0 transport_latency_assumed tick_size_change e 3,244 59 42ms 90ms 224ms 427ms 0 transport_latency_assumed tick_size_change f 3,244 53 47ms 74ms 245ms 476ms 0 transport_latency_assumed tick_size_change g 3,244 not meas. 85ms 146ms 423ms 1.1s 0 transport_latency_assumed tick_size_change h 3,244 824 18ms 39ms 176ms 910ms 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-09/14/2026-09-09T14.parquet sha256sum 2026-09-09T14.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.