Hour audit: 2026-09-12T07
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-12T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T07:00:00.000005172+00:00 · last event 2026-09-12T07:59:59.999982741+00:00
VOLUME 109,718,325 rows · 1,156,537,548 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 106,897,486 · f: 106,868,718 · g: 106,801,903 · h: 103,500,270 · c: 75,089,734 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,997,952 (4.56%) · f: 342,682 (0.31%) · g: 61,700 (0.06%) · h: 31,858,519 (29.04%) · c: 72,457,472 (66.04%) (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 109,718,325 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 88a6c0f475faa724976425005f37a11c8ed3db8f76707e1c0c0171744da50c44
the corpus checksum ledger names this file with the same digest
joined 109,722,621 to merged 109,718,325, minus 4,296 (minus 0.0039%)
boundary drops 4,296 · 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-12T09:34:51Z 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,631,267 116,120,706 0-40 86132782db98d4d74b47341055074f2e0ec52a36fbea5147ca3b109ee3ff323a book 3,072,722 116,836,879 41-52 58fb2bf94192ccc9bb44ca7a38929c4c8c986b1584dc0930f793ac9d548f707e last_trade_price 47,674 2,763,647 53-53 547b8bc704c85574f125da90d036f65886dc809b1954d80a45035493f098e818 market_resolved 740 84,569 54-54 081849da2965f23350d46005faf4a3414da8c4b64e987b03b899c6939b166cc7 new_market 742 68,910 55-55 38d726fc90f7a57f93341e507ae3fb4bf3b81d66cfebc93c0693af43b95c7725 price_change 95,963,548 919,351,746 56-422 cedab414d3898489f8139556f8db5b66a046f8a0446fb83922d5d94c2d0370e7 tick_size_change 1,632 60,259 423-423 e5975f1cf7dc4f73cff843f42bf8b076b13bdd555d57bd8cbddfda20b2119b14 EVENT MIX count share price_change 95,963,548 87.46% best_bid_ask 10,631,267 9.69% book 3,072,722 2.80% last_trade_price 47,674 0.04% tick_size_change 1,632 <0.01% new_market 742 <0.01% market_resolved 740 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,631,511 10,631,267 244 5,538 FULL book 3,074,608 3,072,722 1,886 194,719 FULL last_trade_price 47,674 47,674 0 755 FULL market_resolved 740 740 0 48 FULL new_market 742 742 0 37 FULL price_change 95,965,714 95,963,548 2,166 3,516 FULL tick_size_change 1,632 1,632 0 92 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,294,542 7,047,205 5ms 10ms 69ms 4.9s 0 transport_latency_assumed best_bid_ask e 10,629,476 474,401 35ms 39ms 102ms 1.7s 0 transport_latency_assumed best_bid_ask f 10,629,001 24,646 47ms 50ms 125ms 4.9s 0 transport_latency_assumed best_bid_ask g 10,627,086 2,308 84ms 107ms 287ms 13.8s 0 transport_latency_assumed best_bid_ask h 10,258,247 3,082,707 17ms 25ms 81ms 11.6s 0 transport_latency_assumed book c 2,830,769 2,782,155 21.9min 14.0h 31.5d 105.4d 0 book_staleness book e 273,519 50,917 1.0min 10.8h 20.8d 105.4d 0 book_staleness book f 271,738 46,016 59.6s 10.7h 20.8d 105.4d 0 book_staleness book g 215,338 34,223 8.8s 7.7h 20.7d 105.4d 0 book_staleness book h 648,181 159,411 8.2min 13.9h 30.5d 105.4d 0 book_staleness last_trade_price c 29,855 28,640 11ms 40ms 202ms 4.9s 0 transport_latency_assumed last_trade_price e 47,635 2,532 41ms 93ms 339ms 5.0s 0 transport_latency_assumed last_trade_price f 47,531 282 53ms 106ms 394ms 5.0s 0 transport_latency_assumed last_trade_price g 47,530 37 96ms 205ms 650ms 6.7s 0 transport_latency_assumed last_trade_price h 45,783 16,183 23ms 59ms 189ms 8.1s 0 transport_latency_assumed market_resolved c 617 611 7ms 8.0min 12.6min 12.9min 0 transport_latency_assumed market_resolved e 506 22 36ms 117ms 274ms 551ms 0 transport_latency_assumed market_resolved f 506 2 48ms 128ms 294ms 455ms 0 transport_latency_assumed market_resolved g 506 not meas. 93ms 247ms 445ms 670ms 0 transport_latency_assumed market_resolved h 505 105 18ms 60ms 4.6min 4.6min 0 transport_latency_assumed new_market c 623 409 139ms 6.3min 9.9min 10.7min 0 transport_latency_assumed new_market e 442 82 167ms 15.1s 45.5s 1.3min 0 transport_latency_assumed new_market f 442 58 157ms 11.6s 23.3s 55.0s 0 transport_latency_assumed new_market g 442 10 263ms 831ms 27.5s 1.0min 0 transport_latency_assumed new_market h 442 183 80ms 354ms 20.6s 1.2min 0 transport_latency_assumed price_change c 64,932,040 62,597,188 5ms 11ms 91ms 4.9s 0 transport_latency_assumed price_change e 95,944,276 4,469,946 35ms 39ms 142ms 2.4s 0 transport_latency_assumed price_change f 95,917,868 271,674 47ms 51ms 165ms 5.0s 0 transport_latency_assumed price_change g 95,909,369 25,122 84ms 115ms 353ms 14.8s 0 transport_latency_assumed price_change h 92,545,532 28,599,618 17ms 27ms 93ms 12.9s 0 transport_latency_assumed tick_size_change c 1,288 1,264 5ms 10ms 29ms 115ms 0 transport_latency_assumed tick_size_change e 1,632 52 35ms 40ms 189ms 665ms 0 transport_latency_assumed tick_size_change f 1,632 4 47ms 52ms 292ms 495ms 0 transport_latency_assumed tick_size_change g 1,632 not meas. 84ms 109ms 515ms 696ms 0 transport_latency_assumed tick_size_change h 1,580 312 17ms 22ms 69ms 110ms 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-12/07/2026-09-12T07.parquet sha256sum 2026-09-12T07.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.