Hour audit: 2026-08-29T22
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-29T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-29T22:00:00.016099901+00:00 · last event 2026-08-29T22:59:59.999960746+00:00
VOLUME 107,926,445 rows · 1,112,061,206 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 107,268,138 · e: 104,527,593 · a: 101,808,745 · c: 95,919,519 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,755,554 (2.55%) · e: 104,526,428 (96.85%) · a: 244,490 (0.23%) · c: 399,973 (0.37%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,926,445 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 0a9348fd5b7e573bab7b7b37b938db0dfbe992e0659e6cf6aca8d44305019d47
the corpus checksum ledger names this file with the same digest
joined 107,927,697 to merged 107,926,445, minus 1,252 (minus 0.0012%)
boundary drops 1,252 · 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-30T04:30:38Z 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 9,717,612 107,680,557 0-37 0dd1a951df8284d5b9519ba4f0acff0ecd64eb5a18ec6bee934f1c1fd626591f book 717,417 60,049,924 38-40 0b9d864244e63f013a67d7352c24105851945460c27242d27d8cb3945588ef6a last_trade_price 53,809 3,113,762 41-41 a78d29972220cd51df0165114485efbadc1a832d78870a45cb351ce097b2deb8 market_resolved 3,183 452,145 42-42 72347129350ee01370b8d53b49768d64998883b1cd0a5c7a5298ca43c477b7e0 new_market 1,270 122,267 43-43 200fd92d07106fbbcdb7276ad4285cae655f5a8fead5d25a4a3656389e08ecc5 price_change 97,429,134 939,265,936 44-415 afd346bf02fea1f580a209bbb0ea7488360242777996ab94249a9255dab0b99f tick_size_change 4,020 147,277 416-416 ef747a88fc871507390f0780bbb42209c71c576a148723185901235d537c30d9 EVENT MIX count share price_change 97,429,134 90.27% best_bid_ask 9,717,612 9.00% book 717,417 0.66% last_trade_price 53,809 0.05% tick_size_change 4,020 <0.01% market_resolved 3,183 <0.01% new_market 1,270 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,717,685 9,717,612 73 70,675 PARTIAL book 717,422 717,417 5 177,067 PARTIAL last_trade_price 53,809 53,809 0 3,809 PARTIAL market_resolved 3,183 3,183 0 2,776 PARTIAL new_market 1,270 1,270 0 775 PARTIAL price_change 97,430,308 97,429,134 1,174 134,492 PARTIAL tick_size_change 4,020 4,020 0 1,005 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,230,268 96 39ms 46ms 215ms 11.0s 0 transport_latency_assumed best_bid_ask c 8,623,713 340 1ms 5ms 38ms 6.8s 0 transport_latency_assumed best_bid_ask e 9,544,140 9,544,076 44ms 81ms 557ms 18.0s 0 transport_latency_assumed best_bid_ask h 9,716,622 173,100 12ms 17ms 103ms 51.8s 0 transport_latency_assumed book a 459,255 242,245 1.2min 3.2h 27.3d 92.0d 0 book_staleness book c 453,184 353,670 1.2min 3.3h 27.3d 92.0d 0 book_staleness book e 113,728 113,727 59ms 2.7s 8.3min 21.5h 0 book_staleness book h 117,765 7,775 18ms 257ms 2.4h 73.5d 0 book_staleness last_trade_price a 49,464 3 49ms 947ms 7.1s 11.0s 0 transport_latency_assumed last_trade_price c 46,784 1 6ms 32ms 170ms 4.9s 0 transport_latency_assumed last_trade_price e 53,583 53,583 61ms 2.0s 10.5s 18.0s 0 transport_latency_assumed last_trade_price h 53,714 222 17ms 78ms 644ms 51.7s 0 transport_latency_assumed market_resolved a 2,683 82 41ms 173ms 4.1min 4.4min 0 transport_latency_assumed market_resolved c 2,737 282 1ms 38.4s 8.5min 8.7min 0 transport_latency_assumed market_resolved e 2,716 2,716 45ms 185ms 1.0min 2.5min 0 transport_latency_assumed market_resolved h 2,776 103 12ms 34ms 208ms 877ms 0 transport_latency_assumed new_market a 774 6 202ms 16.8s 25.4s 3.7min 0 transport_latency_assumed new_market c 832 212 187ms 5.0min 10.0min 36.9min 0 transport_latency_assumed new_market e 775 775 226ms 17.0s 25.3s 43.7min 0 transport_latency_assumed new_market h 775 277 107ms 14.1s 21.1s 31.2s 0 transport_latency_assumed price_change a 92,062,685 2,058 40ms 56ms 442ms 11.0s 0 transport_latency_assumed price_change c 86,788,857 45,468 2ms 5ms 46ms 11.1s 0 transport_latency_assumed price_change e 94,808,691 94,807,591 44ms 114ms 1.8s 18.1s 0 transport_latency_assumed price_change h 97,372,466 2,574,017 12ms 19ms 129ms 53.1s 0 transport_latency_assumed tick_size_change a 3,616 not meas. 39ms 45ms 108ms 2.7s 0 transport_latency_assumed tick_size_change c 3,412 not meas. 2ms 5ms 23ms 78ms 0 transport_latency_assumed tick_size_change e 3,960 3,960 45ms 96ms 209ms 435ms 0 transport_latency_assumed tick_size_change h 4,020 60 12ms 17ms 62ms 242ms 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-29/22/2026-08-29T22.parquet sha256sum 2026-08-29T22.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.