Hour audit: 2026-08-30T06
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-30T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T06:00:00.028123941+00:00 · last event 2026-08-30T06:59:59.999950992+00:00
VOLUME 86,723,187 rows · 837,755,272 bytes (798.95 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 86,637,119 · a: 86,629,582 · h: 86,624,499 · e: 86,484,659 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 35,209 (0.04%) · a: 19,706 (0.02%) · h: 184,643 (0.21%) · e: 86,483,629 (99.72%) (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 86,723,187 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 fc4d4eedb806e045f3b3b6a31f352a7621b644cdf3e22d9eaa8d98ee5eaddcae
the corpus checksum ledger names this file with the same digest
joined 86,724,221 to merged 86,723,187, minus 1,034 (minus 0.0012%)
boundary drops 1,034 · 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-31T13:53:12Z 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,571,770 93,205,494 0-32 81813977b4cc9c865620f74caec497b57a7d99790ae2e7b0342a01ddf8da13cc book 187,217 19,075,734 33-33 a69b0af8d097324be6aea274213530bd360eb4c9853ca2827665ad6bc6cdad98 last_trade_price 43,822 2,608,556 34-34 4689133bc0a6f0512712845630d7b15c07c87a4d9d1e2107261402fafc92c610 market_resolved 1,062 170,768 35-35 5d6685c94809dafb4545081e7dc26b6e41b0657d89a0663ab71eb262a443cbc2 new_market 620 63,587 36-36 801f587923fc2fbdaa15355d72ca96d65967da13e50fa09aa62a9c1f9e428bc6 price_change 77,916,832 721,571,361 37-334 da00233c2217c3558e112d379c31260a99c46b6c71be253fe10793d241c132e6 tick_size_change 1,864 68,895 335-335 72421bddb27e7a82eaa041f827ed78fd7a9ff273cc1c3a603b7d22bc75dc98b1 EVENT MIX count share price_change 77,916,832 89.85% best_bid_ask 8,571,770 9.88% book 187,217 0.22% last_trade_price 43,822 0.05% tick_size_change 1,864 <0.01% market_resolved 1,062 <0.01% new_market 620 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,571,896 8,571,770 126 66,871 PARTIAL book 187,221 187,217 4 47,623 PARTIAL last_trade_price 43,822 43,822 0 3,287 PARTIAL market_resolved 1,062 1,062 0 1,047 PARTIAL new_market 620 620 0 416 PARTIAL price_change 77,917,736 77,916,832 904 133,496 PARTIAL tick_size_change 1,864 1,864 0 466 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,570,170 30 33ms 39ms 157ms 8.4s 0 transport_latency_assumed best_bid_ask c 8,571,516 600 4ms 6ms 30ms 5.1s 0 transport_latency_assumed best_bid_ask e 8,563,213 8,563,087 42ms 65ms 636ms 19.9s 0 transport_latency_assumed best_bid_ask h 8,570,218 8,053 12ms 14ms 64ms 6.4s 0 transport_latency_assumed book a 111,173 18,415 74ms 2.0min 7.7d 73.8d 0 book_staleness book c 111,394 19,588 7ms 2.1min 13.5d 92.3d 0 book_staleness book e 111,214 111,212 125ms 3.9min 18.5d 73.8d 0 book_staleness book h 126,513 38,002 26ms 7.0min 21.7d 92.3d 0 book_staleness last_trade_price a 43,774 5 45ms 1.1s 5.3s 8.5s 0 transport_latency_assumed last_trade_price c 43,809 63 9ms 32ms 133ms 5.0s 0 transport_latency_assumed last_trade_price e 42,669 42,669 61ms 2.6s 10.9s 19.9s 0 transport_latency_assumed last_trade_price h 43,615 1,085 17ms 94ms 941ms 5.0s 0 transport_latency_assumed market_resolved a 1,047 1 34ms 171ms 44.8s 57.6s 0 transport_latency_assumed market_resolved c 1,047 4 4ms 6ms 38.8s 52.4s 0 transport_latency_assumed market_resolved e 1,047 1,047 42ms 163ms 48.3s 1.0min 0 transport_latency_assumed market_resolved h 1,047 10 12ms 37ms 48.2s 1.0min 0 transport_latency_assumed new_market a 416 55 189ms 14.3s 21.8s 26.3s 0 transport_latency_assumed new_market c 416 44 52ms 16.3s 22.3s 1.0min 0 transport_latency_assumed new_market e 416 416 188ms 13.7s 23.8s 2.1min 0 transport_latency_assumed new_market h 416 105 85ms 16.9s 23.2s 1.6min 0 transport_latency_assumed price_change a 77,901,138 1,200 33ms 40ms 292ms 8.4s 0 transport_latency_assumed price_change c 77,907,073 14,910 4ms 6ms 40ms 6.5s 0 transport_latency_assumed price_change e 77,764,236 77,763,334 42ms 85ms 1.2s 19.9s 0 transport_latency_assumed price_change h 77,880,826 137,388 12ms 15ms 97ms 6.8s 0 transport_latency_assumed tick_size_change a 1,864 not meas. 33ms 38ms 97ms 131ms 0 transport_latency_assumed tick_size_change c 1,864 not meas. 4ms 6ms 13ms 22ms 0 transport_latency_assumed tick_size_change e 1,864 1,864 42ms 116ms 329ms 5.4s 0 transport_latency_assumed tick_size_change h 1,864 not meas. 12ms 13ms 47ms 184ms 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/06/2026-08-30T06.parquet sha256sum 2026-08-30T06.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.