Hour audit: 2026-09-04T11
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-04T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T11:00:00.000392033+00:00 · last event 2026-09-04T11:59:59.999979090+00:00
VOLUME 98,196,027 rows · 1,003,249,668 bytes (956.77 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 96,077,662 · b: 94,940,198 · e: 94,028,956 · h: 93,711,688 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 571,665 (0.58%) · b: 94,607 (0.10%) · e: 94,027,778 (95.76%) · h: 3,501,977 (3.57%) (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 98,196,027 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 267b1f864b290634227e6df93f5af54a15ca26a5981f4514027ec73ebe8609bc
the corpus checksum ledger names this file with the same digest
joined 98,198,317 to merged 98,196,027, minus 2,290 (minus 0.0023%)
boundary drops 2,290 · 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-04T12:53:52Z 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 8,250,712 91,823,074 0-31 35649627b7e5a0546d86b16c8886b581d73b7522eb46d29ff5f78eebe9b048ab book 835,281 69,611,421 32-35 a1c430d0adc317a3095d349763b861772199d49d5b4fd195bfa89023da3f59d8 last_trade_price 63,990 3,519,700 36-36 a4be7e852f25f05b056a60f26cc5175afb7c7f04d21d46ce26e6c712eb6b92ce market_resolved 561 93,109 37-37 d70c1c932a068f06c1db6b02ec53bd4533788419e400e796be8022466b06b4b4 new_market 987 107,704 38-38 599e05df12cb57d5ec869e8891cc07c8d5a89e4a5993de9f1d26b072faac4e48 price_change 89,042,056 836,885,193 39-378 30f66d0ba9b579fa0d141810b1c90c9c577b72058a067f62da011e37253ff9b0 tick_size_change 2,440 88,337 379-379 51564a5d03a12b30a101d9ed01cd6eb0a4cf5923ccc2c636cb8dcda1ae260399 EVENT MIX count share price_change 89,042,056 90.68% best_bid_ask 8,250,712 8.40% book 835,281 0.85% last_trade_price 63,990 0.07% tick_size_change 2,440 <0.01% new_market 987 <0.01% market_resolved 561 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,250,818 8,250,712 106 1,721 FULL book 836,297 835,281 1,016 170,442 FULL last_trade_price 63,990 63,990 0 100 FULL market_resolved 561 561 0 5 FULL new_market 987 987 0 0 FULL price_change 89,043,224 89,042,056 1,168 10,505 FULL tick_size_change 2,440 2,440 0 22 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,247,910 44 49ms 62ms 197ms 5.3s 0 transport_latency_assumed best_bid_ask c 8,127,040 658 3ms 6ms 58ms 2.0s 0 transport_latency_assumed best_bid_ask e 8,122,211 8,122,143 39ms 50ms 236ms 9.7s 0 transport_latency_assumed best_bid_ask h 8,248,966 127,867 18ms 25ms 114ms 9.6s 0 transport_latency_assumed book b 292,604 88,917 9.0s 7.2h 26.7d 79.1d 0 book_staleness book c 550,974 317,135 1.5min 12.3h 29.8d 97.6d 0 book_staleness book e 308,792 308,438 17.8s 8.1h 25.9d 97.6d 0 book_staleness book h 278,009 120,791 3.5s 6.3h 26.5d 97.6d 0 book_staleness last_trade_price b 63,903 6 59ms 187ms 1.3s 5.3s 0 transport_latency_assumed last_trade_price c 63,142 10 8ms 37ms 204ms 5.0s 0 transport_latency_assumed last_trade_price e 63,416 63,416 47ms 179ms 2.8s 9.7s 0 transport_latency_assumed last_trade_price h 63,912 558 24ms 77ms 366ms 6.6s 0 transport_latency_assumed market_resolved b 554 not meas. 51ms 338ms 55.5s 1.0min 0 transport_latency_assumed market_resolved c 551 4 3ms 17ms 1.0min 2.0min 0 transport_latency_assumed market_resolved e 552 552 39ms 349ms 55.3s 1.0min 0 transport_latency_assumed market_resolved h 554 5 19ms 146ms 55.7s 55.7s 0 transport_latency_assumed new_market b 709 38 158ms 17.7s 32.3s 1.1min 0 transport_latency_assumed new_market c 709 132 43ms 18.7s 27.2s 1.0min 0 transport_latency_assumed new_market e 709 709 124ms 17.3s 34.0s 1.1min 0 transport_latency_assumed new_market h 709 108 114ms 16.8s 36.2s 1.0min 0 transport_latency_assumed price_change b 86,332,078 5,602 49ms 66ms 252ms 5.3s 0 transport_latency_assumed price_change c 87,332,834 253,726 3ms 7ms 64ms 2.7s 0 transport_latency_assumed price_change e 85,530,896 85,530,140 39ms 63ms 296ms 9.7s 0 transport_latency_assumed price_change h 85,117,098 3,252,588 18ms 27ms 131ms 9.6s 0 transport_latency_assumed tick_size_change b 2,440 not meas. 49ms 62ms 133ms 266ms 0 transport_latency_assumed tick_size_change c 2,412 not meas. 3ms 6ms 24ms 231ms 0 transport_latency_assumed tick_size_change e 2,380 2,380 39ms 44ms 115ms 140ms 0 transport_latency_assumed tick_size_change h 2,440 60 18ms 23ms 54ms 125ms 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/11/2026-09-04T11.parquet sha256sum 2026-09-04T11.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.