Hour audit: 2026-09-04T20
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-04T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T20:00:00.020748606+00:00 · last event 2026-09-04T20:59:59.999987772+00:00
VOLUME 105,351,162 rows · 1,109,781,032 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 104,456,564 · e: 104,435,686 · c: 104,378,935 · b: 95,333,909 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 79,465 (0.08%) · e: 104,430,071 (99.13%) · c: 56,631 (0.05%) · b: 784,995 (0.75%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,351,162 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 96a656eb6b7e758fb883eae7309986612af7ea7390664e7ac3e34f6675262535
the corpus checksum ledger names this file with the same digest
joined 105,367,753 to merged 105,351,162, minus 16,591 (minus 0.0157%)
boundary drops 16,591 · 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-04T21:54:05Z as bceh
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,173,087 124,292,295 0-42 b0615b5b08002c77b69cd8bf0edc4fab6e338a4b2278afa71769fae8d70e6cdc book 998,513 70,810,591 43-46 2ed11ba92daba0145efd72c0038023e025a773c1759be709f8fd35da76b5d5e7 last_trade_price 66,734 3,782,828 47-47 9850481cc849a81cad02e330afdd98ff1f7ff3ca3f5a30b2de4f2842437036a5 market_resolved 2,998 449,031 48-48 31761408f8491dbe8e7ed3c29d0a7224df4a60638b623d610249a8ff1b1b0f94 new_market 2,388 250,752 49-49 0fb7756edd2a4c8574821463caf348d1aa9a83d86d08423fe4409c4b768fb7fb price_change 93,101,774 908,789,237 50-405 df929f86373a04b1c2f10c096502af2be9bcd1a3b400f394ab32fe69ff788d9d tick_size_change 5,668 206,744 406-406 b703704138c4b27baea76edf01b40eb4786ba86fdc30fb7c411149f2d0ce6a3e EVENT MIX count share price_change 93,101,774 88.37% best_bid_ask 11,173,087 10.61% book 998,513 0.95% last_trade_price 66,734 0.06% tick_size_change 5,668 <0.01% market_resolved 2,998 <0.01% new_market 2,388 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,174,818 11,173,087 1,731 1,368 FULL book 998,629 998,513 116 193,308 FULL last_trade_price 66,752 66,734 18 181 FULL market_resolved 2,998 2,998 0 59 FULL new_market 2,388 2,388 0 0 FULL price_change 93,116,500 93,101,774 14,726 792 FULL tick_size_change 5,668 5,668 0 66 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,133,272 174 50ms 66ms 297ms 16.6s 0 transport_latency_assumed best_bid_ask c 11,165,239 507 4ms 9ms 109ms 13.3s 0 transport_latency_assumed best_bid_ask e 11,171,275 11,170,711 41ms 59ms 339ms 17.0s 0 transport_latency_assumed best_bid_ask h 11,171,494 1,695 18ms 30ms 247ms 47.4s 0 transport_latency_assumed book b 929,400 763,627 2.4min 11.8h 32.2d 97.9d 0 book_staleness book c 187,722 48,196 8ms 13.0min 13.3d 97.9d 0 book_staleness book e 164,478 164,452 44ms 1.6min 2.9d 79.4d 0 book_staleness book h 161,675 22,238 24ms 1.1min 2.1d 79.4d 0 book_staleness last_trade_price b 61,087 1 60ms 198ms 1.4s 16.8s 0 transport_latency_assumed last_trade_price c 65,792 5 10ms 41ms 303ms 7.5s 0 transport_latency_assumed last_trade_price e 66,624 66,617 48ms 221ms 2.5s 17.0s 0 transport_latency_assumed last_trade_price h 66,488 111 24ms 86ms 721ms 35.8s 0 transport_latency_assumed market_resolved b 2,841 247 63ms 484ms 12.2min 12.7min 0 transport_latency_assumed market_resolved c 2,744 6 4ms 9ms 160ms 44.9s 0 transport_latency_assumed market_resolved e 2,745 2,745 42ms 166ms 598ms 929ms 0 transport_latency_assumed market_resolved h 2,745 not meas. 28ms 72ms 262ms 3.1s 0 transport_latency_assumed new_market b 1,698 154 184ms 37.7s 8.3min 8.3min 0 transport_latency_assumed new_market c 1,602 229 73ms 36.8s 1.3min 3.8min 0 transport_latency_assumed new_market e 1,602 1,602 183ms 27.2s 1.4min 1.8min 0 transport_latency_assumed new_market h 1,602 403 141ms 24.8s 1.4min 2.0min 0 transport_latency_assumed price_change b 84,200,207 20,792 50ms 76ms 422ms 17.3s 0 transport_latency_assumed price_change c 92,950,168 7,688 5ms 10ms 154ms 13.7s 0 transport_latency_assumed price_change e 93,023,294 93,018,276 41ms 77ms 490ms 17.1s 0 transport_latency_assumed price_change h 93,046,892 55,018 18ms 35ms 319ms 47.4s 0 transport_latency_assumed tick_size_change b 5,404 not meas. 50ms 63ms 246ms 429ms 0 transport_latency_assumed tick_size_change c 5,668 not meas. 4ms 8ms 145ms 910ms 0 transport_latency_assumed tick_size_change e 5,668 5,668 41ms 83ms 240ms 1.3s 0 transport_latency_assumed tick_size_change h 5,668 not meas. 18ms 26ms 239ms 5.3s 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-04/20/2026-09-04T20.parquet sha256sum 2026-09-04T20.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.