Hour audit: 2026-08-30T05
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-30T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T05:00:00.027586164+00:00 · last event 2026-08-30T05:59:59.999930325+00:00
VOLUME 88,631,154 rows · 853,382,336 bytes (813.85 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured a: 88,592,683 · c: 88,592,300 · h: 88,580,735 · e: 88,561,510 (each machine's own feed; these overlap and do not sum to the file)
supplied a: 7,015 (0.01%) · c: 19,963 (0.02%) · h: 43,962 (0.05%) · e: 88,560,214 (99.92%) (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 88,631,154 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 6f0686abb97fd0959a12417654249960caf9bcfd7342ee44b98db3ce382a8aac
the corpus checksum ledger names this file with the same digest
joined 88,632,470 to merged 88,631,154, minus 1,316 (minus 0.0015%)
boundary drops 1,316 · 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:35:53Z 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,452,488 92,466,299 0-32 1b53652711568ed18baa70faeb65efe37e7640a952a1e6dd7eaaff523de5f018 book 110,280 10,856,841 33-33 0096715e4f38aec15553c5a72ceec049438698897171b851608c8bf8680a3dad last_trade_price 41,980 2,432,778 34-34 e627273755913c8cdb43eae8226fbd5975ad9c19a910fdc22da965a651f0382d market_resolved 1,105 171,988 35-35 77b52274b9d60d08070e716258f6499304274f56f1f4653614c3fac4bccc3711 new_market 1,625 160,956 36-36 d2bdb4c607b5ba1e7ece2a341978a0c6e26b0df3b665fd7a4e19e53ad632e913 price_change 80,020,948 746,178,416 37-342 0b39f920a795d2116e88f9ef9e234d8b256c14769cb689ec1a372a0280a9331c tick_size_change 2,728 100,765 343-343 718ccc1827e1fbcb1205506707fec5d191253e88416cd36393984fb39089659a EVENT MIX count share price_change 80,020,948 90.29% best_bid_ask 8,452,488 9.54% book 110,280 0.12% last_trade_price 41,980 0.05% tick_size_change 2,728 <0.01% new_market 1,625 <0.01% market_resolved 1,105 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,452,604 8,452,488 116 68,153 PARTIAL book 110,312 110,280 32 13,999 PARTIAL last_trade_price 41,980 41,980 0 3,068 PARTIAL market_resolved 1,105 1,105 0 1,067 PARTIAL new_market 1,625 1,625 0 1,074 PARTIAL price_change 80,022,116 80,020,948 1,168 127,953 PARTIAL tick_size_change 2,728 2,728 0 682 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,449,510 64 39ms 45ms 217ms 5.2s 0 transport_latency_assumed best_bid_ask c 8,451,103 1,016 4ms 6ms 58ms 1.6s 0 transport_latency_assumed best_bid_ask e 8,448,495 8,448,381 43ms 71ms 508ms 13.9s 0 transport_latency_assumed best_bid_ask h 8,450,764 3,027 12ms 16ms 117ms 42.9s 0 transport_latency_assumed book a 90,659 3,709 43ms 737ms 32.0min 73.8d 0 book_staleness book c 92,903 6,496 6ms 64ms 5.7h 73.7d 0 book_staleness book e 95,256 95,236 58ms 5.9s 2.0d 92.3d 0 book_staleness book h 90,568 4,839 17ms 116ms 25.2min 73.7d 0 book_staleness last_trade_price a 41,928 3 47ms 366ms 3.0s 5.3s 0 transport_latency_assumed last_trade_price c 41,887 5 9ms 33ms 142ms 4.8s 0 transport_latency_assumed last_trade_price e 41,722 41,722 57ms 1.4s 7.9s 13.9s 0 transport_latency_assumed last_trade_price h 41,962 250 17ms 58ms 460ms 8.5s 0 transport_latency_assumed market_resolved a 1,067 36 41ms 221ms 536ms 1.1s 0 transport_latency_assumed market_resolved c 1,067 2 4ms 6ms 234ms 407ms 0 transport_latency_assumed market_resolved e 1,067 1,067 44ms 203ms 2.9s 57.8s 0 transport_latency_assumed market_resolved h 1,067 not meas. 12ms 49ms 409ms 58.4s 0 transport_latency_assumed new_market a 1,074 21 208ms 22.2s 1.6min 1.7min 0 transport_latency_assumed new_market c 1,074 154 76ms 23.2s 1.7min 2.5min 0 transport_latency_assumed new_market e 1,074 1,074 215ms 22.4s 1.6min 1.7min 0 transport_latency_assumed new_market h 1,074 376 149ms 31.5s 1.6min 1.6min 0 transport_latency_assumed price_change a 80,005,717 3,182 39ms 47ms 334ms 5.3s 0 transport_latency_assumed price_change c 80,001,538 12,290 4ms 6ms 66ms 1.6s 0 transport_latency_assumed price_change e 79,971,168 79,970,006 44ms 87ms 1.0s 13.9s 0 transport_latency_assumed price_change h 79,992,572 35,470 12ms 17ms 139ms 43.5s 0 transport_latency_assumed tick_size_change a 2,728 not meas. 39ms 53ms 561ms 690ms 0 transport_latency_assumed tick_size_change c 2,728 not meas. 4ms 6ms 106ms 399ms 0 transport_latency_assumed tick_size_change e 2,728 2,728 44ms 123ms 1.3s 5.0s 0 transport_latency_assumed tick_size_change h 2,728 not meas. 12ms 19ms 325ms 616ms 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/05/2026-08-30T05.parquet sha256sum 2026-08-30T05.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.