Hour audit: 2026-09-14T17
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-14T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T17:00:00.000037601+00:00 · last event 2026-09-14T17:59:59.999443058+00:00
VOLUME 119,748,246 rows · 1,290,511,807 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,098,721 · h: 118,097,672 · f: 113,996,224 · g: 113,694,312 · c: 102,094,576 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 939,094 (0.78%) · h: 21,165,398 (17.67%) · f: 522,174 (0.44%) · g: 197,429 (0.16%) · c: 96,924,151 (80.94%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 621a9f2a5c9fb4d2ab45c8dc63f4a0d751589c2d9182b3d3e2e53af092eef93a
the corpus checksum ledger names this file with the same digest
joined 119,750,793 to merged 119,748,246, minus 2,547 (minus 0.0021%)
boundary drops 2,547 · 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-14T19:00:22Z 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,201,392 126,983,066 0-42 69869c345b59d4b45d1d57f6f843bc62e39730cdb11b0df19ee0a469ef72703e book 1,657,869 84,324,613 43-49 5fb326bb9ea3c83e4ebb471774ff57de065d1d5606f801c550221ed4712c93b4 last_trade_price 59,715 3,493,959 50-50 8d1a612923b140001ebd2cebbddf09e690432b81c060857e3f929861920e449d market_resolved 729 98,543 51-51 1c3d63b5d84b73457b4fa317213b73bd4f210e40bfc9268e9924776be9ad2aea new_market 1,498 154,431 52-52 9ffb99cf20e5e792d24a9154543ae57cf0b37f0ff6ef541e1cfc2413b46b0277 price_change 106,821,595 1,073,893,556 53-460 a6d5948f830b8a0f909b91423a96d2ea1fda09f2529445ef3b5912c240c71e29 tick_size_change 5,448 200,666 461-461 232dfcbf8fe0092141a1a38af4cbc11b4030dd4ff7181eca0a67c9b9b2d5ad0e EVENT MIX count share price_change 106,821,595 89.21% best_bid_ask 11,201,392 9.35% book 1,657,869 1.38% last_trade_price 59,715 0.05% tick_size_change 5,448 <0.01% new_market 1,498 <0.01% market_resolved 729 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,201,558 11,201,392 166 1,669 FULL book 1,657,939 1,657,869 70 166,587 FULL last_trade_price 59,716 59,715 1 448 FULL market_resolved 729 729 0 17 FULL new_market 1,498 1,498 0 5 FULL price_change 106,823,905 106,821,595 2,310 1,169 FULL tick_size_change 5,448 5,448 0 162 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,548,593 9,075,759 5ms 14ms 119ms 2.1s 0 transport_latency_assumed best_bid_ask e 11,198,634 86,358 45ms 63ms 245ms 15.9s 0 transport_latency_assumed best_bid_ask f 10,770,179 44,124 48ms 66ms 269ms 11.5s 0 transport_latency_assumed best_bid_ask g 10,761,302 2,504 83ms 114ms 484ms 33.7s 0 transport_latency_assumed best_bid_ask h 11,198,850 1,992,647 18ms 32ms 160ms 35.0s 0 transport_latency_assumed book c 1,471,386 1,449,464 22.5min 3.0d 37.1d 107.8d 0 book_staleness book e 129,247 5,363 53ms 842ms 8.0h 89.2d 0 book_staleness book f 465,197 36,892 3.6min 1.4d 33.1d 107.8d 0 book_staleness book g 483,303 138,867 4.2min 1.5d 33.7d 107.8d 0 book_staleness book h 129,504 27,283 23ms 157ms 5.3h 89.3d 0 book_staleness last_trade_price c 49,734 47,002 11ms 55ms 285ms 5.0s 0 transport_latency_assumed last_trade_price e 59,428 530 63ms 361ms 4.9s 11.2s 0 transport_latency_assumed last_trade_price f 56,943 376 65ms 418ms 4.8s 9.1s 0 transport_latency_assumed last_trade_price g 55,957 227 103ms 544ms 8.5s 18.5s 0 transport_latency_assumed last_trade_price h 59,426 11,580 26ms 104ms 541ms 11.4s 0 transport_latency_assumed market_resolved c 619 598 6ms 4.6min 10.4min 10.4min 0 transport_latency_assumed market_resolved e 596 15 48ms 216ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 595 6 49ms 213ms 2.9min 4.4min 0 transport_latency_assumed market_resolved g 595 11 88ms 366ms 2.7min 4.3min 0 transport_latency_assumed market_resolved h 596 99 19ms 90ms 49.7s 1.0min 0 transport_latency_assumed new_market c 1,015 678 132ms 25.6s 6.1min 26.0min 0 transport_latency_assumed new_market e 978 239 225ms 26.7s 1.0min 1.1min 0 transport_latency_assumed new_market f 978 124 230ms 17.3s 1.1min 4.4min 0 transport_latency_assumed new_market g 978 92 389ms 17.0s 1.1min 4.2min 0 transport_latency_assumed new_market h 978 365 142ms 18.2s 1.0min 1.3min 0 transport_latency_assumed price_change c 91,018,345 86,346,022 5ms 16ms 129ms 3.2s 0 transport_latency_assumed price_change e 106,704,390 846,578 46ms 75ms 684ms 16.1s 0 transport_latency_assumed price_change f 102,696,968 440,648 49ms 80ms 662ms 11.5s 0 transport_latency_assumed price_change g 102,386,801 55,724 84ms 141ms 1.3s 33.7s 0 transport_latency_assumed price_change h 106,702,870 19,132,623 19ms 37ms 215ms 36.9s 0 transport_latency_assumed tick_size_change c 4,884 4,628 5ms 13ms 121ms 248ms 0 transport_latency_assumed tick_size_change e 5,448 11 43ms 60ms 244ms 504ms 0 transport_latency_assumed tick_size_change f 5,364 4 49ms 71ms 182ms 390ms 0 transport_latency_assumed tick_size_change g 5,376 4 83ms 112ms 406ms 1.4s 0 transport_latency_assumed tick_size_change h 5,448 801 18ms 29ms 109ms 547ms 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-14/17/2026-09-14T17.parquet sha256sum 2026-09-14T17.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.