Hour audit: 2026-09-07T11
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-07T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T11:00:00.000149529+00:00 · last event 2026-09-07T11:59:59.999603208+00:00
VOLUME 91,406,871 rows · 924,146,079 bytes (881.33 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 91,245,241 · h: 91,181,581 · e: 91,085,740 · f: 91,076,285 · c: 91,043,045 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 94,230 (0.10%) · h: 2,518,804 (2.76%) · e: 225,586 (0.25%) · f: 119,500 (0.13%) · c: 88,448,751 (96.76%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 91,406,871 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7fad42aad5efe0561b1e37b89b7aa3039e7aadc6035a810d501b610309a457be
the corpus checksum ledger names this file with the same digest
joined 91,408,477 to merged 91,406,871, minus 1,606 (minus 0.0018%)
boundary drops 1,606 · 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-07T12:54:23Z 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,321,268 100,811,406 0-35 bd3d032bef08173f5190394d4445ce5dcf827483e23cdb7e0a17cd01cd29e3c1 book 269,718 26,121,528 36-37 8259bc744c4384f78dff70bf3c0e19783818469bf277e6029d681e4190a1b7f1 last_trade_price 53,741 3,039,996 38-38 fbaa5231cecfd26a569995a088ade85eee223d1c8c4d769ac9306b12b870f9b2 market_resolved 698 113,577 39-39 32e1c9b3c6cccbbbada7cc7bda39f3fa81ab08c6001b181dfc2a1bc9a379adbf new_market 1,274 134,659 40-40 2a6e414490b2b2feca8f0aef1d8616ebdd5bcc89a0afd1927dab0d6c9b7bb5b8 price_change 81,757,988 792,799,533 41-352 574829789a93b4dbe695f4125c976e277d48920b4cf474022499ea697b57653b tick_size_change 2,184 81,057 353-353 b18dcde49b887e0851a4b9f54d08b1b9918b0bbc1aa3f4104daf38618f5126d3 EVENT MIX count share price_change 81,757,988 89.44% best_bid_ask 9,321,268 10.20% book 269,718 0.30% last_trade_price 53,741 0.06% tick_size_change 2,184 <0.01% new_market 1,274 <0.01% market_resolved 698 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,321,434 9,321,268 166 164 FULL book 269,722 269,718 4 60,297 FULL last_trade_price 53,741 53,741 0 0 FULL market_resolved 698 698 0 0 FULL new_market 1,274 1,274 0 0 FULL price_change 81,759,424 81,757,988 1,436 931 FULL tick_size_change 2,184 2,184 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,320,868 9,066,460 5ms 8ms 71ms 11.0s 0 transport_latency_assumed best_bid_ask e 9,319,360 17,582 39ms 43ms 156ms 4.2s 0 transport_latency_assumed best_bid_ask f 9,319,476 9,000 44ms 49ms 166ms 3.0s 0 transport_latency_assumed best_bid_ask g 9,318,684 935 78ms 95ms 326ms 9.8s 0 transport_latency_assumed best_bid_ask h 9,319,550 227,291 17ms 21ms 112ms 40.4s 0 transport_latency_assumed book c 113,068 108,089 7ms 19ms 10.3s 38.1d 0 book_staleness book e 112,610 2,117 41ms 156ms 3.7s 82.0d 0 book_staleness book f 112,979 1,839 47ms 184ms 16.0s 82.0d 0 book_staleness book g 154,545 43,106 91ms 46.5min 9.1d 100.6d 0 book_staleness book h 226,666 114,567 1.6s 2.2h 22.9d 100.6d 0 book_staleness last_trade_price c 53,687 51,721 10ms 39ms 204ms 7.7s 0 transport_latency_assumed last_trade_price e 53,603 288 45ms 138ms 867ms 5.0s 0 transport_latency_assumed last_trade_price f 53,642 88 51ms 158ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 53,638 39 90ms 243ms 1.9s 10.0s 0 transport_latency_assumed last_trade_price h 53,669 1,605 22ms 70ms 365ms 8.0s 0 transport_latency_assumed market_resolved c 689 672 5ms 9ms 112ms 1.0min 0 transport_latency_assumed market_resolved e 689 2 40ms 174ms 7.9s 1.0min 0 transport_latency_assumed market_resolved f 689 9 45ms 189ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 689 3 82ms 244ms 777ms 1.0s 0 transport_latency_assumed market_resolved h 689 12 17ms 79ms 204ms 1.0min 0 transport_latency_assumed new_market c 861 506 84ms 13.5s 44.2s 1.2min 0 transport_latency_assumed new_market e 861 194 172ms 18.3s 46.4s 1.9min 0 transport_latency_assumed new_market f 861 106 196ms 15.7s 31.3s 1.3min 0 transport_latency_assumed new_market g 861 77 264ms 14.1s 32.4s 1.6min 0 transport_latency_assumed new_market h 861 391 123ms 17.6s 31.4s 1.2min 0 transport_latency_assumed price_change c 81,551,688 79,219,181 5ms 9ms 84ms 11.3s 0 transport_latency_assumed price_change e 81,596,433 205,403 39ms 47ms 224ms 4.2s 0 transport_latency_assumed price_change f 81,586,454 108,458 44ms 52ms 238ms 4.9s 0 transport_latency_assumed price_change g 81,714,640 50,070 78ms 99ms 440ms 9.9s 0 transport_latency_assumed price_change h 81,577,962 2,174,876 17ms 23ms 142ms 40.8s 0 transport_latency_assumed tick_size_change c 2,184 2,122 5ms 8ms 45ms 84ms 0 transport_latency_assumed tick_size_change e 2,184 not meas. 39ms 43ms 112ms 208ms 0 transport_latency_assumed tick_size_change f 2,184 not meas. 44ms 52ms 148ms 238ms 0 transport_latency_assumed tick_size_change g 2,184 not meas. 78ms 94ms 223ms 385ms 0 transport_latency_assumed tick_size_change h 2,184 62 17ms 21ms 63ms 157ms 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/11/2026-09-07T11.parquet sha256sum 2026-09-07T11.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.