Hour audit: 2026-09-10T19
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-10T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T19:00:00.000100820+00:00 · last event 2026-09-10T19:59:59.999957722+00:00
VOLUME 114,042,783 rows · 1,264,228,563 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 111,847,530 · h: 111,841,509 · g: 107,253,347 · f: 102,717,900 · c: 89,584,248 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 3,943,490 (3.46%) · h: 27,456,298 (24.08%) · g: 168,006 (0.15%) · f: 1,064,837 (0.93%) · c: 81,410,152 (71.39%) (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 114,042,783 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c94ff42f7f7c081684761eaded5d4e8bd51d32be3d220ffd0c1c75a5060e6960
the corpus checksum ledger names this file with the same digest
joined 114,047,124 to merged 114,042,783, minus 4,341 (minus 0.0038%)
boundary drops 4,341 · 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-10T21:35:40Z 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,751,724 125,656,692 0-41 f40af0a56666953f2c563acb067b23e1d64962b4644f994c6ac67dc603cf9081 book 2,218,156 96,630,673 42-50 0a0e160d3ddf9878a864e09658a9ba70e2f36a7fa8c1fe9f6539d0b0e4d7a880 last_trade_price 59,139 3,413,594 51-51 fefed423a7b1384156f47878bab5fe965cd1abc6b78cffe70cc56773240d286b market_resolved 1,399 212,413 52-52 269926e3167ae7d5fd012e72c3c4b8876bcb3b539d2fb7634255517e45e92499 new_market 10,922 988,661 53-53 7c391e9967822cf4d9622711c4ac8841fb4131cc4f6b609e1b5ce994f39486ed price_change 100,998,567 1,035,918,427 54-439 4ec4121864f982659ff193c5cbebabf7ad59788067ad2b41933b75e6c74a9c51 tick_size_change 2,876 107,194 440-440 2ec719e87f6515e4fbcee7c9410d241b51c9ed58efc9dc073cba15cc2ea67334 EVENT MIX count share price_change 100,998,567 88.56% best_bid_ask 10,751,724 9.43% book 2,218,156 1.95% last_trade_price 59,139 0.05% new_market 10,922 <0.01% tick_size_change 2,876 <0.01% market_resolved 1,399 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,751,972 10,751,724 248 3,514 FULL book 2,218,313 2,218,156 157 195,403 FULL last_trade_price 59,141 59,139 2 443 FULL market_resolved 1,399 1,399 0 71 FULL new_market 10,924 10,922 2 76 FULL price_change 101,002,499 100,998,567 3,932 2,712 FULL tick_size_change 2,876 2,876 0 165 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,382,044 7,609,699 6ms 28ms 252ms 9.7s 0 transport_latency_assumed best_bid_ask e 10,748,018 404,134 38ms 88ms 418ms 19.8s 0 transport_latency_assumed best_bid_ask f 9,768,461 85,990 44ms 91ms 402ms 18.4s 0 transport_latency_assumed best_bid_ask g 10,261,724 10,232 87ms 233ms 1.1s 51.0s 0 transport_latency_assumed best_bid_ask h 10,749,347 2,641,669 19ms 59ms 838ms 55.1s 0 transport_latency_assumed book c 2,063,338 1,934,645 31.8min 1.3d 30.0d 103.9d 0 book_staleness book e 137,146 9,223 56ms 2.3s 26.1min 103.9d 0 book_staleness book f 925,997 183,116 12.0min 1.1d 30.0d 103.9d 0 book_staleness book g 543,346 56,916 5.1min 19.7h 26.4d 103.9d 0 book_staleness book h 136,076 34,256 28ms 770ms 15.4s 85.2d 0 book_staleness last_trade_price c 46,558 42,095 13ms 80ms 782ms 5.0s 0 transport_latency_assumed last_trade_price e 59,058 1,538 74ms 613ms 5.8s 19.8s 0 transport_latency_assumed last_trade_price f 53,427 439 79ms 502ms 5.7s 18.4s 0 transport_latency_assumed last_trade_price g 55,612 57 150ms 2.9s 16.1s 55.1s 0 transport_latency_assumed last_trade_price h 59,023 15,010 29ms 155ms 2.1s 12.0s 0 transport_latency_assumed market_resolved c 1,163 1,059 7ms 6.4min 12.2min 13.0min 0 transport_latency_assumed market_resolved e 1,162 24 40ms 191ms 724ms 1.1s 0 transport_latency_assumed market_resolved f 1,255 76 47ms 4.0min 9.0min 9.7min 0 transport_latency_assumed market_resolved g 1,169 26 88ms 552ms 4.9min 5.7min 0 transport_latency_assumed market_resolved h 1,162 214 20ms 87ms 500ms 7.3s 0 transport_latency_assumed new_market c 8,174 5,095 114ms 6.8min 10.5min 329.9d 0 transport_latency_assumed new_market e 6,195 1,457 162ms 53.1s 2.9min 329.9d 0 transport_latency_assumed new_market f 7,433 949 225ms 5.5min 7.4min 8.6min 0 transport_latency_assumed new_market g 6,627 995 319ms 2.9min 6.9min 329.9d 0 transport_latency_assumed new_market h 6,196 2,426 123ms 1.2min 2.9min 329.9d 0 transport_latency_assumed price_change c 79,080,707 71,815,509 6ms 30ms 261ms 9.7s 0 transport_latency_assumed price_change e 100,893,075 3,527,008 39ms 118ms 752ms 19.8s 0 transport_latency_assumed price_change f 91,958,627 794,226 45ms 118ms 665ms 18.4s 0 transport_latency_assumed price_change g 96,382,077 99,780 88ms 320ms 5.5s 51.3s 0 transport_latency_assumed price_change h 100,886,829 24,762,044 19ms 64ms 811ms 55.1s 0 transport_latency_assumed tick_size_change c 2,264 2,050 7ms 26ms 196ms 360ms 0 transport_latency_assumed tick_size_change e 2,876 106 38ms 75ms 289ms 569ms 0 transport_latency_assumed tick_size_change f 2,700 41 44ms 80ms 300ms 412ms 0 transport_latency_assumed tick_size_change g 2,792 not meas. 82ms 190ms 591ms 3.9s 0 transport_latency_assumed tick_size_change h 2,876 679 18ms 54ms 664ms 4.2s 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-10/19/2026-09-10T19.parquet sha256sum 2026-09-10T19.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.