Hour audit: 2026-09-15T11
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-15T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T11:00:00.000018762+00:00 · last event 2026-09-15T11:59:59.999946150+00:00
VOLUME 100,206,407 rows · 1,060,120,150 bytes (1011.01 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 99,790,839 · h: 99,778,937 · f: 99,763,939 · g: 99,729,283 · c: 96,161,637 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 396,904 (0.40%) · h: 7,902,964 (7.89%) · f: 146,609 (0.15%) · g: 31,303 (0.03%) · c: 91,728,627 (91.54%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,206,407 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f2fa19c049c3bc61f2c203c1dc20b138f83d6782b40725d08c19fb1f378918c4
the corpus checksum ledger names this file with the same digest
joined 100,208,621 to merged 100,206,407, minus 2,214 (minus 0.0022%)
boundary drops 2,214 · 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-15T12:56:21Z 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,416,318 115,839,010 0-39 ced8116780810a9a4ab2eb24d359aee41b00d704d6e825a7c496fe1878d3255e book 467,903 52,115,831 40-41 3adf9b89af2074be00b023c2d244d3d9c4f4872a73af25f8b324fa640e089494 last_trade_price 49,735 2,867,483 42-42 6e4fc051108dbf02197a1ddbfe9cee70ed5b7b43ac78074c2338962e7f8241f9 market_resolved 765 117,909 43-43 43d18189596da5c8ea3fc4d59253071d6e0c9a07ac31a7c4c396a71120fede9d new_market 1,212 121,498 44-44 5c9ff670007f2eaffffdb126ba1748bdc8728ff496acc2d82d2cd3e9ea4ec592 price_change 89,267,562 887,811,216 45-385 083c8dd1b391f059887e47cc88fa80c17b572ce928efddd171af63c8eb704b45 tick_size_change 2,912 105,435 386-386 d3c0550d37fd5cf09fd6e31b47bcb25f75745fb0aa20b080283d6cb29b3ffb6d EVENT MIX count share price_change 89,267,562 89.08% best_bid_ask 10,416,318 10.39% book 467,903 0.47% last_trade_price 49,735 0.05% tick_size_change 2,912 <0.01% new_market 1,212 <0.01% market_resolved 765 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,416,628 10,416,318 310 437 FULL book 467,929 467,903 26 170,215 FULL last_trade_price 49,735 49,735 0 58 FULL market_resolved 765 765 0 3 FULL new_market 1,212 1,212 0 0 FULL price_change 89,269,440 89,267,562 1,878 342 FULL tick_size_change 2,912 2,912 0 15 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,005,326 9,571,203 5ms 11ms 86ms 5.9s 0 transport_latency_assumed best_bid_ask e 10,414,740 35,317 39ms 45ms 174ms 15.5s 0 transport_latency_assumed best_bid_ask f 10,414,368 11,792 45ms 53ms 184ms 13.1s 0 transport_latency_assumed best_bid_ask g 10,413,931 1,576 80ms 100ms 336ms 19.3s 0 transport_latency_assumed best_bid_ask h 10,415,021 796,430 17ms 24ms 111ms 39.8s 0 transport_latency_assumed book c 450,831 441,258 3.8min 1.3d 34.7d 108.5d 0 book_staleness book e 106,176 3,222 41ms 254ms 18.7min 89.9d 0 book_staleness book f 108,400 3,941 47ms 296ms 3.1h 90.0d 0 book_staleness book g 117,529 9,592 91ms 34.5s 3.7d 90.0d 0 book_staleness book h 105,246 9,890 20ms 79ms 6.4min 44.7d 0 book_staleness last_trade_price c 47,929 45,066 11ms 50ms 246ms 5.0s 0 transport_latency_assumed last_trade_price e 49,574 346 46ms 171ms 2.5s 15.5s 0 transport_latency_assumed last_trade_price f 49,472 184 53ms 161ms 2.4s 13.1s 0 transport_latency_assumed last_trade_price g 49,606 27 97ms 369ms 7.5s 19.4s 0 transport_latency_assumed last_trade_price h 49,591 4,112 23ms 82ms 490ms 7.1s 0 transport_latency_assumed market_resolved c 742 719 5ms 19ms 5.2min 5.2min 0 transport_latency_assumed market_resolved e 726 1 39ms 126ms 425ms 842ms 0 transport_latency_assumed market_resolved f 726 not meas. 45ms 128ms 468ms 661ms 0 transport_latency_assumed market_resolved g 726 not meas. 82ms 241ms 630ms 1.3s 0 transport_latency_assumed market_resolved h 726 45 17ms 60ms 177ms 2.4s 0 transport_latency_assumed new_market c 763 497 76ms 25.5s 54.6s 1.0min 0 transport_latency_assumed new_market e 763 146 214ms 34.5s 54.2s 1.1min 0 transport_latency_assumed new_market f 763 142 206ms 26.6s 52.0s 57.1s 0 transport_latency_assumed new_market g 763 120 313ms 26.3s 48.0s 49.8s 0 transport_latency_assumed new_market h 763 307 129ms 23.7s 55.8s 1.1min 0 transport_latency_assumed price_change c 85,653,194 81,667,132 5ms 12ms 102ms 5.9s 0 transport_latency_assumed price_change e 89,215,948 357,872 39ms 51ms 323ms 15.5s 0 transport_latency_assumed price_change f 89,187,298 130,550 45ms 60ms 319ms 13.1s 0 transport_latency_assumed price_change g 89,143,816 19,988 81ms 108ms 634ms 19.4s 0 transport_latency_assumed price_change h 89,204,678 7,092,020 17ms 29ms 168ms 40.5s 0 transport_latency_assumed tick_size_change c 2,852 2,752 5ms 8ms 37ms 206ms 0 transport_latency_assumed tick_size_change e 2,912 not meas. 39ms 41ms 91ms 116ms 0 transport_latency_assumed tick_size_change f 2,912 not meas. 45ms 48ms 92ms 121ms 0 transport_latency_assumed tick_size_change g 2,912 not meas. 80ms 95ms 141ms 199ms 0 transport_latency_assumed tick_size_change h 2,912 160 17ms 21ms 41ms 140ms 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-15/11/2026-09-15T11.parquet sha256sum 2026-09-15T11.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.