Hour audit: 2026-08-31T04
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-31T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T04:00:00.038845528+00:00 · last event 2026-08-31T04:59:59.999943079+00:00
VOLUME 66,863,828 rows · 658,767,500 bytes (628.25 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 66,836,736 · h: 66,789,064 · a: 66,721,739 · e: 66,439,542 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 30,782 (0.05%) · h: 385,695 (0.58%) · a: 8,365 (0.01%) · e: 66,438,986 (99.36%) (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 66,863,828 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 e63a8fa582614b5b857861442b7e193b58d611600c7f8b5498c7f24903184712
the corpus checksum ledger names this file with the same digest
joined 66,864,386 to merged 66,863,828, minus 558 (minus 0.0008%)
boundary drops 558 · 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-31T05:47:45Z 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 6,579,279 73,128,250 0-25 51f4ce270da8f35d68ed23b677308696c14a9f899acb3f065714d84d53355926 book 153,263 13,865,740 26-26 d1e69c01d691a7c49d161779c007b8c1878b403bba4ddfd9bebf5309c921cc57 last_trade_price 62,171 3,452,709 27-27 11a3911719e1679269d0cc01aa8462c199c859a9f3865246528be2fac79e869a market_resolved 731 114,651 28-28 7b582fd144465abd318f6ec27023c072c6af96724098ebf570ff8cc48b37d9e5 new_market 3,206 307,037 29-29 2fc3f56fd23bab7afef88a13d8e56dda1dd64679902f0029b5c5eb69c3b494d1 price_change 60,063,550 567,069,574 30-259 69adfe8346b2b5977761a2592f2e6643f30ab88e05fa4ae65218c2da642724e4 tick_size_change 1,628 60,168 260-260 0ce5263987073e86bf36c41db0c315a9ab389a8e587b5856b764065b73b28546 EVENT MIX count share price_change 60,063,550 89.83% best_bid_ask 6,579,279 9.84% book 153,263 0.23% last_trade_price 62,171 0.09% new_market 3,206 <0.01% tick_size_change 1,628 <0.01% market_resolved 731 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,579,345 6,579,279 66 55,882 PARTIAL book 153,265 153,263 2 12,833 PARTIAL last_trade_price 62,171 62,171 0 3,113 PARTIAL market_resolved 731 731 0 708 PARTIAL new_market 3,206 3,206 0 2,004 PARTIAL price_change 60,064,040 60,063,550 490 114,004 PARTIAL tick_size_change 1,628 1,628 0 407 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,570,470 226 37ms 55ms 662ms 30.1s 0 transport_latency_assumed best_bid_ask c 6,578,256 672 4ms 7ms 179ms 5.1s 0 transport_latency_assumed best_bid_ask e 6,565,168 6,565,102 42ms 122ms 1.8s 33.3s 0 transport_latency_assumed best_bid_ask h 6,577,711 13,279 11ms 17ms 299ms 52.0s 0 transport_latency_assumed book a 133,753 6,554 122ms 5.3s 2.6h 74.8d 0 book_staleness book c 136,230 4,277 7ms 55ms 23.4min 93.3d 0 book_staleness book e 132,581 132,579 173ms 8.0s 2.2h 22.6d 0 book_staleness book h 134,744 9,853 20ms 227ms 4.6min 74.7d 0 book_staleness last_trade_price a 60,082 4 81ms 3.1s 11.5s 30.1s 0 transport_latency_assumed last_trade_price c 62,120 75 10ms 43ms 251ms 4.7s 0 transport_latency_assumed last_trade_price e 59,096 59,096 124ms 5.1s 16.0s 33.4s 0 transport_latency_assumed last_trade_price h 61,964 2,996 19ms 137ms 576ms 27.9s 0 transport_latency_assumed market_resolved a 708 17 39ms 299ms 1.1s 53.0s 0 transport_latency_assumed market_resolved c 708 not meas. 4ms 6ms 79ms 55.6s 0 transport_latency_assumed market_resolved e 708 708 42ms 265ms 1.2s 48.7s 0 transport_latency_assumed market_resolved h 708 6 12ms 44ms 47.1s 1.0min 0 transport_latency_assumed new_market a 2,004 412 270ms 27.8s 58.0s 1.3min 0 transport_latency_assumed new_market c 2,004 399 109ms 29.8s 53.2s 1.3min 0 transport_latency_assumed new_market e 2,004 2,004 273ms 25.5s 1.1min 1.1min 0 transport_latency_assumed new_market h 2,004 391 149ms 30.2s 1.1min 1.3min 0 transport_latency_assumed price_change a 59,953,098 1,152 38ms 106ms 3.1s 30.2s 0 transport_latency_assumed price_change c 60,055,790 25,359 4ms 8ms 202ms 5.6s 0 transport_latency_assumed price_change e 59,678,361 59,677,873 42ms 210ms 6.4s 33.4s 0 transport_latency_assumed price_change h 60,010,305 359,166 12ms 21ms 328ms 52.0s 0 transport_latency_assumed tick_size_change a 1,624 not meas. 38ms 260ms 689ms 3.2s 0 transport_latency_assumed tick_size_change c 1,628 not meas. 4ms 34ms 627ms 3.2s 0 transport_latency_assumed tick_size_change e 1,624 1,624 43ms 468ms 1.4s 5.9s 0 transport_latency_assumed tick_size_change h 1,628 4 12ms 48ms 4.0s 27.5s 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-31/04/2026-08-31T04.parquet sha256sum 2026-08-31T04.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.