Hour audit: 2026-09-06T06
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-06T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T06:00:00.061927099+00:00 · last event 2026-09-06T06:59:59.999994842+00:00
VOLUME 89,897,000 rows · 878,800,351 bytes (838.09 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 89,716,211 · f: 89,714,397 · g: 89,714,279 · c: 89,652,221 · e: 89,396,065 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 35,584 (0.04%) · f: 49,718 (0.06%) · g: 89,712,097 (99.79%) · c: 56,067 (0.06%) · e: 43,534 (0.05%) (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 89,897,000 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a550d114a7ef0ab04c00793ec4dd2b6114979a706638fa7522e0fd01eccd1c4f
the corpus checksum ledger names this file with the same digest
joined 89,899,212 to merged 89,897,000, minus 2,212 (minus 0.0025%)
boundary drops 2,212 · 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-06T09:37: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 11,027,666 114,477,744 0-42 ca345e524269f6923e1b068013f7f50530df30d8efb3c32e22ad638816da8842 book 290,233 28,912,091 43-44 c408c3028dbec8c3d5cbf3e467dcb979d65833254a464ab79e8000c28184ac10 last_trade_price 50,390 2,847,201 45-45 1261e27e578339f2a0e54a01510e532a2cb21e53afe82c1595affe49c21358d4 market_resolved 1,441 218,872 46-46 49660bae15a48e3e9a9c62e44b20f795a492449743fe1b3e75f2f62ecd445d14 new_market 1,922 197,954 47-47 58d3496e7cc3f4e919f1c5fe56427c8fa978bf58c6b83b5007d0167d82e52dfb price_change 78,523,012 731,031,813 48-347 db2f7fa9e40d257b8bc11aed80c72342ef6b74f7f8f7edf51ff3ef9c3378686a tick_size_change 2,336 86,231 348-348 c5c13e85feb250441babd753a8aabbf73288e8d8e53f6caae55a12d7d380c16f EVENT MIX count share price_change 78,523,012 87.35% best_bid_ask 11,027,666 12.27% book 290,233 0.32% last_trade_price 50,390 0.06% tick_size_change 2,336 <0.01% new_market 1,922 <0.01% market_resolved 1,441 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,027,948 11,027,666 282 293 FULL book 290,269 290,233 36 79,348 FULL last_trade_price 50,390 50,390 0 0 FULL market_resolved 1,441 1,441 0 0 FULL new_market 1,922 1,922 0 0 FULL price_change 78,524,906 78,523,012 1,894 366 FULL tick_size_change 2,336 2,336 0 8 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,019,315 646 4ms 7ms 83ms 3.8s 0 transport_latency_assumed best_bid_ask e 11,014,472 332 38ms 42ms 160ms 15.9s 0 transport_latency_assumed best_bid_ask f 11,025,665 1,520 47ms 52ms 180ms 4.0s 0 transport_latency_assumed best_bid_ask g 11,024,879 11,024,597 79ms 93ms 360ms 10.0s 0 transport_latency_assumed best_bid_ask h 11,026,042 571 17ms 21ms 174ms 44.9s 0 transport_latency_assumed book c 170,898 49,209 8ms 6.0h 14.7d 99.3d 0 book_staleness book e 143,703 35,556 42ms 1.4h 14.7d 80.8d 0 book_staleness book f 135,855 27,975 51ms 23.4min 14.7d 99.3d 0 book_staleness book g 147,887 147,881 89ms 1.6h 14.7d 91.6d 0 book_staleness book h 140,667 29,612 22ms 35.3min 14.7d 99.4d 0 book_staleness last_trade_price c 49,752 3 9ms 36ms 211ms 5.0s 0 transport_latency_assumed last_trade_price e 49,395 8 44ms 86ms 5.0s 15.9s 0 transport_latency_assumed last_trade_price f 50,356 20 53ms 94ms 766ms 5.0s 0 transport_latency_assumed last_trade_price g 50,356 50,356 89ms 157ms 3.7s 10.1s 0 transport_latency_assumed last_trade_price h 50,331 3 22ms 54ms 325ms 41.3s 0 transport_latency_assumed market_resolved c 1,386 not meas. 4ms 9ms 55.4s 58.1s 0 transport_latency_assumed market_resolved e 1,386 18 40ms 204ms 56.0s 58.9s 0 transport_latency_assumed market_resolved f 1,386 37 50ms 207ms 53.9s 56.1s 0 transport_latency_assumed market_resolved g 1,386 1,386 88ms 338ms 803ms 1.6s 0 transport_latency_assumed market_resolved h 1,386 not meas. 19ms 96ms 57.1s 59.7s 0 transport_latency_assumed new_market c 1,292 196 85ms 35.7s 46.5s 4.1h 0 transport_latency_assumed new_market e 1,292 114 170ms 28.6s 51.5s 2.3h 0 transport_latency_assumed new_market f 1,292 274 170ms 27.7s 51.3s 2.2h 0 transport_latency_assumed new_market g 1,292 1,292 298ms 30.7s 49.7s 3.7h 0 transport_latency_assumed new_market h 1,292 46 144ms 26.7s 50.8s 1.4h 0 transport_latency_assumed price_change c 78,407,242 6,013 4ms 7ms 96ms 5.6s 0 transport_latency_assumed price_change e 78,183,509 7,506 38ms 43ms 211ms 15.9s 0 transport_latency_assumed price_change f 78,497,507 19,888 47ms 53ms 206ms 4.1s 0 transport_latency_assumed price_change g 78,486,147 78,484,253 80ms 95ms 434ms 10.1s 0 transport_latency_assumed price_change h 78,494,157 5,352 18ms 23ms 184ms 49.7s 0 transport_latency_assumed tick_size_change c 2,336 not meas. 4ms 8ms 252ms 313ms 0 transport_latency_assumed tick_size_change e 2,308 not meas. 39ms 89ms 443ms 1.9s 0 transport_latency_assumed tick_size_change f 2,336 4 48ms 54ms 475ms 779ms 0 transport_latency_assumed tick_size_change g 2,332 2,332 78ms 98ms 706ms 1.3s 0 transport_latency_assumed tick_size_change h 2,336 not meas. 18ms 28ms 599ms 1.5s 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-06/06/2026-09-06T06.parquet sha256sum 2026-09-06T06.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.