Hour audit: 2026-08-30T14
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-30T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T14:00:00.035228432+00:00 · last event 2026-08-30T14:59:59.999995722+00:00
VOLUME 100,753,182 rows · 1,030,606,724 bytes (982.86 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 100,731,166 · h: 100,680,322 · a: 100,666,321 · e: 100,452,085 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 38,554 (0.04%) · h: 255,813 (0.25%) · a: 8,014 (0.01%) · e: 100,450,801 (99.70%) (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 100,753,182 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 b710e203710b4482d404b2c93f2bfe7c7c396910589012bc7e8ffc416600dd6d
the corpus checksum ledger names this file with the same digest
joined 100,754,468 to merged 100,753,182, minus 1,286 (minus 0.0013%)
boundary drops 1,286 · 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-30T15:54:15Z 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,683,556 99,393,471 0-33 c3b15327df15606c873a42ff030659421564b481a34178e9d1c2055c9925a1a5 book 164,299 16,713,284 34-34 8b714226357b6ffbfb5c7629862384fe111df211dacf4f8bf8ddfd9f34063e66 last_trade_price 74,426 4,254,062 35-35 d9ca989bea9cbd723cb91b487c6b81296367a4191f2576024ad0b9196bec77db market_resolved 1,291 203,802 36-36 2553b732582d9528afbf224bdd832a56bd7674794aeecc087192a7daf189bf25 new_market 1,722 180,203 37-37 97541644ed8d8f1636838e331a738041966aef853c659b53d09c4168e943ae03 price_change 91,821,864 908,496,526 38-388 c6c278013f753e8b618aed11d903ecec0772fee4411cffbd128725065a3ed98a tick_size_change 6,024 215,634 389-389 05a6de08257b7c38f65ff28e14a42c7921bb9244cc1a01826e61e47a8077daae EVENT MIX count share price_change 91,821,864 91.14% best_bid_ask 8,683,556 8.62% book 164,299 0.16% last_trade_price 74,426 0.07% tick_size_change 6,024 <0.01% new_market 1,722 <0.01% market_resolved 1,291 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,683,642 8,683,556 86 79,393 PARTIAL book 164,299 164,299 0 9,220 PARTIAL last_trade_price 74,426 74,426 0 4,918 PARTIAL market_resolved 1,291 1,291 0 1,262 PARTIAL new_market 1,722 1,722 0 1,188 PARTIAL price_change 91,823,064 91,821,864 1,200 134,014 PARTIAL tick_size_change 6,024 6,024 0 1,506 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,678,115 214 37ms 48ms 426ms 20.3s 0 transport_latency_assumed best_bid_ask c 8,682,586 1,106 4ms 8ms 123ms 8.8s 0 transport_latency_assumed best_bid_ask e 8,671,475 8,671,389 44ms 109ms 1.5s 22.1s 0 transport_latency_assumed best_bid_ask h 8,681,706 10,847 12ms 20ms 174ms 47.8s 0 transport_latency_assumed book a 155,523 3,492 52ms 2.7s 2.3min 74.1d 0 book_staleness book c 154,496 1,578 7ms 24ms 1.7s 74.0d 0 book_staleness book e 153,659 153,659 70ms 5.3s 13.0min 3.1d 0 book_staleness book h 154,426 5,570 19ms 101ms 1.4s 74.1d 0 book_staleness last_trade_price a 73,825 6 51ms 2.1s 13.0s 20.3s 0 transport_latency_assumed last_trade_price c 74,398 9 9ms 38ms 221ms 5.1s 0 transport_latency_assumed last_trade_price e 72,599 72,599 65ms 4.0s 15.3s 22.2s 0 transport_latency_assumed last_trade_price h 74,338 1,812 18ms 89ms 571ms 5.2s 0 transport_latency_assumed market_resolved a 1,262 23 39ms 209ms 587ms 1.2s 0 transport_latency_assumed market_resolved c 1,262 6 4ms 9ms 419ms 1.0min 0 transport_latency_assumed market_resolved e 1,262 1,262 44ms 298ms 57.0s 1.0min 0 transport_latency_assumed market_resolved h 1,262 not meas. 13ms 42ms 57.5s 1.0min 0 transport_latency_assumed new_market a 1,188 129 203ms 17.6s 25.9s 1.4min 0 transport_latency_assumed new_market c 1,188 155 80ms 17.5s 25.7s 1.4min 0 transport_latency_assumed new_market e 1,188 1,188 218ms 16.5s 24.9s 1.0min 0 transport_latency_assumed new_market h 1,188 250 125ms 16.7s 26.5s 1.5min 0 transport_latency_assumed price_change a 91,750,384 4,150 38ms 68ms 1.5s 20.3s 0 transport_latency_assumed price_change c 91,811,212 35,700 5ms 9ms 141ms 10.0s 0 transport_latency_assumed price_change e 91,545,878 91,544,680 44ms 189ms 6.5s 22.2s 0 transport_latency_assumed price_change h 91,761,378 237,334 13ms 22ms 206ms 48.8s 0 transport_latency_assumed tick_size_change a 6,024 not meas. 38ms 48ms 304ms 672ms 0 transport_latency_assumed tick_size_change c 6,024 not meas. 4ms 9ms 195ms 793ms 0 transport_latency_assumed tick_size_change e 6,024 6,024 43ms 121ms 716ms 8.1s 0 transport_latency_assumed tick_size_change h 6,024 not meas. 13ms 20ms 100ms 1.0s 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/14/2026-08-30T14.parquet sha256sum 2026-08-30T14.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.