Hour audit: 2026-08-31T05
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-31T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T05:00:00.038821270+00:00 · last event 2026-08-31T05:59:59.999972024+00:00
VOLUME 67,017,001 rows · 677,168,959 bytes (645.80 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 66,972,590 · h: 66,956,520 · a: 66,900,923 · e: 66,681,803 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 25,687 (0.04%) · h: 302,754 (0.45%) · a: 7,551 (0.01%) · e: 66,681,009 (99.50%) (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 67,017,001 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 61accc3c07e94df1235fa69372f6a50a6dca576cff16b64feff6c117b4393608
the corpus checksum ledger names this file with the same digest
joined 67,017,801 to merged 67,017,001, minus 800 (minus 0.0012%)
boundary drops 800 · 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-31T06:47:28Z 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 6,301,534 75,146,699 0-24 b157249575ca60a0f01f69a1e8e160ce7dc950391332c4019fc0a6ddecc1eb5e book 170,728 15,809,031 25-25 ab84cf19346830995ea13548f21940afac7af4ef440f87e785145f0b9f5c95fb last_trade_price 62,943 3,470,168 26-26 dd557ec8387f5316ea30633882209038b99ec39f8f13e913e2aba933dd704e43 market_resolved 894 146,722 27-27 ba293fd2ce6a582b45607bdbfd430a32f23e155d601e48c8d7bb707090c058c4 new_market 1,394 138,458 28-28 25da342f0546809d46b65b1395c7b8f79d1ac3dcc7ffb7ca01eb608e8a97c72b price_change 60,477,444 581,611,147 29-259 413779676c37d99bb0e8a004419165049e04ab17dcdfdb99b922a060c3620adb tick_size_change 2,064 77,040 260-260 dd16d09c2376e14cbc7cf199d16e6dd12517c4222db5fb4d28a5cd29bf129e15 EVENT MIX count share price_change 60,477,444 90.24% best_bid_ask 6,301,534 9.40% book 170,728 0.25% last_trade_price 62,943 0.09% tick_size_change 2,064 <0.01% new_market 1,394 <0.01% market_resolved 894 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,301,604 6,301,534 70 92,457 PARTIAL book 170,730 170,728 2 21,007 PARTIAL last_trade_price 62,943 62,943 0 2,840 PARTIAL market_resolved 894 894 0 890 PARTIAL new_market 1,394 1,394 0 905 PARTIAL price_change 60,478,172 60,477,444 728 140,902 PARTIAL tick_size_change 2,064 2,064 0 516 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,297,931 146 38ms 51ms 429ms 15.3s 0 transport_latency_assumed best_bid_ask c 6,300,874 586 4ms 7ms 80ms 6.1s 0 transport_latency_assumed best_bid_ask e 6,292,778 6,292,708 43ms 121ms 2.6s 26.0s 0 transport_latency_assumed best_bid_ask h 6,300,428 8,094 12ms 18ms 148ms 36.2s 0 transport_latency_assumed book a 135,646 5,987 90ms 3.4s 1.8h 74.8d 0 book_staleness book c 136,550 5,935 7ms 37ms 2.4h 74.8d 0 book_staleness book e 133,837 133,837 157ms 8.2s 3.0h 32.5d 0 book_staleness book h 152,000 24,969 23ms 2.2min 7.5d 93.3d 0 book_staleness last_trade_price a 62,435 6 64ms 2.1s 8.0s 15.4s 0 transport_latency_assumed last_trade_price c 62,895 14 9ms 35ms 163ms 5.0s 0 transport_latency_assumed last_trade_price e 61,441 61,441 117ms 5.6s 14.0s 26.4s 0 transport_latency_assumed last_trade_price h 62,885 1,482 18ms 120ms 811ms 6.6s 0 transport_latency_assumed market_resolved a 890 not meas. 39ms 232ms 523ms 1.0min 0 transport_latency_assumed market_resolved c 890 4 4ms 6ms 91ms 1.5s 0 transport_latency_assumed market_resolved e 890 890 43ms 254ms 4.3s 58.1s 0 transport_latency_assumed market_resolved h 890 not meas. 12ms 41ms 246ms 57.2s 0 transport_latency_assumed new_market a 905 174 214ms 22.4s 37.8s 52.7s 0 transport_latency_assumed new_market c 905 103 64ms 21.0s 41.5s 1.2min 0 transport_latency_assumed new_market e 905 905 233ms 20.0s 39.0s 1.1min 0 transport_latency_assumed new_market h 905 212 127ms 20.5s 38.6s 56.7s 0 transport_latency_assumed price_change a 60,401,052 1,238 39ms 88ms 2.1s 15.3s 0 transport_latency_assumed price_change c 60,468,416 19,045 4ms 8ms 155ms 6.4s 0 transport_latency_assumed price_change e 60,189,888 60,189,164 43ms 200ms 6.6s 26.0s 0 transport_latency_assumed price_change h 60,437,348 267,997 12ms 22ms 242ms 42.7s 0 transport_latency_assumed tick_size_change a 2,064 not meas. 38ms 43ms 103ms 347ms 0 transport_latency_assumed tick_size_change c 2,060 not meas. 4ms 6ms 21ms 138ms 0 transport_latency_assumed tick_size_change e 2,064 2,064 44ms 123ms 2.1s 6.2s 0 transport_latency_assumed tick_size_change h 2,064 not meas. 12ms 17ms 95ms 153ms 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/05/2026-08-31T05.parquet sha256sum 2026-08-31T05.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.