Hour audit: 2026-09-07T02
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-07T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T02:00:00.000010314+00:00 · last event 2026-09-07T02:59:59.999919992+00:00
VOLUME 111,637,860 rows · 1,112,109,073 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,613,563 · f: 111,595,232 · g: 111,533,676 · h: 111,447,395 · e: 111,423,592 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 106,941,172 (95.79%) · f: 260,839 (0.23%) · g: 32,972 (0.03%) · h: 3,773,612 (3.38%) · e: 629,265 (0.56%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 111,637,860 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 52e1aace7019f5898aa8727ed240731826fdd7e47275d343889b90c1d30b0091
the corpus checksum ledger names this file with the same digest
joined 111,640,391 to merged 111,637,860, minus 2,531 (minus 0.0023%)
boundary drops 2,531 · 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-07T04:26:05Z 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 11,877,437 128,929,427 0-45 35bf1a7c81f451861bde2c53e3a33c3b46319d6060fd1f429dd76fc0bb70faa4 book 120,387 11,876,694 46-46 017d9f6edeac10f7f9c09181ad832df3cf64606896374da0e2c7c1815a945f22 last_trade_price 46,481 2,587,561 47-47 a8c3314cb0a027b90b5c2b499779ebe66cfb186cae68a52194d99b07d129d7fb market_resolved 1,703 262,032 48-48 e4c3d6a3db3c02c054bf465cf9d10c8c2457a390e32be0f5b721135324646bf0 new_market 3,812 379,357 49-49 69fabaf85c2d99f455f52e36d616f31283921a4216538ec3cd15386a8b034448 price_change 99,585,492 966,710,284 50-429 b1845c9472dabe481e6b241348dcd4d4897c56ddc7a02335250c35bcc704788c tick_size_change 2,548 93,169 430-430 b95593a2c38974007b550688d0a264db5d45fb2c5130ffcb898312e914130dd2 EVENT MIX count share price_change 99,585,492 89.20% best_bid_ask 11,877,437 10.64% book 120,387 0.11% last_trade_price 46,481 0.04% new_market 3,812 <0.01% tick_size_change 2,548 <0.01% market_resolved 1,703 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,877,729 11,877,437 292 606 FULL book 120,387 120,387 0 8,441 FULL last_trade_price 46,482 46,481 1 0 FULL market_resolved 1,703 1,703 0 0 FULL new_market 3,812 3,812 0 0 FULL price_change 99,587,730 99,585,492 2,238 804 FULL tick_size_change 2,548 2,548 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,875,482 11,380,957 4ms 10ms 173ms 9.6s 0 transport_latency_assumed best_bid_ask e 11,874,210 69,400 38ms 45ms 259ms 6.2s 0 transport_latency_assumed best_bid_ask f 11,873,988 29,053 49ms 60ms 283ms 8.2s 0 transport_latency_assumed best_bid_ask g 11,872,521 2,863 82ms 107ms 625ms 30.8s 0 transport_latency_assumed best_bid_ask h 11,874,149 395,164 18ms 33ms 468ms 50.0s 0 transport_latency_assumed book c 105,788 98,571 6ms 194ms 10.1h 82.1d 0 book_staleness book e 100,075 2,443 39ms 155ms 3.9s 42.3d 0 book_staleness book f 100,329 1,923 51ms 192ms 4.3s 81.5d 0 book_staleness book g 108,146 9,863 92ms 3.0s 19.5h 81.7d 0 book_staleness book h 101,235 7,587 21ms 109ms 3.5min 81.5d 0 book_staleness last_trade_price c 46,465 44,050 9ms 44ms 357ms 5.1s 0 transport_latency_assumed last_trade_price e 46,444 399 43ms 105ms 1.2s 6.2s 0 transport_latency_assumed last_trade_price f 46,419 99 55ms 127ms 1.6s 8.2s 0 transport_latency_assumed last_trade_price g 46,300 8 96ms 220ms 3.9s 31.1s 0 transport_latency_assumed last_trade_price h 46,415 1,925 23ms 71ms 715ms 46.9s 0 transport_latency_assumed market_resolved c 1,625 1,567 4ms 11ms 188ms 671ms 0 transport_latency_assumed market_resolved e 1,625 88 39ms 205ms 54.6s 1.0min 0 transport_latency_assumed market_resolved f 1,625 6 50ms 207ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,625 not meas. 86ms 290ms 1.4s 1.0min 0 transport_latency_assumed market_resolved h 1,625 42 18ms 104ms 53.9s 59.5s 0 transport_latency_assumed new_market c 2,409 1,432 112ms 21.2s 1.6min 2.0h 0 transport_latency_assumed new_market e 2,409 596 172ms 23.6s 1.7min 1.6h 0 transport_latency_assumed new_market f 2,409 376 229ms 22.9s 1.7min 2.0h 0 transport_latency_assumed new_market g 2,409 358 315ms 21.1s 1.7min 1.9min 0 transport_latency_assumed new_market h 2,409 1,050 167ms 22.3s 1.8min 25.3min 0 transport_latency_assumed price_change c 99,579,246 95,412,091 4ms 11ms 173ms 10.4s 0 transport_latency_assumed price_change e 99,396,281 556,339 38ms 49ms 293ms 6.2s 0 transport_latency_assumed price_change f 99,567,914 229,382 49ms 64ms 313ms 8.3s 0 transport_latency_assumed price_change g 99,500,127 19,880 83ms 116ms 672ms 31.1s 0 transport_latency_assumed price_change h 99,419,014 3,367,800 18ms 36ms 430ms 51.8s 0 transport_latency_assumed tick_size_change c 2,548 2,504 4ms 6ms 29ms 58ms 0 transport_latency_assumed tick_size_change e 2,548 not meas. 38ms 42ms 151ms 282ms 0 transport_latency_assumed tick_size_change f 2,548 not meas. 48ms 52ms 129ms 257ms 0 transport_latency_assumed tick_size_change g 2,548 not meas. 80ms 95ms 319ms 484ms 0 transport_latency_assumed tick_size_change h 2,548 44 18ms 30ms 442ms 5.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-07/02/2026-09-07T02.parquet sha256sum 2026-09-07T02.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.