Hour audit: 2026-09-01T10
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.
1 finding
- a machine expected this hour contributed nothing. Of the 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T10:00:00.034848900+00:00 · last event 2026-09-01T10:59:59.999910994+00:00
VOLUME 87,297,116 rows · 852,038,300 bytes (812.57 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 87,269,527 · h: 87,249,808 · e: 86,890,546 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 24,097 (0.03%) · h: 383,621 (0.44%) · e: 86,889,398 (99.53%) (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 87,297,116 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 f70a6c01e56022db77490fd4dd71920549e298ac510d230baa3c7bc4af7d5964
the corpus checksum ledger names this file with the same digest
joined 87,298,276 to merged 87,297,116, minus 1,160 (minus 0.0013%)
boundary drops 1,160 · 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-01T14:27:00Z as ceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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 7,685,464 85,704,993 0-29 fe5a6216eef0c6df1bdea82eb56c8fcb7423a5772ade377c7c21cad6456c2d08 book 163,133 15,979,115 30-30 7469db22061e3e6bb530605756a5120a887cc5c0feb0330fd03a4e2654d3c93b last_trade_price 62,372 3,463,802 31-31 576b205f8a51c1ff673096066e83281ace91c81b503af5827df4769225be0030 market_resolved 1,007 159,878 32-32 848d66bb05bfc2e45132b098c07cd5660d1c8a38671d3c396dd3fe0d95f9ac28 new_market 1,416 150,316 33-33 2d97928787b3b658ab34fa894fe041c50905d12da5d42a868a8914ae6e8759d9 price_change 79,380,856 745,481,257 34-336 7b8faa06685bf091264278282d0ef0a08ecf658e78d6aeabbd61c7418323a622 tick_size_change 2,868 104,079 337-337 9ca4b22cee156de4ec743369e9606a4c1829af05da70176f331d80ea79fec52f EVENT MIX count share price_change 79,380,856 90.93% best_bid_ask 7,685,464 8.80% book 163,133 0.19% last_trade_price 62,372 0.07% tick_size_change 2,868 <0.01% new_market 1,416 <0.01% market_resolved 1,007 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,685,530 7,685,464 66 75,274 PARTIAL book 163,137 163,133 4 17,612 PARTIAL last_trade_price 62,372 62,372 0 3,241 PARTIAL market_resolved 1,007 1,007 0 994 PARTIAL new_market 1,416 1,416 0 1,002 PARTIAL price_change 79,381,946 79,380,856 1,090 128,195 PARTIAL tick_size_change 2,868 2,868 0 717 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,684,679 1,204 3ms 6ms 116ms 3.1s 0 transport_latency_assumed best_bid_ask e 7,670,928 7,670,862 41ms 86ms 911ms 21.2s 0 transport_latency_assumed best_bid_ask h 7,683,802 13,398 18ms 25ms 243ms 9.6s 0 transport_latency_assumed book c 144,275 15,404 6ms 3.3s 17.9h 94.5d 0 book_staleness book e 141,308 141,306 127ms 27.1s 11.9h 94.5d 0 book_staleness book h 129,818 6,423 27ms 399ms 2.1s 30.0d 0 book_staleness last_trade_price c 62,275 13 9ms 38ms 194ms 4.6s 0 transport_latency_assumed last_trade_price e 59,792 59,792 82ms 4.0s 16.6s 21.3s 0 transport_latency_assumed last_trade_price h 62,342 2,567 26ms 391ms 1.9s 8.0s 0 transport_latency_assumed market_resolved c 994 not meas. 3ms 7ms 54.6s 57.5s 0 transport_latency_assumed market_resolved e 994 994 41ms 256ms 59.2s 1.0min 0 transport_latency_assumed market_resolved h 994 13 18ms 69ms 56.7s 59.5s 0 transport_latency_assumed new_market c 1,002 138 63ms 16.9s 23.3s 1.5min 0 transport_latency_assumed new_market e 1,002 1,002 232ms 16.8s 24.5s 1.4min 0 transport_latency_assumed new_market h 1,002 276 139ms 14.8s 22.6s 58.7s 0 transport_latency_assumed price_change c 79,373,434 7,338 4ms 7ms 220ms 3.4s 0 transport_latency_assumed price_change e 79,013,654 79,012,574 41ms 131ms 3.9s 21.3s 0 transport_latency_assumed price_change h 79,368,982 360,944 18ms 31ms 480ms 9.7s 0 transport_latency_assumed tick_size_change c 2,868 not meas. 4ms 5ms 39ms 481ms 0 transport_latency_assumed tick_size_change e 2,868 2,868 41ms 100ms 275ms 423ms 0 transport_latency_assumed tick_size_change h 2,868 not meas. 18ms 28ms 71ms 2.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-01/10/2026-09-01T10.parquet sha256sum 2026-09-01T10.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.