Hour audit: 2026-09-20T23
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-20T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T23:00:00.000120127+00:00 · last event 2026-09-20T23:59:59.999950529+00:00
VOLUME 110,395,398 rows · 1,144,572,816 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 110,022,101 · e: 109,986,493 · f: 106,220,987 · h: 106,043,440 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,769,257 (94.00%) · e: 459,761 (0.42%) · f: 504,635 (0.46%) · h: 5,661,745 (5.13%) (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 110,395,398 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 f4aa75da2985872f4f5c7033f97bf4a2e9e6eca6dacaa31f17c06e8f6ce601f7
the corpus checksum ledger names this file with the same digest
joined 110,396,696 to merged 110,395,398, minus 1,298 (minus 0.0012%)
boundary drops 1,298 · 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-21T04:45:10Z 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 9,949,600 111,705,732 0-37 694af99021f3f7940fd3864f6e471d59e7dccc97526fe6849d0b6d1cdca3cdda book 443,924 45,531,901 38-39 2284c55975aa1a4875981fddb46b848304b50da18649e7f48264ccb4a5d562c0 last_trade_price 57,352 3,196,637 40-40 4e3a14d8fe9862414139269f4e3e46f6bb45467d56c0484520d76716ef0f06b2 market_resolved 4,389 679,112 41-41 2cc934bd9c796b090738fd678b534e44093756fda133d85b02e3dd0386f6739c new_market 393 47,686 42-42 a0b3749ba733a8c93e48a1280351991fa3998878e3091c330d24342c0a0e42f1 price_change 99,934,064 981,954,858 43-424 ac0fc6e6ccde1923da15d92bc097a3abcba78e749dd9cf4526b76352031929e0 tick_size_change 5,676 201,482 425-425 7cd24193a5a25036bf671eb415848a974a71efef2094ccca2136c936f36df656 EVENT MIX count share price_change 99,934,064 90.52% best_bid_ask 9,949,600 9.01% book 443,924 0.40% last_trade_price 57,352 0.05% tick_size_change 5,676 <0.01% market_resolved 4,389 <0.01% new_market 393 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,949,742 9,949,600 142 72,497 PARTIAL book 443,942 443,924 18 156,825 PARTIAL last_trade_price 57,352 57,352 0 3,129 PARTIAL market_resolved 4,389 4,389 0 4,246 PARTIAL new_market 393 393 0 303 PARTIAL price_change 99,935,202 99,934,064 1,138 121,650 PARTIAL tick_size_change 5,676 5,676 0 1,419 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,948,626 9,434,808 5ms 13ms 84ms 2.1s 0 transport_latency_assumed best_bid_ask e 9,947,467 32,220 39ms 48ms 141ms 4.7s 0 transport_latency_assumed best_bid_ask f 9,581,392 11,386 46ms 58ms 161ms 5.4s 0 transport_latency_assumed best_bid_ask h 9,752,428 471,186 17ms 26ms 89ms 7.2s 0 transport_latency_assumed book c 119,671 110,000 6ms 47ms 2.6h 95.5d 0 book_staleness book e 118,923 4,058 42ms 198ms 36.6min 95.5d 0 book_staleness book f 428,002 315,192 1.9min 2.0d 40.2d 114.0d 0 book_staleness book h 116,266 14,674 20ms 6.2s 8.4d 95.5d 0 book_staleness last_trade_price c 57,093 53,045 6ms 24ms 167ms 1.1s 0 transport_latency_assumed last_trade_price e 56,899 515 42ms 125ms 2.6s 4.7s 0 transport_latency_assumed last_trade_price f 55,668 247 48ms 217ms 2.8s 5.4s 0 transport_latency_assumed last_trade_price h 51,607 3,545 18ms 47ms 216ms 1.3s 0 transport_latency_assumed market_resolved c 4,246 4,076 5ms 12ms 104ms 36.6s 0 transport_latency_assumed market_resolved e 4,245 12 41ms 118ms 287ms 38.3s 0 transport_latency_assumed market_resolved f 4,185 108 48ms 128ms 4.7min 5.0min 0 transport_latency_assumed market_resolved h 4,190 193 20ms 52ms 27.0s 2.5min 0 transport_latency_assumed new_market c 303 212 43ms 291ms 15.1h 22.1h 0 transport_latency_assumed new_market e 303 24 130ms 14.0s 15.1h 22.1h 0 transport_latency_assumed new_market f 303 52 90ms 10.6s 15.1h 22.1h 0 transport_latency_assumed new_market h 303 105 60ms 12.4s 15.1h 22.1h 0 transport_latency_assumed price_change c 99,886,486 94,161,620 5ms 16ms 99ms 2.1s 0 transport_latency_assumed price_change e 99,852,980 422,928 39ms 55ms 225ms 4.8s 0 transport_latency_assumed price_change f 96,146,041 177,650 46ms 66ms 282ms 5.4s 0 transport_latency_assumed price_change h 96,113,102 5,171,866 17ms 30ms 109ms 7.3s 0 transport_latency_assumed tick_size_change c 5,676 5,496 5ms 9ms 38ms 232ms 0 transport_latency_assumed tick_size_change e 5,676 4 39ms 44ms 96ms 149ms 0 transport_latency_assumed tick_size_change f 5,396 not meas. 46ms 51ms 116ms 258ms 0 transport_latency_assumed tick_size_change h 5,544 176 17ms 21ms 59ms 244ms 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-20/23/2026-09-20T23.parquet sha256sum 2026-09-20T23.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.