Hour audit: 2026-09-08T10
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-08T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T10:00:00.000064014+00:00 · last event 2026-09-08T10:59:59.999956459+00:00
VOLUME 93,356,088 rows · 950,347,020 bytes (906.32 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 93,274,042 · c: 93,088,170 · h: 93,086,148 · f: 93,073,835 · e: 93,043,563 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 260,940 (0.28%) · c: 90,395,582 (96.83%) · h: 2,482,292 (2.66%) · f: 59,370 (0.06%) · e: 157,904 (0.17%) (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 93,356,088 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0481d41621a954436168ec23089ba153f168f783bffce899475c392ab0de1fb7
the corpus checksum ledger names this file with the same digest
joined 93,359,379 to merged 93,356,088, minus 3,291 (minus 0.0035%)
boundary drops 3,291 · 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-08T11:54:58Z 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 8,798,930 95,329,641 0-33 9db7cba7896dc7319eab521c1c163d8c7b285773242948d109a22b927205edc8 book 375,752 38,484,512 34-35 860f6f184d611208cf23c6beb3982a2589262088314d9f9006210777b3e07aa6 last_trade_price 56,623 3,170,648 36-36 07f688c8a01c42d613b0ef7f614a3a46f9ac9560e6f5f938fbd6ffb72c072421 market_resolved 971 157,666 37-37 02a19d281be8aacb651ad70748340aa52a432f21204fe0802af7270e48d5266d new_market 642 71,692 38-38 6e1274469a8e768f80d50dfb9a600f09f67378aff42b630c81f47ff1cd7a1fb9 price_change 84,119,882 811,949,371 39-359 7db1faa535f22b0222eaa3e51362b47ed20f00cfeed291bfc5e63549333cdde2 tick_size_change 3,288 117,781 360-360 0f50cd710cc8d9d19aea33b478ee5f92face5187f3738c98759ad234067222cb EVENT MIX count share price_change 84,119,882 90.11% best_bid_ask 8,798,930 9.43% book 375,752 0.40% last_trade_price 56,623 0.06% tick_size_change 3,288 <0.01% market_resolved 971 <0.01% new_market 642 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,799,051 8,798,930 121 184 FULL book 376,142 375,752 390 110,237 FULL last_trade_price 56,623 56,623 0 0 FULL market_resolved 971 971 0 0 FULL new_market 642 642 0 0 FULL price_change 84,122,662 84,119,882 2,780 84 FULL tick_size_change 3,288 3,288 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,798,229 8,570,785 4ms 8ms 57ms 4.0s 0 transport_latency_assumed best_bid_ask e 8,796,602 12,122 40ms 44ms 118ms 9.7s 0 transport_latency_assumed best_bid_ask f 8,797,045 3,774 47ms 51ms 131ms 5.7s 0 transport_latency_assumed best_bid_ask g 8,794,475 409 79ms 96ms 234ms 11.7s 0 transport_latency_assumed best_bid_ask h 8,797,888 211,840 17ms 20ms 73ms 8.4s 0 transport_latency_assumed book c 117,292 112,373 6ms 16ms 381ms 83.0d 0 book_staleness book e 117,668 2,305 41ms 116ms 42.7s 82.9d 0 book_staleness book f 118,984 2,582 49ms 146ms 19.7min 83.0d 0 book_staleness book g 371,431 253,840 2.2min 15.0h 27.6d 101.5d 0 book_staleness book h 117,248 4,652 21ms 46ms 633ms 82.8d 0 book_staleness last_trade_price c 56,570 54,420 9ms 37ms 183ms 5.0s 0 transport_latency_assumed last_trade_price e 56,416 200 46ms 98ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price f 56,559 96 53ms 120ms 2.0s 5.7s 0 transport_latency_assumed last_trade_price g 56,517 17 91ms 165ms 1.2s 11.8s 0 transport_latency_assumed last_trade_price h 56,565 1,890 22ms 56ms 258ms 6.0s 0 transport_latency_assumed market_resolved c 971 944 4ms 10ms 101ms 45.4s 0 transport_latency_assumed market_resolved e 971 4 40ms 149ms 349ms 42.8s 0 transport_latency_assumed market_resolved f 971 not meas. 48ms 194ms 424ms 43.1s 0 transport_latency_assumed market_resolved g 971 not meas. 84ms 275ms 557ms 55.5s 0 transport_latency_assumed market_resolved h 971 23 18ms 59ms 148ms 54.1s 0 transport_latency_assumed new_market c 466 284 54ms 310ms 24.0s 1.1min 0 transport_latency_assumed new_market e 466 101 144ms 17.7s 28.5s 58.9s 0 transport_latency_assumed new_market f 466 26 122ms 376ms 21.3s 25.3s 0 transport_latency_assumed new_market g 466 38 215ms 14.4s 23.8s 1.1min 0 transport_latency_assumed new_market h 466 193 72ms 432ms 22.2s 1.0min 0 transport_latency_assumed price_change c 84,111,354 81,653,574 5ms 9ms 73ms 4.0s 0 transport_latency_assumed price_change e 84,068,152 143,168 40ms 45ms 176ms 9.8s 0 transport_latency_assumed price_change f 84,096,522 52,888 47ms 54ms 205ms 9.9s 0 transport_latency_assumed price_change g 84,046,902 6,636 80ms 99ms 347ms 11.8s 0 transport_latency_assumed price_change h 84,109,722 2,263,616 17ms 22ms 102ms 8.5s 0 transport_latency_assumed tick_size_change c 3,288 3,202 5ms 8ms 48ms 195ms 0 transport_latency_assumed tick_size_change e 3,288 4 39ms 44ms 143ms 3.0s 0 transport_latency_assumed tick_size_change f 3,288 4 47ms 59ms 136ms 266ms 0 transport_latency_assumed tick_size_change g 3,280 not meas. 81ms 98ms 231ms 450ms 0 transport_latency_assumed tick_size_change h 3,288 78 17ms 24ms 126ms 4.4s 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-08/10/2026-09-08T10.parquet sha256sum 2026-09-08T10.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.