Hour audit: 2026-09-19T07
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-19T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T07:00:00.000464434+00:00 · last event 2026-09-19T07:59:59.999984338+00:00
VOLUME 111,425,071 rows · 1,104,157,524 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,384,676 · e: 111,379,505 · h: 111,356,048 · f: 111,348,821 · g: 111,281,867 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,859,081 (96.80%) · e: 225,202 (0.20%) · h: 3,217,139 (2.89%) · f: 99,969 (0.09%) · g: 23,680 (0.02%) (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 111,425,071 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d81fffb1b6681f603818155877395cd769605def30b8ed26a3ec9e18459b38a1
the corpus checksum ledger names this file with the same digest
joined 111,427,930 to merged 111,425,071, minus 2,859 (minus 0.0026%)
boundary drops 2,859 · 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-19T08:59:10Z 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,475,752 130,560,418 0-43 6f0ab4dc213dd0210636cce31b4a1a679ad37ca8ced962b547565a6a7d99d91a book 102,357 10,973,467 44-44 092f15999a296549fe4340913e6f4bd77e300b3d36eb91a3a7d14bf04e2baf6c last_trade_price 42,768 2,556,309 45-45 98c41cc847d4a631d87d63cda091d3232e9556d16c7d09b28119982539f5b046 market_resolved 551 88,216 46-46 c1c208852a130c1dcb81f1e0dd288f3087eeb63e3ed29589e5dc4d3b78cce2d9 new_market 702 77,650 47-47 4b5e1a5f79bdcff1096c972113ca14f34b7c22dfb1e0398e37bad31f05606fbe price_change 99,800,497 958,542,563 48-428 7b4d1b4cd5d569452be9cf6edf9e3e3a63bab120bebc4e6b6a9559548fd02606 tick_size_change 2,444 90,546 429-429 9f7a2b03c72f19536268af1d700bc0a200a7ba28115d1603e9dd48ef45ab0004 EVENT MIX count share price_change 99,800,497 89.57% best_bid_ask 11,475,752 10.30% book 102,357 0.09% last_trade_price 42,768 0.04% tick_size_change 2,444 <0.01% new_market 702 <0.01% market_resolved 551 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,476,040 11,475,752 288 107 FULL book 102,361 102,357 4 4,370 FULL last_trade_price 42,771 42,768 3 1 FULL market_resolved 551 551 0 0 FULL new_market 702 702 0 0 FULL price_change 99,803,061 99,800,497 2,564 141 FULL tick_size_change 2,444 2,444 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,475,290 11,134,095 4ms 8ms 65ms 6.0s 0 transport_latency_assumed best_bid_ask e 11,474,400 21,399 43ms 48ms 132ms 5.3s 0 transport_latency_assumed best_bid_ask f 11,474,147 7,928 48ms 54ms 155ms 4.7s 0 transport_latency_assumed best_bid_ask g 11,473,427 1,515 77ms 90ms 236ms 11.5s 0 transport_latency_assumed best_bid_ask h 11,474,097 310,815 17ms 22ms 88ms 23.8s 0 transport_latency_assumed book c 90,838 86,005 6ms 27ms 14.4min 93.9d 0 book_staleness book e 89,799 1,664 45ms 144ms 57.5s 93.9d 0 book_staleness book f 91,433 3,121 50ms 213ms 17.1min 93.8d 0 book_staleness book g 93,546 4,120 81ms 459ms 34.1min 93.9d 0 book_staleness book h 91,622 7,447 21ms 71ms 17.3min 93.8d 0 book_staleness last_trade_price c 42,645 40,631 9ms 43ms 294ms 5.0s 0 transport_latency_assumed last_trade_price e 42,697 205 50ms 139ms 1.8s 5.3s 0 transport_latency_assumed last_trade_price f 42,656 90 55ms 156ms 2.1s 5.0s 0 transport_latency_assumed last_trade_price g 42,527 56 89ms 216ms 5.0s 11.5s 0 transport_latency_assumed last_trade_price h 42,460 1,786 23ms 65ms 378ms 10.4s 0 transport_latency_assumed market_resolved c 546 536 5ms 10ms 43ms 139ms 0 transport_latency_assumed market_resolved e 546 1 45ms 189ms 602ms 1.0min 0 transport_latency_assumed market_resolved f 546 1 49ms 194ms 575ms 59.8s 0 transport_latency_assumed market_resolved g 546 not meas. 80ms 250ms 609ms 1.1s 0 transport_latency_assumed market_resolved h 546 13 18ms 59ms 262ms 1.0min 0 transport_latency_assumed new_market c 502 349 69ms 12.4s 22.4s 1.1min 0 transport_latency_assumed new_market e 502 97 160ms 14.3s 23.5s 1.3min 0 transport_latency_assumed new_market f 502 76 173ms 12.5s 24.2s 59.3s 0 transport_latency_assumed new_market g 502 41 247ms 12.4s 22.2s 1.1min 0 transport_latency_assumed new_market h 502 139 114ms 12.5s 23.5s 29.8s 0 transport_latency_assumed price_change c 99,772,411 96,595,092 5ms 9ms 76ms 6.1s 0 transport_latency_assumed price_change e 99,769,117 201,832 43ms 50ms 247ms 5.7s 0 transport_latency_assumed price_change f 99,737,093 88,750 48ms 57ms 278ms 4.8s 0 transport_latency_assumed price_change g 99,668,875 17,948 77ms 93ms 410ms 11.5s 0 transport_latency_assumed price_change h 99,744,377 2,896,875 18ms 24ms 128ms 23.8s 0 transport_latency_assumed tick_size_change c 2,444 2,373 5ms 8ms 50ms 143ms 0 transport_latency_assumed tick_size_change e 2,444 4 43ms 49ms 180ms 233ms 0 transport_latency_assumed tick_size_change f 2,444 3 48ms 57ms 187ms 396ms 0 transport_latency_assumed tick_size_change g 2,444 not meas. 77ms 90ms 214ms 371ms 0 transport_latency_assumed tick_size_change h 2,444 64 18ms 26ms 83ms 277ms 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-19/07/2026-09-19T07.parquet sha256sum 2026-09-19T07.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.