Hour audit: 2026-08-31T01
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-31T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T01:00:00.044936382+00:00 · last event 2026-08-31T01:59:59.999978594+00:00
VOLUME 70,623,581 rows · 725,624,526 bytes (692.01 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 70,449,912 · h: 70,292,356 · a: 70,143,128 · e: 69,577,954 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 156,822 (0.22%) · h: 774,118 (1.10%) · a: 114,705 (0.16%) · e: 69,577,936 (98.52%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 70,623,581 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 1ad5aa732d9f777a8dbb4043595f3d34538d0d1e81269088dd5a3626f978b2a1
the corpus checksum ledger names this file with the same digest
joined 70,623,847 to merged 70,623,581, minus 266 (minus 0.0004%)
boundary drops 266 · 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-31T02:48: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 an incident recorded by the venue intersects this hour: Venue in cancel-only mode for about half an hour, 2026-08-31T00:40Z to 2026-08-31T01:12ZThe 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,580,464 80,221,916 0-25 f2a33fd3a5a8cf564b86c921d86e4126f0aa6a2bb175ffe5da06e14a064b02c5 book 440,519 39,705,283 26-27 b4e2f1f87bf2940d622d27dfa8a052ff9998aea995799a3dd66bfe0208a30b9e last_trade_price 61,748 3,407,251 28-28 b8dfbcad2b491e38c1937a531aa10ee24ee870817b4305d623397f3cc133a06f market_resolved 818 129,742 29-29 5c3b02fa30e845a0d57ca3a14fa2f29ebacc631bb98116cdd318a117138947d8 new_market 790 81,712 30-30 9b536fe803dbc830589bdd6459e53b55bd7f40df32fcf56771820281c5c02c91 price_change 63,536,422 601,163,834 31-273 93f858cce6f11d4e0802bc61258edeebf14420ca7c310e4f3d447f905a92aa47 tick_size_change 2,820 103,338 274-274 56bf1f90dc106245df4f8755e1acf50c61bcd16887c7a8af785ce0f5046febdd EVENT MIX count share price_change 63,536,422 89.96% best_bid_ask 6,580,464 9.32% book 440,519 0.62% last_trade_price 61,748 0.09% tick_size_change 2,820 <0.01% market_resolved 818 <0.01% new_market 790 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,580,464 6,580,464 0 102,163 PARTIAL book 440,785 440,519 266 117,056 PARTIAL last_trade_price 61,748 61,748 0 3,113 PARTIAL market_resolved 818 818 0 801 PARTIAL new_market 790 790 0 531 PARTIAL price_change 63,536,422 63,536,422 0 137,294 PARTIAL tick_size_change 2,820 2,820 0 703 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,572,083 92 36ms 53ms 745ms 26.9s 0 transport_latency_assumed best_bid_ask c 6,579,960 432 3ms 7ms 65ms 1.7s 0 transport_latency_assumed best_bid_ask e 6,548,194 6,548,194 45ms 113ms 3.4s 24.1s 0 transport_latency_assumed best_bid_ask h 6,579,808 31,746 12ms 19ms 115ms 6.9s 0 transport_latency_assumed book a 267,714 112,929 14.1s 34.5min 22.5d 93.1d 0 book_staleness book c 272,721 134,128 6.8s 30.6min 22.5d 93.1d 0 book_staleness book e 154,609 154,591 403ms 5.0min 22.5d 32.4d 0 book_staleness book h 159,164 38,871 26ms 3.1min 9.3d 74.6d 0 book_staleness last_trade_price a 59,708 8 78ms 5.0s 19.6s 26.9s 0 transport_latency_assumed last_trade_price c 61,720 8 9ms 38ms 170ms 5.0s 0 transport_latency_assumed last_trade_price e 57,741 57,741 109ms 7.5s 17.1s 24.4s 0 transport_latency_assumed last_trade_price h 61,715 3,991 19ms 125ms 577ms 5.0s 0 transport_latency_assumed market_resolved a 801 9 37ms 341ms 59.0s 59.1s 0 transport_latency_assumed market_resolved c 801 8 4ms 7ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 801 801 45ms 427ms 44.6s 58.2s 0 transport_latency_assumed market_resolved h 801 not meas. 12ms 55ms 44.5s 58.1s 0 transport_latency_assumed new_market a 531 70 182ms 15.9s 27.4s 1.3min 0 transport_latency_assumed new_market c 531 62 50ms 17.5s 32.2s 1.0min 0 transport_latency_assumed new_market e 531 531 140ms 12.6s 24.4s 1.5min 0 transport_latency_assumed new_market h 531 127 87ms 17.9s 32.3s 56.5s 0 transport_latency_assumed price_change a 63,239,471 1,597 37ms 105ms 6.6s 26.9s 0 transport_latency_assumed price_change c 63,531,359 22,184 4ms 8ms 187ms 1.9s 0 transport_latency_assumed price_change e 62,813,262 62,813,262 45ms 195ms 9.4s 24.4s 0 transport_latency_assumed price_change h 63,487,517 699,379 12ms 24ms 277ms 7.2s 0 transport_latency_assumed tick_size_change a 2,820 not meas. 36ms 41ms 111ms 658ms 0 transport_latency_assumed tick_size_change c 2,820 not meas. 4ms 6ms 33ms 312ms 0 transport_latency_assumed tick_size_change e 2,816 2,816 45ms 107ms 1.4s 17.8s 0 transport_latency_assumed tick_size_change h 2,820 4 12ms 16ms 36ms 1.0s 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/01/2026-08-31T01.parquet sha256sum 2026-08-31T01.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.