Hour audit: 2026-09-16T10
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-16T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T10:00:00.000015827+00:00 · last event 2026-09-16T10:59:59.999934782+00:00
VOLUME 113,558,855 rows · 1,163,678,467 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 113,334,170 · e: 113,288,413 · h: 113,285,258 · g: 113,254,318 · f: 113,222,687 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 109,117,275 (96.09%) · e: 472,943 (0.42%) · h: 3,570,925 (3.14%) · g: 183,735 (0.16%) · f: 213,977 (0.19%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 113,558,855 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4309b470ead3c632e148145eb27e28e8437542aeb3bf2869f40bbaabb973e532
the corpus checksum ledger names this file with the same digest
joined 113,560,963 to merged 113,558,855, minus 2,108 (minus 0.0019%)
boundary drops 2,108 · 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-16T11:59: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 11,389,964 130,514,124 0-43 f2a95567df8a60fa6908f98d9b1faa59f4138d44a0f832a16d0306d825a4687c book 317,658 32,653,422 44-45 606c0c4fcff02873eabf412d9f23b74e14674dc7c099246232e408b646e8be0e last_trade_price 45,409 2,600,743 46-46 77584916ae4cdacecc74fcf706bca6367b8ca1d51c5b9dc4da271c980287ccd4 market_resolved 849 133,812 47-47 b9f47517ec33e7b0a80c6f6b3f2dcef15fbb9992e8790831639d69b3bccf81fd new_market 1,673 181,725 48-48 96cf45b0a0e18908a5c75966e45949665a847778865e3d1b3cf29c0a5680a241 price_change 101,800,078 996,181,398 49-437 e819b8fa5382997e6d0381a143d15d1cb24eb270f218350947ebd806ae7142fc tick_size_change 3,224 118,597 438-438 e5e5ab6ce55b59643eba4efe4351135287f98dd5b5f82d195f81fe2b82048f19 EVENT MIX count share price_change 101,800,078 89.65% best_bid_ask 11,389,964 10.03% book 317,658 0.28% last_trade_price 45,409 0.04% tick_size_change 3,224 <0.01% new_market 1,673 <0.01% market_resolved 849 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,390,212 11,389,964 248 339 FULL book 317,704 317,658 46 88,874 FULL last_trade_price 45,409 45,409 0 1 FULL market_resolved 849 849 0 0 FULL new_market 1,673 1,673 0 0 FULL price_change 101,801,892 101,800,078 1,814 70 FULL tick_size_change 3,224 3,224 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,388,567 10,992,236 5ms 10ms 103ms 4.1s 0 transport_latency_assumed best_bid_ask e 11,386,231 42,227 39ms 46ms 201ms 13.6s 0 transport_latency_assumed best_bid_ask f 11,385,904 16,804 45ms 55ms 231ms 9.4s 0 transport_latency_assumed best_bid_ask g 11,382,121 1,532 79ms 99ms 466ms 28.5s 0 transport_latency_assumed best_bid_ask h 11,386,776 337,165 18ms 32ms 195ms 51.1s 0 transport_latency_assumed book c 110,370 104,270 7ms 51.2s 7.1d 91.0d 0 book_staleness book e 115,009 18,188 43ms 2.5min 9.0d 109.5d 0 book_staleness book f 114,890 18,259 49ms 3.2min 9.0d 91.0d 0 book_staleness book g 263,162 165,062 41.5s 3.3h 24.9d 109.5d 0 book_staleness book h 103,296 11,879 23ms 463ms 12.6h 91.0d 0 book_staleness last_trade_price c 45,329 43,307 11ms 52ms 248ms 5.0s 0 transport_latency_assumed last_trade_price e 45,155 277 49ms 206ms 3.8s 13.7s 0 transport_latency_assumed last_trade_price f 45,009 174 55ms 198ms 2.4s 9.4s 0 transport_latency_assumed last_trade_price g 44,851 21 97ms 531ms 6.8s 26.4s 0 transport_latency_assumed last_trade_price h 45,070 1,630 25ms 110ms 553ms 21.2s 0 transport_latency_assumed market_resolved c 821 775 5ms 15ms 46.3s 1.0min 0 transport_latency_assumed market_resolved e 821 31 41ms 189ms 59.8s 1.0min 0 transport_latency_assumed market_resolved f 821 4 46ms 196ms 59.8s 1.0min 0 transport_latency_assumed market_resolved g 821 12 82ms 255ms 1.0s 2.9s 0 transport_latency_assumed market_resolved h 821 27 19ms 82ms 44.1s 50.9s 0 transport_latency_assumed new_market c 1,205 720 89ms 17.8s 25.1s 27.4s 0 transport_latency_assumed new_market e 1,205 196 202ms 647ms 21.9s 55.1s 0 transport_latency_assumed new_market f 1,205 272 173ms 17.6s 26.0s 54.3s 0 transport_latency_assumed new_market g 1,205 98 289ms 16.0s 26.5s 2.3min 0 transport_latency_assumed new_market h 1,205 387 144ms 15.8s 25.1s 26.9s 0 transport_latency_assumed price_change c 101,784,654 97,972,874 5ms 11ms 122ms 4.4s 0 transport_latency_assumed price_change e 101,736,768 412,008 40ms 53ms 381ms 13.7s 0 transport_latency_assumed price_change f 101,671,634 178,460 45ms 64ms 386ms 9.5s 0 transport_latency_assumed price_change g 101,558,934 17,010 80ms 119ms 976ms 28.6s 0 transport_latency_assumed price_change h 101,744,866 3,219,726 18ms 37ms 254ms 51.1s 0 transport_latency_assumed tick_size_change c 3,224 3,093 5ms 14ms 147ms 266ms 0 transport_latency_assumed tick_size_change e 3,224 16 40ms 52ms 292ms 488ms 0 transport_latency_assumed tick_size_change f 3,224 4 46ms 104ms 322ms 1.6s 0 transport_latency_assumed tick_size_change g 3,224 not meas. 80ms 107ms 516ms 9.5s 0 transport_latency_assumed tick_size_change h 3,224 111 19ms 45ms 338ms 1.1s 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-16/10/2026-09-16T10.parquet sha256sum 2026-09-16T10.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.