Hour audit: 2026-09-06T17
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-06T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T17:00:00.067036683+00:00 · last event 2026-09-06T17:59:59.999952850+00:00
VOLUME 122,127,794 rows · 1,321,479,398 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 120,212,550 · g: 120,191,023 · h: 120,055,734 · e: 119,980,986 · c: 98,764,300 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 475,556 (0.39%) · g: 40,702 (0.03%) · h: 25,618,227 (20.98%) · e: 1,793,215 (1.47%) · c: 94,200,094 (77.13%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 87958fda6fd1f846a94335c5b5e57512c76a4c92e8bc221264034bfa72a665de
the corpus checksum ledger names this file with the same digest
joined 122,133,955 to merged 122,127,794, minus 6,161 (minus 0.0050%)
boundary drops 6,161 · 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-07T00:26:59Z 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,309,080 139,815,798 0-46 f309e9ffa7e1288bd44b0a3671e6ba3634c756beea36a30b5fb809bbbd1c4e55 book 1,921,359 85,320,290 47-54 9e611011e52d0a5100691eadc2a95e188b9e8a5953076d05e0a91e8c479bfd6b last_trade_price 69,908 4,006,525 55-55 40e1b2bb2a826c11f64ef3cc97ea5cc3d98b8940cb1f2f4965e5539bd0f14f51 market_resolved 3,102 409,551 56-56 83ef76b22024a621541bb727849ac43d733c7523fc819cdd4adcd40de2994ec4 new_market 3,725 341,979 57-57 0b97e7e0406d54063d34d19d5632db7cd5b049f73b7cdea0cb01e1d1671f8999 price_change 107,813,092 1,089,920,123 58-469 b4934c4073d3ede3d429f515f05c7782b009d6e05f389437d9b43ae1bc438a85 tick_size_change 7,528 276,160 470-470 64e9ae1b7914745ab31bc5fba9bd6f3f5ba00383a269e1f600e8837be390f517 EVENT MIX count share price_change 107,813,092 88.28% best_bid_ask 12,309,080 10.08% book 1,921,359 1.57% last_trade_price 69,908 0.06% tick_size_change 7,528 <0.01% new_market 3,725 <0.01% market_resolved 3,102 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,309,563 12,309,080 483 3,440 FULL book 1,921,393 1,921,359 34 172,103 FULL last_trade_price 69,914 69,908 6 537 FULL market_resolved 3,102 3,102 0 125 FULL new_market 3,725 3,725 0 5 FULL price_change 107,818,690 107,813,092 5,598 2,234 FULL tick_size_change 7,568 7,528 40 267 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,960,115 9,500,831 5ms 12ms 177ms 16.2s 0 transport_latency_assumed best_bid_ask e 12,305,859 174,774 38ms 49ms 247ms 5.7s 0 transport_latency_assumed best_bid_ask f 12,305,914 42,179 46ms 61ms 273ms 5.4s 0 transport_latency_assumed best_bid_ask g 12,304,852 3,306 83ms 129ms 565ms 17.2s 0 transport_latency_assumed best_bid_ask h 12,306,873 2,587,990 19ms 31ms 277ms 49.1s 0 transport_latency_assumed book c 1,887,479 1,878,596 4.4min 23.5h 35.2d 99.8d 0 book_staleness book e 147,660 4,888 40ms 194ms 3.6s 39.1d 0 book_staleness book f 146,695 2,113 49ms 197ms 2.6s 7.8s 0 book_staleness book g 153,458 4,922 91ms 765ms 6.3h 81.3d 0 book_staleness book h 146,874 30,840 23ms 75ms 2.6s 73.3d 0 book_staleness last_trade_price c 56,195 53,297 10ms 46ms 320ms 4.9s 0 transport_latency_assumed last_trade_price e 69,858 1,133 44ms 155ms 2.0s 5.7s 0 transport_latency_assumed last_trade_price f 69,872 358 53ms 170ms 1.7s 5.5s 0 transport_latency_assumed last_trade_price g 69,771 60 96ms 324ms 5.7s 17.2s 0 transport_latency_assumed last_trade_price h 69,871 15,060 25ms 73ms 531ms 9.1s 0 transport_latency_assumed market_resolved c 2,745 2,662 6ms 6.1min 11.6min 13.4min 0 transport_latency_assumed market_resolved e 2,492 29 40ms 199ms 525ms 888ms 0 transport_latency_assumed market_resolved f 2,492 9 48ms 205ms 547ms 4.9s 0 transport_latency_assumed market_resolved g 2,492 1 92ms 375ms 1.1s 5.6s 0 transport_latency_assumed market_resolved h 2,492 401 22ms 87ms 470ms 6.6s 0 transport_latency_assumed new_market c 2,372 1,660 111ms 4.0min 46.4min 13.2h 0 transport_latency_assumed new_market e 2,107 440 173ms 21.2s 59.5s 2.2h 0 transport_latency_assumed new_market f 2,107 378 184ms 20.7s 48.1s 39.7min 0 transport_latency_assumed new_market g 2,102 371 321ms 21.9s 51.8s 19.3min 0 transport_latency_assumed new_market h 2,107 876 138ms 20.0s 56.2s 13.1h 0 transport_latency_assumed price_change c 86,848,894 82,757,147 5ms 13ms 186ms 17.6s 0 transport_latency_assumed price_change e 107,445,466 1,611,789 38ms 58ms 318ms 5.7s 0 transport_latency_assumed price_change f 107,677,922 430,411 46ms 69ms 335ms 5.5s 0 transport_latency_assumed price_change g 107,650,784 32,027 85ms 147ms 724ms 17.2s 0 transport_latency_assumed price_change h 107,519,989 22,981,718 19ms 34ms 292ms 49.1s 0 transport_latency_assumed tick_size_change c 6,500 5,901 5ms 43ms 373ms 709ms 0 transport_latency_assumed tick_size_change e 7,544 162 38ms 72ms 406ms 639ms 0 transport_latency_assumed tick_size_change f 7,548 108 46ms 85ms 390ms 744ms 0 transport_latency_assumed tick_size_change g 7,564 15 85ms 172ms 833ms 1.5s 0 transport_latency_assumed tick_size_change h 7,528 1,342 19ms 45ms 506ms 4.9s 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/17/2026-09-06T17.parquet sha256sum 2026-09-06T17.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.