Hour audit: 2026-08-30T12
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-30T12 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T12:00:00.033209870+00:00 · last event 2026-08-30T12:59:59.999991787+00:00
VOLUME 101,762,766 rows · 1,072,796,459 bytes (1023.10 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 101,390,368 · h: 101,311,344 · e: 100,567,743 · a: 97,426,038 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 71,113 (0.07%) · h: 773,453 (0.76%) · e: 100,566,897 (98.82%) · a: 351,303 (0.35%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,762,766 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 b9d800959d2c7a80bc3b522018acefc9d5ba5bd01dd28be538d4311103d0cd46
the corpus checksum ledger names this file with the same digest
joined 101,763,624 to merged 101,762,766, minus 858 (minus 0.0008%)
boundary drops 858 · 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-30T15:10:36Z 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,342,252 95,147,856 0-31 21fdbfe3ddcdbfbe3712952d7b0dd4271dc01540c7a9a60597ffe2e48703b0c8 book 515,067 54,248,269 32-33 750e75b1c97e655435aa7c5b8a88d6683f5d85c77e823e26aeae4fc99839825e last_trade_price 73,535 4,136,092 34-34 7b5dd017f33ffef36486c0e2019e16d64d868be8e618fe9bb1d077d0e4926e23 market_resolved 681 94,864 35-35 a476c46818a218db2924a44175bdfdc55051a21e87bfa8fdbd08c41bf96a03cb new_market 2,411 241,936 36-36 d917d3f03e82f2565f7d3cc4b2acc2af789c933c1839061f1e3c3d49f50a1177 price_change 92,823,804 917,584,187 37-391 78d94b042603fd7041c3a4eb128faa7af641d708eb47bf4ee886ef868a0791d4 tick_size_change 5,016 183,753 392-392 2f93c1826ac33fba2c2557649402a39a17db5304b8d12018245986b8737529d2 EVENT MIX count share price_change 92,823,804 91.22% best_bid_ask 8,342,252 8.20% book 515,067 0.51% last_trade_price 73,535 0.07% tick_size_change 5,016 <0.01% new_market 2,411 <0.01% market_resolved 681 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,342,320 8,342,252 68 72,267 PARTIAL book 515,081 515,067 14 174,484 PARTIAL last_trade_price 73,535 73,535 0 4,444 PARTIAL market_resolved 681 681 0 585 PARTIAL new_market 2,411 2,411 0 1,586 PARTIAL price_change 92,824,580 92,823,804 776 131,171 PARTIAL tick_size_change 5,016 5,016 0 1,254 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,996,412 124 37ms 57ms 535ms 28.6s 0 transport_latency_assumed best_bid_ask c 8,341,196 1,212 5ms 9ms 153ms 6.0s 0 transport_latency_assumed best_bid_ask e 8,313,999 8,313,931 45ms 128ms 2.2s 29.3s 0 transport_latency_assumed best_bid_ask h 8,340,508 26,985 12ms 23ms 263ms 51.4s 0 transport_latency_assumed book a 494,386 347,990 50.4s 6.8h 26.7d 92.6d 0 book_staleness book c 154,337 2,133 8ms 31ms 3.8s 73.9d 0 book_staleness book e 154,300 154,298 117ms 8.5s 1.4h 14.9d 0 book_staleness book h 153,342 10,646 21ms 135ms 2.1s 74.0d 0 book_staleness last_trade_price a 69,262 5 56ms 1.9s 12.7s 28.6s 0 transport_latency_assumed last_trade_price c 73,508 7 10ms 42ms 244ms 5.0s 0 transport_latency_assumed last_trade_price e 69,053 69,053 78ms 5.1s 15.1s 29.2s 0 transport_latency_assumed last_trade_price h 73,509 4,470 19ms 115ms 800ms 50.0s 0 transport_latency_assumed market_resolved a 575 96 40ms 56.4s 5.0min 5.1min 0 transport_latency_assumed market_resolved c 585 not meas. 5ms 23ms 57.3s 59.9s 0 transport_latency_assumed market_resolved e 585 585 46ms 714ms 54.2s 56.5s 0 transport_latency_assumed market_resolved h 585 not meas. 13ms 115ms 53.6s 55.9s 0 transport_latency_assumed new_market a 1,586 108 247ms 22.5s 33.1s 1.2min 0 transport_latency_assumed new_market c 1,586 331 110ms 19.1s 29.5s 1.1min 0 transport_latency_assumed new_market e 1,586 1,586 222ms 22.0s 32.7s 1.9min 0 transport_latency_assumed new_market h 1,586 386 103ms 22.0s 42.9s 1.4min 0 transport_latency_assumed price_change a 88,859,301 2,980 38ms 90ms 1.8s 28.7s 0 transport_latency_assumed price_change c 92,814,140 67,430 5ms 10ms 187ms 6.6s 0 transport_latency_assumed price_change e 92,023,224 92,022,448 45ms 224ms 6.8s 29.3s 0 transport_latency_assumed price_change h 92,736,798 730,946 13ms 25ms 287ms 51.5s 0 transport_latency_assumed tick_size_change a 4,516 not meas. 37ms 42ms 215ms 638ms 0 transport_latency_assumed tick_size_change c 5,016 not meas. 5ms 8ms 79ms 435ms 0 transport_latency_assumed tick_size_change e 4,996 4,996 45ms 117ms 523ms 6.7s 0 transport_latency_assumed tick_size_change h 5,016 20 13ms 19ms 117ms 934ms 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/12/2026-08-30T12.parquet sha256sum 2026-08-30T12.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.