Hour audit: 2026-08-30T09
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-30T09 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T09:00:00.027655980+00:00 · last event 2026-08-30T09:59:59.999933820+00:00
VOLUME 95,925,887 rows · 991,348,192 bytes (945.42 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured e: 95,294,879 · h: 95,248,223 · a: 91,952,896 · c: 69,185,938 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 95,294,151 (99.34%) · h: 62,743 (0.07%) · a: 188,370 (0.20%) · c: 380,623 (0.40%) (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 95,925,887 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 67ccb8bf0863e5e76d644725503528ff304d587d6338d7225e2a19108fb4a544
the corpus checksum ledger names this file with the same digest
joined 95,926,660 to merged 95,925,887, minus 773 (minus 0.0008%)
boundary drops 773 · 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-31T14:46:52Z 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,359,637 93,073,242 0-31 985c1b46408228016952da73fa134aa1a18dc6dfc2fa653ac4c9f01446260268 book 649,207 57,949,700 32-34 18353f5e82a0b193dcb1bd796876b002a80b38ee8ccaef485b3433a106c858b0 last_trade_price 54,045 3,106,921 35-35 852e3d11c77ed04384d2d8bac63f01678f99f918d77d0c3b1a32907a33a47cbc market_resolved 534 63,658 36-36 59c98b1ae3776b6480c996af51520b6cb156a4248e936fa4b94c34a96b3fd6c5 new_market 2,164 204,526 37-37 15795455da3e4f07a0be3655835f7da5ce2942bf9da9681cb4936e5dd913f20a price_change 86,858,152 835,775,839 38-369 30c8613346651449cda2b2992e2ef7a59646ca7b97344460682c36b2bf00eb15 tick_size_change 2,148 80,104 370-370 c9f3ce04e01fe902b698d41c0d83ceb8baec9edc88a28180383049d133ab0c67 EVENT MIX count share price_change 86,858,152 90.55% best_bid_ask 8,359,637 8.71% book 649,207 0.68% last_trade_price 54,045 0.06% new_market 2,164 <0.01% tick_size_change 2,148 <0.01% market_resolved 534 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,359,691 8,359,637 54 66,156 PARTIAL book 649,247 649,207 40 172,623 PARTIAL last_trade_price 54,045 54,045 0 3,569 PARTIAL market_resolved 534 534 0 383 PARTIAL new_market 2,165 2,164 1 1,339 PARTIAL price_change 86,858,830 86,858,152 678 126,608 PARTIAL tick_size_change 2,148 2,148 0 537 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,014,671 320 38ms 46ms 359ms 22.4s 0 transport_latency_assumed best_bid_ask c 6,050,732 1,719 24ms 35ms 126ms 6.6s 0 transport_latency_assumed best_bid_ask e 8,354,295 8,354,241 42ms 75ms 651ms 30.4s 0 transport_latency_assumed best_bid_ask h 8,350,847 3,357 11ms 16ms 221ms 23.7s 0 transport_latency_assumed book a 456,022 183,605 1.1min 8.5h 27.8d 92.5d 0 book_staleness book c 428,142 340,379 1.3min 10.0h 27.9d 92.5d 0 book_staleness book e 120,187 120,187 52ms 3.8s 1.4d 33.0d 0 book_staleness book h 113,606 5,036 17ms 315ms 29.0min 73.8d 0 book_staleness last_trade_price a 51,867 4 47ms 653ms 5.3s 22.3s 0 transport_latency_assumed last_trade_price c 40,340 102 32ms 58ms 247ms 4.8s 0 transport_latency_assumed last_trade_price e 53,605 53,605 53ms 1.1s 7.1s 30.4s 0 transport_latency_assumed last_trade_price h 53,046 334 17ms 130ms 1.6s 8.6s 0 transport_latency_assumed market_resolved a 374 13 40ms 429ms 4.0min 4.0min 0 transport_latency_assumed market_resolved c 383 139 33ms 13.7min 20.9min 20.9min 0 transport_latency_assumed market_resolved e 377 377 43ms 717ms 53.3s 1.0min 0 transport_latency_assumed market_resolved h 377 5 12ms 87ms 60.0s 1.0min 0 transport_latency_assumed new_market a 1,331 182 250ms 18.1s 25.6s 4.3min 0 transport_latency_assumed new_market c 1,339 186 74ms 19.3s 15.3min 18.2min 0 transport_latency_assumed new_market e 1,331 1,331 113ms 17.7s 25.6s 1.1min 0 transport_latency_assumed new_market h 1,331 465 131ms 18.9s 24.8s 1.0min 0 transport_latency_assumed price_change a 83,426,583 4,246 38ms 55ms 540ms 22.4s 0 transport_latency_assumed price_change c 62,663,498 38,098 25ms 35ms 147ms 6.6s 0 transport_latency_assumed price_change e 86,762,936 86,762,262 42ms 98ms 1.2s 30.4s 0 transport_latency_assumed price_change h 86,726,868 53,546 12ms 18ms 266ms 27.5s 0 transport_latency_assumed tick_size_change a 2,048 not meas. 39ms 51ms 186ms 295ms 0 transport_latency_assumed tick_size_change c 1,504 not meas. 28ms 36ms 59ms 291ms 0 transport_latency_assumed tick_size_change e 2,148 2,148 42ms 119ms 343ms 807ms 0 transport_latency_assumed tick_size_change h 2,148 not meas. 12ms 22ms 173ms 388ms 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/09/2026-08-30T09.parquet sha256sum 2026-08-30T09.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.