Hour audit: 2026-08-31T10
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-31T10 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T10:00:00.012818718+00:00 · last event 2026-08-31T10:59:59.999904184+00:00
VOLUME 24,515,856 rows · 274,661,334 bytes (261.94 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 24,504,779 · h: 24,473,744 · a: 24,451,084 · e: 24,352,174 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 14,065 (0.06%) · h: 144,783 (0.59%) · a: 4,834 (0.02%) · e: 24,352,174 (99.33%) (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 24,515,856 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 06512c9549f927407689bfa67d8bae7e0f2b49996cf9b9a83111dc4263b32356
the corpus checksum ledger names this file with the same digest
joined 24,515,856 to merged 24,515,856, no change
boundary drops 0 · 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-31T11:49:55Z 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 2,843,546 42,706,802 0-10 29b670955a942ea6114cd407b41bc105e9e651b03cc4acfa65a4e7581916ed41 book 67,247 6,159,482 11-11 2af2b1760e1b3f482f295b8229bddd7b0075a3e6f3f37dc20d915c961ac46fd0 last_trade_price 26,178 1,614,547 12-12 ef5c1cb6f01f209c9f3ebbd6ce0f5e38b32d585e3df039da2726bd55975c6b56 market_resolved 428 68,362 13-13 0eb0d4b12e0e4e434e0ba88e45918a2b4077296287b023dbebce81b8c506a448 new_market 1,694 174,938 14-14 bf2062f2972504c3ed96e9bf59a0b3725da2feca2c3757e3477968834c1957ec price_change 21,575,043 223,582,713 15-97 6a8fda3cb83ae80411b9916ca18759138da79b9edde358abde9e5a12be9e9948 tick_size_change 1,720 61,825 98-98 156078418536eb5ca75583ddbed057fdf54dc260dc8ec3d8c0d1d99e49783810 EVENT MIX count share price_change 21,575,043 88.00% best_bid_ask 2,843,546 11.60% book 67,247 0.27% last_trade_price 26,178 0.11% tick_size_change 1,720 <0.01% new_market 1,694 <0.01% market_resolved 428 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 2,843,546 2,843,546 0 103,732 PARTIAL book 67,247 67,247 0 9,373 PARTIAL last_trade_price 26,178 26,178 0 2,776 PARTIAL market_resolved 428 428 0 411 PARTIAL new_market 1,694 1,694 0 1,164 PARTIAL price_change 21,575,043 21,575,043 0 140,997 PARTIAL tick_size_change 1,720 1,720 0 430 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 2,841,869 14 40ms 52ms 535ms 20.2s 0 transport_latency_assumed best_bid_ask c 2,843,452 188 4ms 6ms 119ms 6.6s 0 transport_latency_assumed best_bid_ask e 2,837,774 2,837,774 43ms 102ms 1.9s 28.1s 0 transport_latency_assumed best_bid_ask h 2,843,344 5,570 11ms 19ms 218ms 5.8s 0 transport_latency_assumed book a 59,421 4,700 109ms 7.0s 4.9h 85.8d 0 book_staleness book c 58,939 3,553 6ms 381ms 4.0h 75.0d 0 book_staleness book e 56,468 56,468 127ms 7.8s 3.7h 22.9d 0 book_staleness book h 55,715 2,526 24ms 297ms 3.2s 74.9d 0 book_staleness last_trade_price a 25,802 2 62ms 2.4s 9.2s 20.2s 0 transport_latency_assumed last_trade_price c 26,172 6 9ms 47ms 402ms 3.3s 0 transport_latency_assumed last_trade_price e 25,131 25,131 80ms 5.1s 13.9s 28.1s 0 transport_latency_assumed last_trade_price h 26,165 1,039 19ms 196ms 1.2s 3.4s 0 transport_latency_assumed market_resolved a 411 14 39ms 172ms 512ms 1.0min 0 transport_latency_assumed market_resolved c 411 not meas. 4ms 6ms 235ms 551ms 0 transport_latency_assumed market_resolved e 411 411 43ms 210ms 952ms 1.0min 0 transport_latency_assumed market_resolved h 411 3 12ms 27ms 211ms 830ms 0 transport_latency_assumed new_market a 1,164 24 155ms 17.7s 24.8s 1.3min 0 transport_latency_assumed new_market c 1,164 150 73ms 18.0s 24.7s 1.0min 0 transport_latency_assumed new_market e 1,164 1,164 201ms 17.4s 25.0s 1.0min 0 transport_latency_assumed new_market h 1,164 356 102ms 16.7s 27.1s 1.0min 0 transport_latency_assumed price_change a 21,520,697 80 40ms 111ms 2.4s 20.2s 0 transport_latency_assumed price_change c 21,572,921 10,168 4ms 9ms 261ms 7.4s 0 transport_latency_assumed price_change e 21,429,506 21,429,506 44ms 210ms 6.3s 28.1s 0 transport_latency_assumed price_change h 21,545,225 135,289 12ms 28ms 439ms 7.1s 0 transport_latency_assumed tick_size_change a 1,720 not meas. 39ms 57ms 148ms 372ms 0 transport_latency_assumed tick_size_change c 1,720 not meas. 4ms 6ms 25ms 107ms 0 transport_latency_assumed tick_size_change e 1,720 1,720 44ms 128ms 362ms 1.4s 0 transport_latency_assumed tick_size_change h 1,720 not meas. 11ms 20ms 84ms 296ms 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/10/2026-08-31T10.parquet sha256sum 2026-08-31T10.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.