Hour audit: 2026-09-17T11
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-17T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T11:00:00.000313812+00:00 · last event 2026-09-17T11:59:59.999967316+00:00
VOLUME 107,993,909 rows · 1,154,928,994 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 107,166,403 · e: 107,153,328 · f: 107,142,396 · c: 107,133,749 · g: 106,934,354 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,358,196 (4.04%) · e: 552,941 (0.51%) · f: 368,696 (0.34%) · c: 102,434,531 (94.85%) · g: 279,545 (0.26%) (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 107,993,909 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2518566bd4c16480c5addf1ee74b0ab0723f74579434268bcb8b2bd54ab47689
the corpus checksum ledger names this file with the same digest
joined 107,997,499 to merged 107,993,909, minus 3,590 (minus 0.0033%)
boundary drops 3,590 · 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-17T12:58:25Z 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,985,144 116,840,162 0-38 07f347cf3fbe4883c73cb4322ffa2d002f060752a522d6c66b91dc0cec960b8a book 1,192,268 82,229,759 39-43 adefe2582777147da3da4731da248d941372f93fe41b8c110da498a09a643952 last_trade_price 51,950 2,973,576 44-44 ac999cc563f8ee2606e379084f95a2488513cec6cb23690208a0e0288bf694ed market_resolved 685 110,273 45-45 03f00039403c76738b2fc4a730ecf7609063ded9ac797f9f50e86dd42046cae1 new_market 910 94,582 46-46 f9dd0ccc24d091fd70eca340e6c34dcb29434317f42f98f4da48fe9d5a509b62 price_change 96,759,668 951,327,095 47-416 d698bc294455c756429cfa3cb66ec8b90223a174788980d05b9f388dac1521fb tick_size_change 3,284 120,514 417-417 2c70b97deaeb2db7adfd2631f67412932b642d4bff3f40b470ecbb1a7eaf0abc EVENT MIX count share price_change 96,759,668 89.60% best_bid_ask 9,985,144 9.25% book 1,192,268 1.10% last_trade_price 51,950 0.05% tick_size_change 3,284 <0.01% new_market 910 <0.01% market_resolved 685 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,985,306 9,985,144 162 178 FULL book 1,193,692 1,192,268 1,424 108,508 FULL last_trade_price 51,950 51,950 0 6 FULL market_resolved 685 685 0 16 FULL new_market 910 910 0 0 FULL price_change 96,761,672 96,759,668 2,004 36 FULL tick_size_change 3,284 3,284 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,982,654 9,586,798 5ms 11ms 87ms 2.8s 0 transport_latency_assumed best_bid_ask e 9,981,186 27,677 42ms 48ms 162ms 10.8s 0 transport_latency_assumed best_bid_ask f 9,980,575 11,478 47ms 57ms 191ms 8.3s 0 transport_latency_assumed best_bid_ask g 9,971,019 1,526 77ms 96ms 303ms 19.3s 0 transport_latency_assumed best_bid_ask h 9,980,581 357,665 18ms 27ms 114ms 15.8s 0 transport_latency_assumed book c 427,252 295,362 1.8min 15.5h 35.7d 110.6d 0 book_staleness book e 457,658 217,838 2.0min 15.3h 35.7d 110.6d 0 book_staleness book f 454,722 218,738 1.9min 16.2h 35.7d 110.6d 0 book_staleness book g 487,997 252,664 2.0min 18.7h 35.9d 110.6d 0 book_staleness book h 443,018 207,666 1.9min 14.1h 35.7d 110.6d 0 book_staleness last_trade_price c 51,744 49,203 11ms 46ms 209ms 4.9s 0 transport_latency_assumed last_trade_price e 51,779 190 50ms 186ms 2.0s 10.8s 0 transport_latency_assumed last_trade_price f 51,700 218 56ms 180ms 1.2s 8.4s 0 transport_latency_assumed last_trade_price g 51,367 18 93ms 418ms 6.5s 19.1s 0 transport_latency_assumed last_trade_price h 51,562 2,321 25ms 80ms 367ms 8.2s 0 transport_latency_assumed market_resolved c 656 643 6ms 16ms 108ms 426ms 0 transport_latency_assumed market_resolved e 656 2 120ms 293ms 17.3s 17.4s 0 transport_latency_assumed market_resolved f 656 14 120ms 212ms 17.2s 17.2s 0 transport_latency_assumed market_resolved g 672 16 204ms 346ms 718ms 1.0s 0 transport_latency_assumed market_resolved h 656 10 41ms 89ms 17.5s 17.5s 0 transport_latency_assumed new_market c 605 396 67ms 6.9s 24.0s 1.2min 0 transport_latency_assumed new_market e 605 122 175ms 14.9s 35.0s 1.4min 0 transport_latency_assumed new_market f 605 148 214ms 21.9s 34.5s 1.1min 0 transport_latency_assumed new_market g 605 71 272ms 19.3s 35.1s 1.2min 0 transport_latency_assumed new_market h 605 173 108ms 19.6s 34.7s 1.2min 0 transport_latency_assumed price_change c 96,667,554 92,498,970 5ms 13ms 109ms 3.9s 0 transport_latency_assumed price_change e 96,658,160 307,112 42ms 55ms 389ms 10.8s 0 transport_latency_assumed price_change f 96,650,854 138,100 48ms 66ms 381ms 8.8s 0 transport_latency_assumed price_change g 96,419,410 25,250 78ms 107ms 772ms 19.4s 0 transport_latency_assumed price_change h 96,686,697 3,790,236 19ms 30ms 177ms 15.8s 0 transport_latency_assumed tick_size_change c 3,284 3,159 5ms 11ms 46ms 190ms 0 transport_latency_assumed tick_size_change e 3,284 not meas. 42ms 65ms 153ms 204ms 0 transport_latency_assumed tick_size_change f 3,284 not meas. 47ms 54ms 107ms 268ms 0 transport_latency_assumed tick_size_change g 3,284 not meas. 77ms 93ms 190ms 346ms 0 transport_latency_assumed tick_size_change h 3,284 125 19ms 29ms 131ms 359ms 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-17/11/2026-09-17T11.parquet sha256sum 2026-09-17T11.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.