Hour audit: 2026-09-21T02
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: g. 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-09-21T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T02:00:00.005953567+00:00 · last event 2026-09-21T02:59:59.999898043+00:00
VOLUME 109,978,092 rows · 1,099,359,265 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 109,886,930 · f: 109,820,610 · e: 109,820,181 · h: 109,780,275 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,281,681 (95.73%) · f: 192,351 (0.17%) · e: 316,407 (0.29%) · h: 4,187,653 (3.81%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 109,978,092 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 aaa698e8bb092fd9a04452f9c192fe5dda9a58857761e3c65ff23a0dd635f45d
the corpus checksum ledger names this file with the same digest
joined 109,979,562 to merged 109,978,092, minus 1,470 (minus 0.0013%)
boundary drops 1,470 · 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-09-21T05:59:57Z as cefh
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 11,291,994 124,384,364 0-43 035e335f6342d8e5f62192e0e46fe74ef37bd6cb3eb1f7673f730bc13a691d3c book 126,072 13,686,708 44-44 d09d6d3d3aa2c1f3e42a15fe145c893fe5c2bb6f7c2f1d5d7e9dddcc49982192 last_trade_price 48,028 2,681,423 45-45 f022bdd5a62adcbe927ee2466ef9cab4a27a45c58fa0861a7aef41f82217000b market_resolved 1,670 269,291 46-46 ef1dc977501670674cd2744803234adfe62db33399926dc8f9a26d9b56aa95f3 new_market 1,298 126,398 47-47 628e0dc8cae89f18cefc8445e9f4a4e0a51b8cacddf6f38dbdd436ade69a86c8 price_change 98,506,454 956,864,303 48-423 9c2323763904befd37495684f910b10bc16698854f93176ddb17d6c9dd406faa tick_size_change 2,576 94,604 424-424 38a191042b6c0e9c87950706f35bbbe9bc0f8044ebf06a9c0ff08c949e50e8ee EVENT MIX count share price_change 98,506,454 89.57% best_bid_ask 11,291,994 10.27% book 126,072 0.11% last_trade_price 48,028 0.04% tick_size_change 2,576 <0.01% market_resolved 1,670 <0.01% new_market 1,298 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,292,119 11,291,994 125 66,481 PARTIAL book 126,078 126,072 6 14,140 PARTIAL last_trade_price 48,029 48,028 1 2,546 PARTIAL market_resolved 1,670 1,670 0 1,661 PARTIAL new_market 1,298 1,298 0 805 PARTIAL price_change 98,507,792 98,506,454 1,338 116,587 PARTIAL tick_size_change 2,576 2,576 0 643 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,291,378 10,869,700 4ms 10ms 82ms 5.3s 0 transport_latency_assumed best_bid_ask e 11,290,979 26,190 44ms 50ms 167ms 22.6s 0 transport_latency_assumed best_bid_ask f 11,290,910 13,837 46ms 55ms 184ms 10.8s 0 transport_latency_assumed best_bid_ask h 11,291,368 382,267 18ms 34ms 160ms 48.3s 0 transport_latency_assumed book c 104,063 97,393 6ms 84ms 1.5d 95.6d 0 book_staleness book e 104,241 7,217 47ms 1.6s 1.5d 95.7d 0 book_staleness book f 104,975 7,579 49ms 804ms 1.7d 114.2d 0 book_staleness book h 106,504 13,883 22ms 626ms 5.4d 95.7d 0 book_staleness last_trade_price c 47,887 45,107 5ms 18ms 161ms 2.2s 0 transport_latency_assumed last_trade_price e 47,831 217 46ms 135ms 5.4s 13.0s 0 transport_latency_assumed last_trade_price f 47,807 121 48ms 108ms 2.6s 10.8s 0 transport_latency_assumed last_trade_price h 47,935 2,583 19ms 56ms 278ms 10.0s 0 transport_latency_assumed market_resolved c 1,661 1,337 5ms 32.1s 57.0s 1.0min 0 transport_latency_assumed market_resolved e 1,661 9 45ms 33.8s 59.3s 1.1min 0 transport_latency_assumed market_resolved f 1,661 4 48ms 33.8s 59.6s 1.1min 0 transport_latency_assumed market_resolved h 1,661 320 19ms 30.9s 56.2s 1.0min 0 transport_latency_assumed new_market c 805 510 201ms 43.0s 1.2min 1.4min 0 transport_latency_assumed new_market e 805 258 277ms 38.5s 55.7s 1.2min 0 transport_latency_assumed new_market f 805 213 241ms 35.3s 52.3s 54.4s 0 transport_latency_assumed new_market h 805 317 229ms 36.3s 1.3min 1.5min 0 transport_latency_assumed price_change c 98,438,560 94,265,142 5ms 12ms 94ms 5.9s 0 transport_latency_assumed price_change e 98,372,088 282,512 44ms 56ms 434ms 22.6s 0 transport_latency_assumed price_change f 98,371,876 170,597 47ms 61ms 285ms 11.2s 0 transport_latency_assumed price_change h 98,329,426 3,788,203 18ms 39ms 185ms 48.7s 0 transport_latency_assumed tick_size_change c 2,576 2,492 4ms 8ms 62ms 174ms 0 transport_latency_assumed tick_size_change e 2,576 4 44ms 49ms 119ms 224ms 0 transport_latency_assumed tick_size_change f 2,576 not meas. 46ms 55ms 97ms 196ms 0 transport_latency_assumed tick_size_change h 2,576 80 18ms 34ms 128ms 223ms 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-09-21/02/2026-09-21T02.parquet sha256sum 2026-09-21T02.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.