Hour audit: 2026-08-31T06
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-31T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T06:00:00.037184024+00:00 · last event 2026-08-31T06:59:59.131530765+00:00
VOLUME 34,771,810 rows · 387,254,771 bytes (369.31 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 34,568,522 · h: 34,537,037 · e: 34,534,627 · a: 34,515,314 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 27,411 (0.08%) · h: 203,287 (0.58%) · e: 34,534,002 (99.32%) · a: 7,110 (0.02%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 34,771,810 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 d68a83281b03095d05e54fb7e6de2cdb883b12d38731b29215dfbf9cc1e92380
the corpus checksum ledger names this file with the same digest
joined 34,772,443 to merged 34,771,810, minus 633 (minus 0.0018%)
boundary drops 633 · 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-31T07:41:47Z 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 an incident recorded by the venue intersects this hour: Venue stopped trading for four hours, 2026-08-31T06:30Z to 2026-08-31T10:47ZThe 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 3,151,114 44,479,047 0-12 1a6f2d4eccaa161549eeda166f3049b51174b2b797d35a10b7ae87b0b44e00e1 book 279,543 27,530,010 13-14 c993bb6749161b67612a3273748527014631c49b6b7e347c8ffac9862fa94f47 last_trade_price 32,175 1,831,155 15-15 9b16df2889de7e243df936ff0a9f18430e7322ca834d26db5a33136a09128aaf market_resolved 602 99,050 16-16 130bf4ba6a1b7e2a9434b33d90d71a2615292db75c24623e0bcda12d3085dd00 new_market 1,924 180,629 17-17 051e892a3679edeb5fc05dbea02a964248b9f133e9b056896350b837914453d0 price_change 31,305,456 312,687,402 18-137 52657b9bafcd4c37f9e5985e59e655d17c77523216fe95b057aed783fd0b69d1 tick_size_change 996 37,021 138-138 fa72936a264b4a8094c089ffd05941909321a1a0593c458fd0d59236adce6f7e EVENT MIX count share price_change 31,305,456 90.03% best_bid_ask 3,151,114 9.06% book 279,543 0.80% last_trade_price 32,175 0.09% new_market 1,924 <0.01% tick_size_change 996 <0.01% market_resolved 602 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 3,151,176 3,151,114 62 95,527 PARTIAL book 279,545 279,543 2 89,989 PARTIAL last_trade_price 32,176 32,175 1 1,917 PARTIAL market_resolved 602 602 0 593 PARTIAL new_market 1,924 1,924 0 1,183 PARTIAL price_change 31,306,024 31,305,456 568 140,681 PARTIAL tick_size_change 996 996 0 249 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 3,148,412 130 39ms 57ms 678ms 25.1s 0 transport_latency_assumed best_bid_ask c 3,150,562 638 4ms 7ms 178ms 5.0s 0 transport_latency_assumed best_bid_ask e 3,143,824 3,143,762 43ms 130ms 3.6s 37.5s 0 transport_latency_assumed best_bid_ask h 3,149,838 6,584 12ms 19ms 263ms 33.6s 0 transport_latency_assumed book a 75,603 5,166 111ms 43.6s 3.1d 74.9d 0 book_staleness book c 84,404 11,212 8ms 18.0min 15.5d 74.9d 0 book_staleness book e 254,510 254,508 5.7min 5.4h 28.8d 93.3d 0 book_staleness book h 77,678 8,657 23ms 3.6min 3.1d 74.9d 0 book_staleness last_trade_price a 31,856 3 64ms 2.6s 8.4s 25.0s 0 transport_latency_assumed last_trade_price c 32,156 6 9ms 41ms 239ms 4.9s 0 transport_latency_assumed last_trade_price e 30,887 30,886 152ms 6.9s 14.0s 36.5s 0 transport_latency_assumed last_trade_price h 32,156 1,280 19ms 131ms 941ms 9.5s 0 transport_latency_assumed market_resolved a 593 not meas. 42ms 328ms 59.0s 1.0min 0 transport_latency_assumed market_resolved c 593 9 4ms 6ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 593 593 44ms 373ms 58.1s 1.0min 0 transport_latency_assumed market_resolved h 593 not meas. 13ms 49ms 57.2s 1.0min 0 transport_latency_assumed new_market a 1,183 185 266ms 21.7s 45.2s 56.8s 0 transport_latency_assumed new_market c 1,183 117 97ms 23.4s 46.1s 1.0min 0 transport_latency_assumed new_market e 1,183 1,183 307ms 17.7s 26.7s 1.4min 0 transport_latency_assumed new_market h 1,183 439 162ms 22.2s 45.9s 1.1min 0 transport_latency_assumed price_change a 31,256,671 1,626 40ms 98ms 2.1s 25.1s 0 transport_latency_assumed price_change c 31,298,628 15,429 4ms 8ms 213ms 6.7s 0 transport_latency_assumed price_change e 31,102,634 31,102,074 43ms 242ms 6.9s 37.6s 0 transport_latency_assumed price_change h 31,274,593 186,327 12ms 22ms 296ms 34.8s 0 transport_latency_assumed tick_size_change a 996 not meas. 39ms 43ms 104ms 115ms 0 transport_latency_assumed tick_size_change c 996 not meas. 4ms 6ms 9ms 41ms 0 transport_latency_assumed tick_size_change e 996 996 43ms 119ms 1.5s 3.3s 0 transport_latency_assumed tick_size_change h 996 not meas. 12ms 14ms 27ms 31ms 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-31/06/2026-08-31T06.parquet sha256sum 2026-08-31T06.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.