Hour audit: 2026-09-07T16
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-07T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T16:00:00.000005634+00:00 · last event 2026-09-07T16:59:59.999991505+00:00
VOLUME 98,974,739 rows · 1,002,509,555 bytes (956.07 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 98,910,798 · f: 98,891,752 · g: 98,829,098 · e: 96,770,200 · c: 95,853,459 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 6,890,243 (6.96%) · f: 195,800 (0.20%) · g: 26,289 (0.03%) · e: 423,469 (0.43%) · c: 91,438,938 (92.39%) (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 98,974,739 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8d9b81f5505884fdb8e4cc3d5e0d07f278cb28f66621dfc925f3c5646b4e0e47
the corpus checksum ledger names this file with the same digest
joined 98,977,171 to merged 98,974,739, minus 2,432 (minus 0.0025%)
boundary drops 2,432 · 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-07T17:56:16Z 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,111,643 110,252,138 0-38 710c095e70e262cb2ad7f2fa514aed354a04dd7700ada564ca3d4b18214dc368 book 193,615 20,067,473 39-39 568708b3692786ea35dbb3927329ad453df875179faadd79064aa0625421abe8 last_trade_price 66,130 3,764,314 40-40 714109a5ff387a1bb6d228225d9afedf01cfd09263bd258387a2c35d41ba2541 market_resolved 1,429 229,276 41-41 116348beeed9822613c6e1651c62968f03d8a17b1adf6df16d92673450639bd1 new_market 2,952 282,298 42-42 6d1d636b6bee57d8823821549f19cb7365d95e515bb7a91890a5a4d1305c9abb price_change 88,595,286 866,651,442 43-380 699c8c6d551711c7f528feb80228404e0bee4cb05c7c0edb87b935560d8b2279 tick_size_change 3,684 135,608 381-381 0ba9c6d5b0de5f0953f4bcf7cc44b4aa800c84bbef85fb95c894608d1da00df0 EVENT MIX count share price_change 88,595,286 89.51% best_bid_ask 10,111,643 10.22% book 193,615 0.20% last_trade_price 66,130 0.07% tick_size_change 3,684 <0.01% new_market 2,952 <0.01% market_resolved 1,429 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,111,842 10,111,643 199 2,841 FULL book 193,617 193,615 2 23,214 FULL last_trade_price 66,131 66,130 1 211 FULL market_resolved 1,429 1,429 0 65 FULL new_market 2,952 2,952 0 0 FULL price_change 88,597,516 88,595,286 2,230 4,501 FULL tick_size_change 3,684 3,684 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,765,848 9,332,064 5ms 11ms 159ms 20.3s 0 transport_latency_assumed best_bid_ask e 9,888,100 41,547 39ms 46ms 240ms 16.5s 0 transport_latency_assumed best_bid_ask f 10,107,448 19,868 44ms 55ms 265ms 16.0s 0 transport_latency_assumed best_bid_ask g 10,105,855 1,380 85ms 135ms 619ms 26.9s 0 transport_latency_assumed best_bid_ask h 10,109,262 716,784 18ms 25ms 232ms 40.2s 0 transport_latency_assumed book c 143,204 134,716 7ms 74ms 6.1h 99.2d 0 book_staleness book e 148,956 17,357 42ms 6.4s 13.0h 82.3d 0 book_staleness book f 149,083 11,329 48ms 904ms 6.8h 99.2d 0 book_staleness book g 152,163 14,318 98ms 4.7s 10.5h 82.3d 0 book_staleness book h 144,795 15,895 22ms 118ms 5.0h 82.3d 0 book_staleness last_trade_price c 64,670 61,439 10ms 45ms 272ms 5.1s 0 transport_latency_assumed last_trade_price e 63,279 272 46ms 165ms 1.4s 16.6s 0 transport_latency_assumed last_trade_price f 66,062 114 52ms 200ms 2.0s 16.1s 0 transport_latency_assumed last_trade_price g 65,759 13 104ms 557ms 6.3s 26.7s 0 transport_latency_assumed last_trade_price h 66,064 4,292 23ms 69ms 427ms 9.5s 0 transport_latency_assumed market_resolved c 1,353 1,292 5ms 14ms 58.9s 2.5min 0 transport_latency_assumed market_resolved e 1,375 29 41ms 202ms 57.8s 2.1min 0 transport_latency_assumed market_resolved f 1,397 3 47ms 201ms 704ms 57.8s 0 transport_latency_assumed market_resolved g 1,397 not meas. 94ms 382ms 863ms 2.6s 0 transport_latency_assumed market_resolved h 1,397 105 19ms 75ms 160ms 690ms 0 transport_latency_assumed new_market c 1,796 1,089 103ms 20.6s 59.4s 1.9min 0 transport_latency_assumed new_market e 1,796 425 198ms 22.7s 1.2min 2.0min 0 transport_latency_assumed new_market f 1,796 274 229ms 20.9s 50.6s 2.4min 0 transport_latency_assumed new_market g 1,796 280 360ms 23.3s 1.2min 2.1min 0 transport_latency_assumed new_market h 1,796 884 133ms 20.1s 1.1min 1.8min 0 transport_latency_assumed price_change c 85,873,052 81,905,062 5ms 12ms 174ms 21.0s 0 transport_latency_assumed price_change e 86,663,062 363,804 39ms 56ms 405ms 16.6s 0 transport_latency_assumed price_change f 88,562,282 164,192 45ms 65ms 442ms 16.1s 0 transport_latency_assumed price_change g 88,498,448 10,298 85ms 163ms 1.1s 27.0s 0 transport_latency_assumed price_change h 88,583,800 6,151,930 18ms 29ms 266ms 48.3s 0 transport_latency_assumed tick_size_change c 3,536 3,276 5ms 22ms 295ms 526ms 0 transport_latency_assumed tick_size_change e 3,632 35 39ms 65ms 566ms 967ms 0 transport_latency_assumed tick_size_change f 3,684 20 45ms 96ms 585ms 4.8s 0 transport_latency_assumed tick_size_change g 3,680 not meas. 86ms 262ms 917ms 1.5s 0 transport_latency_assumed tick_size_change h 3,684 353 18ms 51ms 531ms 2.2s 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-07/16/2026-09-07T16.parquet sha256sum 2026-09-07T16.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.