Hour audit: 2026-09-16T03
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-16T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T03:00:00.000024515+00:00 · last event 2026-09-16T03:59:59.999969777+00:00
VOLUME 111,791,270 rows · 1,151,029,693 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,145,498 · e: 111,109,789 · f: 111,093,440 · h: 111,088,610 · g: 110,771,505 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,111,762 (95.81%) · e: 594,685 (0.53%) · f: 343,716 (0.31%) · h: 3,691,053 (3.30%) · g: 50,054 (0.04%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 111,791,270 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d087210a661773520746f4698f8882cffcd2b6737b5c05a73004636d434e61f7
the corpus checksum ledger names this file with the same digest
joined 111,794,312 to merged 111,791,270, minus 3,042 (minus 0.0027%)
boundary drops 3,042 · 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-16T05:02:06Z 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 12,334,818 135,991,971 0-47 ed3b7c1b2b9e48aebe81b7d9454ae575802a9c8728f1e75edf22a23168c9b6bd book 1,018,400 72,698,752 48-51 49fcdca68844d8a91b7e08bf473d0a93582e0d7f8871bc93f07458a0162896d6 last_trade_price 41,648 2,405,177 52-52 09cf50efc3783cf80631ca92bc0d70c70db08ac7dca4a45370523b52da3c1076 market_resolved 2,326 378,066 53-53 6a291d304116d4478c29337bcd87de12b9eafec7e7eb9dc1d831a5fc511ffb1f new_market 1,040 109,342 54-54 1ba0c8e955f7ff1bde5a7c76df7eb962f3d775bfeb26ca27101989feea6bd107 price_change 98,388,202 937,997,318 55-430 4882f7515b8e15ce83c1e0261fb21c946ee9078317fb8a832996133a312d64ad tick_size_change 4,836 175,208 431-431 7681b2b54b8458a747ee2cb451e79cc9fa98ce883f792605de3195ccab6d63da EVENT MIX count share price_change 98,388,202 88.01% best_bid_ask 12,334,818 11.03% book 1,018,400 0.91% last_trade_price 41,648 0.04% tick_size_change 4,836 <0.01% market_resolved 2,326 <0.01% new_market 1,040 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,335,114 12,334,818 296 99 FULL book 1,019,096 1,018,400 696 159,820 FULL last_trade_price 41,648 41,648 0 2 FULL market_resolved 2,326 2,326 0 0 FULL new_market 1,040 1,040 0 0 FULL price_change 98,390,252 98,388,202 2,050 40 FULL tick_size_change 4,836 4,836 0 15 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,332,623 11,945,933 4ms 8ms 68ms 2.7s 0 transport_latency_assumed best_bid_ask e 12,329,509 33,067 38ms 43ms 132ms 7.8s 0 transport_latency_assumed best_bid_ask f 12,330,122 10,117 46ms 55ms 156ms 5.2s 0 transport_latency_assumed best_bid_ask g 12,330,582 751 80ms 98ms 283ms 14.8s 0 transport_latency_assumed best_bid_ask h 12,330,011 344,950 18ms 24ms 99ms 7.0s 0 transport_latency_assumed book c 416,173 299,739 2.5min 18.1h 35.4d 109.2d 0 book_staleness book e 446,786 228,754 2.7min 17.2h 35.4d 109.2d 0 book_staleness book f 438,463 222,224 2.6min 18.7h 35.4d 109.2d 0 book_staleness book g 139,876 39,828 114ms 24.0min 21.4d 90.7d 0 book_staleness book h 424,692 227,855 2.4min 13.3h 35.3d 109.2d 0 book_staleness last_trade_price c 41,524 38,933 10ms 49ms 234ms 5.0s 0 transport_latency_assumed last_trade_price e 41,412 357 45ms 109ms 705ms 7.8s 0 transport_latency_assumed last_trade_price f 41,483 149 53ms 126ms 649ms 5.3s 0 transport_latency_assumed last_trade_price g 41,390 28 93ms 215ms 3.2s 14.9s 0 transport_latency_assumed last_trade_price h 41,287 2,181 24ms 72ms 264ms 5.3s 0 transport_latency_assumed market_resolved c 2,300 2,253 5ms 9ms 45.9s 1.0min 0 transport_latency_assumed market_resolved e 2,300 4 86ms 118ms 259ms 605ms 0 transport_latency_assumed market_resolved f 2,300 4 101ms 130ms 323ms 1.5s 0 transport_latency_assumed market_resolved g 2,300 not meas. 155ms 248ms 444ms 1.1s 0 transport_latency_assumed market_resolved h 2,300 65 33ms 56ms 117ms 3.6s 0 transport_latency_assumed new_market c 710 461 67ms 27.2s 1.5min 4.1d 0 transport_latency_assumed new_market e 710 93 158ms 21.3s 1.6min 4.1d 0 transport_latency_assumed new_market f 710 128 160ms 21.7s 1.6min 4.1d 0 transport_latency_assumed new_market g 710 73 262ms 23.8s 1.7min 4.1d 0 transport_latency_assumed new_market h 710 285 79ms 18.6s 1.5min 7.0min 0 transport_latency_assumed price_change c 98,347,332 94,819,774 5ms 10ms 81ms 2.7s 0 transport_latency_assumed price_change e 98,284,236 332,410 38ms 47ms 195ms 7.8s 0 transport_latency_assumed price_change f 98,275,526 111,094 46ms 60ms 213ms 5.3s 0 transport_latency_assumed price_change g 98,251,815 9,374 81ms 108ms 379ms 14.9s 0 transport_latency_assumed price_change h 98,284,830 3,115,550 18ms 28ms 120ms 7.5s 0 transport_latency_assumed tick_size_change c 4,836 4,669 4ms 9ms 37ms 193ms 0 transport_latency_assumed tick_size_change e 4,836 not meas. 38ms 56ms 138ms 351ms 0 transport_latency_assumed tick_size_change f 4,836 not meas. 46ms 86ms 179ms 1.3s 0 transport_latency_assumed tick_size_change g 4,832 not meas. 81ms 165ms 490ms 2.2s 0 transport_latency_assumed tick_size_change h 4,780 167 18ms 21ms 105ms 522ms 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/03/2026-09-16T03.parquet sha256sum 2026-09-16T03.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.