Hour audit: 2026-09-06T12
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-06T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-06T12:00:00.060884021+00:00 · last event 2026-09-06T12:59:59.999997424+00:00
VOLUME 118,403,446 rows · 1,257,888,130 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 115,857,170 · g: 115,847,384 · h: 115,834,564 · e: 115,719,328 · c: 85,500,135 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 385,676 (0.33%) · g: 57,642 (0.05%) · h: 33,981,485 (28.70%) · e: 1,707,632 (1.44%) · c: 82,271,011 (69.48%) (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 118,403,446 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 aa0ec8f4b917dbf6d9e19e53d3ca43b2731c80db53c21e06029be5673db2ae5c
the corpus checksum ledger names this file with the same digest
joined 118,405,764 to merged 118,403,446, minus 2,318 (minus 0.0020%)
boundary drops 2,318 · 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-06T22:07:01Z 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,558,130 119,390,958 0-40 9fea6653e41c1120bb2d1bbe4e2bb55601e0719a45b5366a9482eb468afa9672 book 2,600,520 95,109,531 41-50 a9888381b8ba896bc474faa873308bd7ba43b2b00de36e6ae2f65ad7cd282fd2 last_trade_price 63,409 3,633,006 51-51 b2189ed03426b865738c099426d32af65a43c61d454885c1959256deec606529 market_resolved 2,058 211,049 52-52 fedcf7a8fd7f9dde17e866a0c0316c59c0bef3c7557cf19c114b56b7d5d50bb6 new_market 2,681 218,489 53-53 c2663f0b50574255ddcb6a4ce09c76bc53c6f3f793256e8efee834633e842651 price_change 105,171,216 1,037,780,175 54-455 b6d4574c9d1086e8b220368ba23f14a76c55ba75e964f8e45ad4d08f4b59b635 tick_size_change 5,432 196,473 456-456 84a2954f872eb5af670d9f5387910b36a8f2a4b5b8e1baa152d31b736762831e EVENT MIX count share price_change 105,171,216 88.82% best_bid_ask 10,558,130 8.92% book 2,600,520 2.20% last_trade_price 63,409 0.05% tick_size_change 5,432 <0.01% new_market 2,681 <0.01% market_resolved 2,058 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,558,317 10,558,130 187 4,623 FULL book 2,600,536 2,600,520 16 172,163 FULL last_trade_price 63,410 63,409 1 638 FULL market_resolved 2,058 2,058 0 42 FULL new_market 2,681 2,681 0 48 FULL price_change 105,173,330 105,171,216 2,114 2,242 FULL tick_size_change 5,432 5,432 0 341 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,605,578 7,323,497 5ms 10ms 117ms 10.6s 0 transport_latency_assumed best_bid_ask e 10,555,629 153,605 41ms 47ms 190ms 3.1s 0 transport_latency_assumed best_bid_ask f 10,555,636 33,483 49ms 58ms 218ms 3.8s 0 transport_latency_assumed best_bid_ask g 10,554,053 3,789 81ms 101ms 436ms 14.3s 0 transport_latency_assumed best_bid_ask h 10,556,252 3,043,756 18ms 27ms 185ms 21.7s 0 transport_latency_assumed book c 2,558,388 2,551,672 5.8min 22.2h 35.0d 99.6d 0 book_staleness book e 131,957 4,690 43ms 120ms 1.8s 35.5d 0 book_staleness book f 131,673 1,946 51ms 127ms 1.3s 18.4s 0 book_staleness book g 137,995 4,172 85ms 464ms 6.9h 81.1d 0 book_staleness book h 132,250 38,040 22ms 58ms 2.7s 81.0d 0 book_staleness last_trade_price c 45,258 43,149 10ms 40ms 326ms 10.3s 0 transport_latency_assumed last_trade_price e 63,384 1,284 47ms 103ms 780ms 5.0s 0 transport_latency_assumed last_trade_price f 63,386 376 55ms 112ms 851ms 5.1s 0 transport_latency_assumed last_trade_price g 63,353 39 91ms 227ms 3.5s 14.3s 0 transport_latency_assumed last_trade_price h 63,313 18,561 24ms 61ms 483ms 8.6s 0 transport_latency_assumed market_resolved c 1,662 1,579 60ms 10.4min 19.4min 19.4min 0 transport_latency_assumed market_resolved e 1,247 75 42ms 206ms 57.3s 1.0min 0 transport_latency_assumed market_resolved f 1,247 10 50ms 221ms 57.3s 1.0min 0 transport_latency_assumed market_resolved g 1,247 12 86ms 347ms 967ms 1.8s 0 transport_latency_assumed market_resolved h 1,247 382 19ms 95ms 4.6s 58.3s 0 transport_latency_assumed new_market c 1,899 1,251 16.9s 12.2min 3.2h 9.9h 0 transport_latency_assumed new_market e 1,367 387 160ms 16.6s 25.3s 3.4min 0 transport_latency_assumed new_market f 1,367 291 186ms 18.8s 27.0s 3.0h 0 transport_latency_assumed new_market g 1,367 132 315ms 16.9s 27.8s 3.8h 0 transport_latency_assumed new_market h 1,367 620 151ms 17.1s 29.0s 1.3h 0 transport_latency_assumed price_change c 75,283,282 72,345,890 5ms 11ms 128ms 11.3s 0 transport_latency_assumed price_change e 104,960,312 1,547,549 41ms 50ms 225ms 3.1s 0 transport_latency_assumed price_change f 105,098,429 349,568 49ms 61ms 242ms 3.8s 0 transport_latency_assumed price_change g 105,083,937 49,498 82ms 107ms 517ms 14.4s 0 transport_latency_assumed price_change h 105,074,703 30,878,711 18ms 29ms 193ms 21.8s 0 transport_latency_assumed tick_size_change c 4,068 3,973 5ms 9ms 56ms 381ms 0 transport_latency_assumed tick_size_change e 5,432 42 41ms 45ms 99ms 311ms 0 transport_latency_assumed tick_size_change f 5,432 2 49ms 54ms 103ms 321ms 0 transport_latency_assumed tick_size_change g 5,432 not meas. 81ms 96ms 197ms 560ms 0 transport_latency_assumed tick_size_change h 5,432 1,415 18ms 24ms 87ms 3.1s 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/12/2026-09-06T12.parquet sha256sum 2026-09-06T12.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.