Hour audit: 2026-09-16T11
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-16T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T11:00:00.000363634+00:00 · last event 2026-09-16T11:59:59.999979839+00:00
VOLUME 115,908,523 rows · 1,220,251,818 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 115,432,608 · h: 115,381,182 · f: 115,329,577 · e: 115,309,109 · g: 111,031,611 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 110,011,637 (94.91%) · h: 4,719,959 (4.07%) · f: 246,965 (0.21%) · e: 566,190 (0.49%) · g: 363,772 (0.31%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 115,908,523 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8e827da9c4fcaff863a98fab09bd4ba3d9b6a89993ba262648722ddce0d14825
the corpus checksum ledger names this file with the same digest
joined 115,913,064 to merged 115,908,523, minus 4,541 (minus 0.0039%)
boundary drops 4,541 · 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-16T12:59:50Z 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,006,107 139,223,292 0-45 6467574b358fcaf05d92b8d70eee8f7b524abb7ab2a2283f7511b3de1cbccc11 book 560,620 55,538,407 46-48 af0202698a35125dfcb10c3b03bcd53fb4ce5686b47f641a040eaac6f5d0dd6a last_trade_price 52,452 3,020,636 49-49 af17fecbadbcbd430b132049908baf480681475683310a39f76c8721332ddf75 market_resolved 951 140,042 50-50 c1651d5ebd3ae0c0c67bb92d84b799928d761e82a956b289c3a0f12705327007 new_market 2,045 205,692 51-51 1b28b5764a66589ff95b998db3c9d9ed2a30bcce72f4aa78e1b5301485c6d8fb price_change 103,283,476 1,020,701,553 52-445 a6a1c6a60ecccc0ed6b62265724aa253c86e12c64dc36745781c095298384745 tick_size_change 2,872 104,218 446-446 522d9e8d50e44e8704a3c3d035838e6a9052bcaf1f93dd3da2b8f2fddc0e57f7 EVENT MIX count share price_change 103,283,476 89.11% best_bid_ask 12,006,107 10.36% book 560,620 0.48% last_trade_price 52,452 0.05% tick_size_change 2,872 <0.01% new_market 2,045 <0.01% market_resolved 951 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,006,428 12,006,107 321 1,793 FULL book 561,036 560,620 416 171,297 FULL last_trade_price 52,456 52,452 4 41 FULL market_resolved 951 951 0 5 FULL new_market 2,045 2,045 0 0 FULL price_change 103,287,276 103,283,476 3,800 1,238 FULL tick_size_change 2,872 2,872 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,003,817 11,485,250 5ms 12ms 132ms 4.8s 0 transport_latency_assumed best_bid_ask e 12,000,492 48,970 40ms 50ms 235ms 17.1s 0 transport_latency_assumed best_bid_ask f 12,001,331 19,906 45ms 59ms 277ms 16.7s 0 transport_latency_assumed best_bid_ask g 11,517,581 1,917 80ms 104ms 569ms 33.0s 0 transport_latency_assumed best_bid_ask h 12,002,838 450,064 19ms 31ms 202ms 36.0s 0 transport_latency_assumed book c 147,383 133,725 8ms 11.4min 10.9d 109.5d 0 book_staleness book e 141,826 29,897 47ms 8.9min 10.9d 109.5d 0 book_staleness book f 139,867 27,158 54ms 8.0min 9.0d 109.5d 0 book_staleness book g 476,331 336,560 1.4min 16.2h 34.9d 109.5d 0 book_staleness book h 142,496 33,280 27ms 8.0min 9.0d 109.5d 0 book_staleness last_trade_price c 52,194 49,185 11ms 53ms 277ms 5.0s 0 transport_latency_assumed last_trade_price e 51,737 380 51ms 239ms 4.5s 16.4s 0 transport_latency_assumed last_trade_price f 51,963 211 59ms 278ms 5.1s 16.8s 0 transport_latency_assumed last_trade_price g 49,644 36 98ms 705ms 10.3s 27.5s 0 transport_latency_assumed last_trade_price h 52,175 2,640 27ms 108ms 654ms 13.7s 0 transport_latency_assumed market_resolved c 857 754 5ms 154ms 53.3s 57.7s 0 transport_latency_assumed market_resolved e 857 70 41ms 442ms 52.4s 57.7s 0 transport_latency_assumed market_resolved f 857 4 46ms 420ms 52.4s 57.7s 0 transport_latency_assumed market_resolved g 862 95 84ms 332ms 4.5min 4.9min 0 transport_latency_assumed market_resolved h 856 28 20ms 162ms 56.5s 1.0min 0 transport_latency_assumed new_market c 1,335 836 100ms 20.3s 28.4s 1.6min 0 transport_latency_assumed new_market e 1,335 187 220ms 19.6s 26.5s 40.4s 0 transport_latency_assumed new_market f 1,335 280 179ms 15.9s 24.9s 1.1min 0 transport_latency_assumed new_market g 1,335 202 373ms 19.5s 30.8s 4.4min 0 transport_latency_assumed new_market h 1,335 540 130ms 18.8s 26.5s 2.5min 0 transport_latency_assumed price_change c 103,224,150 98,339,082 5ms 14ms 158ms 5.3s 0 transport_latency_assumed price_change e 103,109,990 486,686 40ms 62ms 513ms 17.1s 0 transport_latency_assumed price_change f 103,131,352 199,406 46ms 73ms 580ms 16.8s 0 transport_latency_assumed price_change g 98,983,022 24,962 81ms 137ms 1.9s 35.1s 0 transport_latency_assumed price_change h 103,178,610 4,233,340 20ms 37ms 285ms 37.7s 0 transport_latency_assumed tick_size_change c 2,872 2,805 5ms 10ms 66ms 252ms 0 transport_latency_assumed tick_size_change e 2,872 not meas. 40ms 47ms 185ms 603ms 0 transport_latency_assumed tick_size_change f 2,872 not meas. 46ms 79ms 187ms 301ms 0 transport_latency_assumed tick_size_change g 2,836 not meas. 80ms 97ms 262ms 812ms 0 transport_latency_assumed tick_size_change h 2,872 67 20ms 33ms 99ms 949ms 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/11/2026-09-16T11.parquet sha256sum 2026-09-16T11.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.