Hour audit: 2026-08-30T21
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-30T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T21:00:00.033027040+00:00 · last event 2026-08-30T21:59:59.999961315+00:00
VOLUME 97,839,121 rows · 1,020,984,364 bytes (973.69 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 97,243,996 · e: 96,736,957 · a: 93,053,524 · c: 67,752,330 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 557,562 (0.57%) · e: 96,735,684 (98.87%) · a: 209,107 (0.21%) · c: 336,768 (0.34%) (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 97,839,121 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 9f0c3f4bce064ed3e99af6fe43ee63ca118d17c2adc3b7877fc06072e5399e6c
the corpus checksum ledger names this file with the same digest
joined 97,840,432 to merged 97,839,121, minus 1,311 (minus 0.0013%)
boundary drops 1,311 · 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-30T23:14:27Z 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 7,547,290 86,369,884 0-28 00f926a18867ea7f8da6bb2063804cff2d06f081b472f0ff595589d6aa24bb85 book 726,935 61,714,085 29-31 57b89bf71340ad3eb58222820d28c45daaa410e1bc19b28f584c1b2666df40df last_trade_price 68,901 3,833,175 32-32 367d5d8670b37286696a06274d13b921a65ff153608fc1cc19d00295b90eec2b market_resolved 3,975 505,950 33-33 5b90200d8ed2d3b7fb802138440d8cc0c315b515d93e453f7f9b3ede5f1a2186 new_market 2,172 209,492 34-34 ae41431a2c29106eaa0070f4d517820962338a65547a3b002b6e7deaa033e515 price_change 89,485,444 867,074,606 35-376 ac4ef732eb114a99490f93e9450392aa3c99d2ede12826dc92dcd0b24e3646fe tick_size_change 4,404 161,858 377-377 1b4c4d3847075f19fd8c02ab247d330fc2e910c55b920db8bd3731b413534bda EVENT MIX count share price_change 89,485,444 91.46% best_bid_ask 7,547,290 7.71% book 726,935 0.74% last_trade_price 68,901 0.07% tick_size_change 4,404 <0.01% market_resolved 3,975 <0.01% new_market 2,172 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,547,436 7,547,290 146 70,737 PARTIAL book 726,971 726,935 36 170,660 PARTIAL last_trade_price 68,906 68,901 5 3,879 PARTIAL market_resolved 3,975 3,975 0 3,126 PARTIAL new_market 2,172 2,172 0 1,355 PARTIAL price_change 89,486,568 89,485,444 1,124 121,660 PARTIAL tick_size_change 4,404 4,404 0 1,101 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,190,448 234 34ms 54ms 455ms 21.2s 0 transport_latency_assumed best_bid_ask c 5,094,289 656 2ms 7ms 157ms 6.4s 0 transport_latency_assumed best_bid_ask e 7,535,352 7,535,206 42ms 126ms 2.1s 28.1s 0 transport_latency_assumed best_bid_ask h 7,543,803 11,194 12ms 20ms 209ms 13.9s 0 transport_latency_assumed book a 477,051 202,657 54.0s 2.8h 27.3d 93.0d 0 book_staleness book c 440,915 318,630 1.3min 3.0h 28.4d 93.0d 0 book_staleness book e 144,831 144,805 97ms 5.1s 9.2min 14.2d 0 book_staleness book h 201,006 60,843 29ms 20.3min 22.2d 91.4d 0 book_staleness last_trade_price a 64,824 5 54ms 1.6s 7.7s 21.2s 0 transport_latency_assumed last_trade_price c 48,533 7 8ms 42ms 246ms 5.0s 0 transport_latency_assumed last_trade_price e 67,640 67,635 77ms 4.2s 19.6s 28.1s 0 transport_latency_assumed last_trade_price h 68,856 1,254 18ms 101ms 543ms 7.5s 0 transport_latency_assumed market_resolved a 3,126 15 38ms 281ms 4.5min 4.8min 0 transport_latency_assumed market_resolved c 3,160 834 4ms 15.3min 20.3min 20.8min 0 transport_latency_assumed market_resolved e 3,125 3,125 45ms 270ms 1.4s 55.7s 0 transport_latency_assumed market_resolved h 3,126 1 13ms 45ms 435ms 57.1s 0 transport_latency_assumed new_market a 1,355 74 211ms 18.9s 38.9s 14.3min 0 transport_latency_assumed new_market c 1,358 285 230ms 8.8min 15.3min 25.4min 0 transport_latency_assumed new_market e 1,355 1,355 238ms 20.9s 35.4s 18.6min 0 transport_latency_assumed new_market h 1,355 458 122ms 17.6s 28.0s 11.4min 0 transport_latency_assumed price_change a 85,312,516 6,122 35ms 81ms 1.5s 21.2s 0 transport_latency_assumed price_change c 62,160,871 16,356 2ms 8ms 168ms 6.8s 0 transport_latency_assumed price_change e 88,980,250 88,979,154 42ms 178ms 4.9s 28.2s 0 transport_latency_assumed price_change h 89,421,446 483,812 12ms 22ms 235ms 14.8s 0 transport_latency_assumed tick_size_change a 4,204 not meas. 35ms 65ms 455ms 1.2s 0 transport_latency_assumed tick_size_change c 3,204 not meas. 3ms 12ms 283ms 691ms 0 transport_latency_assumed tick_size_change e 4,404 4,404 42ms 122ms 702ms 6.3s 0 transport_latency_assumed tick_size_change h 4,404 not meas. 12ms 24ms 257ms 792ms 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/21/2026-08-30T21.parquet sha256sum 2026-08-30T21.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.