Hour audit: 2026-09-13T06
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-13T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T06:00:00.000023584+00:00 · last event 2026-09-13T06:59:59.999990250+00:00
VOLUME 87,568,216 rows · 871,000,639 bytes (830.65 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 87,464,139 · h: 87,448,168 · e: 87,444,452 · g: 87,436,006 · f: 87,434,455 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 84,783,751 (96.82%) · h: 2,330,799 (2.66%) · e: 261,819 (0.30%) · g: 54,857 (0.06%) · f: 136,990 (0.16%) (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 87,568,216 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7c468cf01aa42950db29b555871219d06a8cfe1b339ee968d07f169968d6bede
the corpus checksum ledger names this file with the same digest
joined 87,570,052 to merged 87,568,216, minus 1,836 (minus 0.0021%)
boundary drops 1,836 · 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-13T07:53:28Z 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,715,556 102,790,004 0-37 7a1d7309255a0675e812044cf0cf382dac5093b8eb139beee86055f3821bdb64 book 225,282 23,279,067 38-38 9c592eadb5cdcbedf5f68eb771fa04afc48a37df250801ecf4379454cf317a01 last_trade_price 44,799 2,567,635 39-39 019c6e3b0a8e14d1a004c7b6fa49ae547859a1fcae1aeca347fdedd5951cf6e5 market_resolved 1,473 240,787 40-40 99167c14071a25abbaa4904ace5b49aa9c4f34b01de8f1c4ea5710330bdd1988 new_market 1,144 124,527 41-41 718c2039d516f0e52185d022f325b23d638c01c2d2abaf1b584700ccc6563ee4 price_change 77,577,978 740,926,307 42-337 977e18fdbb8661d97204ad971f36d1a8c359a17381fd30b84ccf46be8b637ac8 tick_size_change 1,984 72,547 338-338 875d4fa9249d89f99cb6c009f67f506a610ba91c5fed64bf6eb641014d320a38 EVENT MIX count share price_change 77,577,978 88.59% best_bid_ask 9,715,556 11.09% book 225,282 0.26% last_trade_price 44,799 0.05% tick_size_change 1,984 <0.01% market_resolved 1,473 <0.01% new_market 1,144 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,715,732 9,715,556 176 214 FULL book 225,282 225,282 0 60,164 FULL last_trade_price 44,799 44,799 0 1 FULL market_resolved 1,473 1,473 0 0 FULL new_market 1,144 1,144 0 0 FULL price_change 77,579,638 77,577,978 1,660 64 FULL tick_size_change 1,984 1,984 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,714,264 9,448,488 5ms 8ms 80ms 5.8s 0 transport_latency_assumed best_bid_ask e 9,713,784 21,505 40ms 43ms 100ms 1.5s 0 transport_latency_assumed best_bid_ask f 9,713,745 9,505 47ms 50ms 111ms 9.7s 0 transport_latency_assumed best_bid_ask g 9,712,210 1,233 77ms 92ms 278ms 12.5s 0 transport_latency_assumed best_bid_ask h 9,714,278 234,825 18ms 20ms 78ms 45.2s 0 transport_latency_assumed book c 128,656 121,325 7ms 2.8h 7.7d 106.3d 0 book_staleness book e 125,395 27,744 42ms 1.9h 7.7d 98.6d 0 book_staleness book f 112,449 16,773 49ms 9.0min 5.8d 98.6d 0 book_staleness book g 131,503 34,374 90ms 3.0h 10.5d 106.4d 0 book_staleness book h 117,306 25,066 22ms 37.0min 5.8d 106.3d 0 book_staleness last_trade_price c 44,761 43,172 10ms 38ms 182ms 5.0s 0 transport_latency_assumed last_trade_price e 44,709 174 45ms 95ms 275ms 5.0s 0 transport_latency_assumed last_trade_price f 44,713 69 53ms 104ms 354ms 5.0s 0 transport_latency_assumed last_trade_price g 44,753 13 91ms 207ms 880ms 12.5s 0 transport_latency_assumed last_trade_price h 44,762 1,371 23ms 54ms 242ms 5.3s 0 transport_latency_assumed market_resolved c 1,466 1,392 5ms 11ms 339ms 936ms 0 transport_latency_assumed market_resolved e 1,466 18 44ms 190ms 433ms 59.6s 0 transport_latency_assumed market_resolved f 1,466 2 51ms 196ms 449ms 59.6s 0 transport_latency_assumed market_resolved g 1,466 not meas. 91ms 317ms 744ms 1.3s 0 transport_latency_assumed market_resolved h 1,466 61 28ms 64ms 328ms 39.1s 0 transport_latency_assumed new_market c 812 384 104ms 643ms 31.3s 4.1h 0 transport_latency_assumed new_market e 812 180 137ms 15.7s 31.8s 49.1s 0 transport_latency_assumed new_market f 812 165 132ms 545ms 31.7s 3.6h 0 transport_latency_assumed new_market g 812 55 245ms 682ms 40.8s 55.0s 0 transport_latency_assumed new_market h 812 360 128ms 15.2s 33.9s 4.8h 0 transport_latency_assumed price_change c 77,572,196 75,167,014 5ms 9ms 119ms 6.4s 0 transport_latency_assumed price_change e 77,556,302 212,198 40ms 44ms 152ms 1.9s 0 transport_latency_assumed price_change f 77,559,286 110,476 47ms 51ms 166ms 9.8s 0 transport_latency_assumed price_change g 77,543,278 19,182 77ms 96ms 384ms 13.0s 0 transport_latency_assumed price_change h 77,567,560 2,069,108 18ms 21ms 132ms 46.5s 0 transport_latency_assumed tick_size_change c 1,984 1,976 5ms 6ms 12ms 20ms 0 transport_latency_assumed tick_size_change e 1,984 not meas. 40ms 44ms 90ms 125ms 0 transport_latency_assumed tick_size_change f 1,984 not meas. 47ms 49ms 69ms 131ms 0 transport_latency_assumed tick_size_change g 1,984 not meas. 77ms 90ms 239ms 306ms 0 transport_latency_assumed tick_size_change h 1,984 8 18ms 20ms 39ms 1.6s 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-13/06/2026-09-13T06.parquet sha256sum 2026-09-13T06.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.