Hour audit: 2026-08-30T11
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 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T11 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T11:00:00.020182695+00:00 · last event 2026-08-30T11:59:59.999999349+00:00
VOLUME 96,633,493 rows · 977,545,230 bytes (932.26 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 96,610,774 · a: 96,585,415 · h: 96,497,622 · e: 96,351,715 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 104,272 (0.11%) · a: 4,813 (0.00%) · h: 175,167 (0.18%) · e: 96,349,241 (99.71%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,633,493 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 7630c0e0da12bc6af6530b9a4ea27e10fab8ef324623c6ae0ad13d1ef31a080f
the corpus checksum ledger names this file with the same digest
joined 96,637,003 to merged 96,633,493, minus 3,510 (minus 0.0036%)
boundary drops 3,510 · 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-08-30T14:47:20Z as aceh
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 8,601,500 96,676,026 0-32 4fa13a9f4c4db5b4eb5947ddefa12e406fc2ee84059041d53abcf127fdf56c9d book 135,518 13,291,193 33-33 42eb7736859534f4822f179ad30781fe653ecc8aaea8b86850ccb33c5a3786d1 last_trade_price 56,766 3,324,381 34-34 18e7afca9a591917e9acbec4093902f1b35b8f445a5299f84327d4d9c74ba5c2 market_resolved 604 96,730 35-35 797111621be41c3d26d1a9743531603e988d366aa11c23b6a75e36bda801159c new_market 2,553 242,340 36-36 9b0921c8f5b776a04d207cab3c7015e5ff9006bb7fdfd904193da377619baffc price_change 87,832,968 862,682,251 37-372 2d2f1a3a9d9e633ba5457c049d50d73294320795c65a384c07b9735831f944df tick_size_change 3,584 129,729 373-373 4b6bb2007ed5302a4b8d564bd1ee59d6dc40167d82774e8630e7187713e2b111 EVENT MIX count share price_change 87,832,968 90.89% best_bid_ask 8,601,500 8.90% book 135,518 0.14% last_trade_price 56,766 0.06% tick_size_change 3,584 <0.01% new_market 2,553 <0.01% market_resolved 604 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,601,657 8,601,500 157 68,882 PARTIAL book 135,518 135,518 0 11,543 PARTIAL last_trade_price 56,767 56,766 1 3,951 PARTIAL market_resolved 604 604 0 586 PARTIAL new_market 2,553 2,553 0 1,573 PARTIAL price_change 87,836,320 87,832,968 3,352 129,158 PARTIAL tick_size_change 3,584 3,584 0 896 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,597,382 172 38ms 47ms 368ms 15.4s 0 transport_latency_assumed best_bid_ask c 8,600,075 1,216 9ms 17ms 132ms 2.9s 0 transport_latency_assumed best_bid_ask e 8,593,304 8,593,192 45ms 90ms 922ms 27.2s 0 transport_latency_assumed best_bid_ask h 8,599,290 6,920 12ms 17ms 223ms 40.0s 0 transport_latency_assumed book a 121,228 3,658 47ms 1.1s 5.9min 74.0d 0 book_staleness book c 119,614 2,284 12ms 31ms 5.3s 73.9d 0 book_staleness book e 126,680 126,680 63ms 4.8s 3.7h 49.7d 0 book_staleness book h 119,044 2,896 18ms 100ms 2.7s 74.0d 0 book_staleness last_trade_price a 56,610 4 48ms 689ms 6.1s 15.4s 0 transport_latency_assumed last_trade_price c 56,744 3 15ms 42ms 241ms 5.0s 0 transport_latency_assumed last_trade_price e 56,412 56,412 59ms 1.8s 11.5s 25.6s 0 transport_latency_assumed last_trade_price h 56,745 347 17ms 73ms 868ms 7.9s 0 transport_latency_assumed market_resolved a 586 18 40ms 333ms 526ms 632ms 0 transport_latency_assumed market_resolved c 586 not meas. 10ms 17ms 68ms 252ms 0 transport_latency_assumed market_resolved e 586 586 45ms 327ms 817ms 1.5s 0 transport_latency_assumed market_resolved h 586 not meas. 12ms 62ms 154ms 472ms 0 transport_latency_assumed new_market a 1,573 93 259ms 18.8s 26.0s 1.2min 0 transport_latency_assumed new_market c 1,573 211 107ms 18.8s 25.1s 38.0s 0 transport_latency_assumed new_market e 1,573 1,573 236ms 19.2s 29.4s 58.7s 0 transport_latency_assumed new_market h 1,573 676 157ms 19.7s 46.9s 58.6s 0 transport_latency_assumed price_change a 87,804,452 868 38ms 60ms 557ms 15.5s 0 transport_latency_assumed price_change c 87,828,598 100,558 9ms 18ms 146ms 4.7s 0 transport_latency_assumed price_change e 87,569,576 87,567,214 45ms 129ms 2.6s 27.2s 0 transport_latency_assumed price_change h 87,716,800 164,328 12ms 19ms 242ms 49.3s 0 transport_latency_assumed tick_size_change a 3,584 not meas. 38ms 45ms 211ms 536ms 0 transport_latency_assumed tick_size_change c 3,584 not meas. 9ms 19ms 197ms 512ms 0 transport_latency_assumed tick_size_change e 3,584 3,584 45ms 119ms 318ms 2.7s 0 transport_latency_assumed tick_size_change h 3,584 not meas. 12ms 19ms 109ms 941ms 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-08-30/11/2026-08-30T11.parquet sha256sum 2026-08-30T11.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.