Hour audit: 2026-09-21T07
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-21T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T07:00:00.000034392+00:00 · last event 2026-09-21T07:59:59.999895486+00:00
VOLUME 103,010,609 rows · 1,025,367,540 bytes (977.87 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 102,778,176 · f: 102,740,703 · h: 102,683,412 · e: 102,659,569 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 98,981,429 (96.09%) · f: 181,319 (0.18%) · h: 3,544,152 (3.44%) · e: 303,709 (0.29%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,010,609 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 4e6034190e68239475ece4e50dc128267bc59a5dba50780ab779c69b2a8f9e07
the corpus checksum ledger names this file with the same digest
joined 103,011,945 to merged 103,010,609, minus 1,336 (minus 0.0013%)
boundary drops 1,336 · 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-21T08:54:24Z 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 10,139,092 110,316,345 0-38 79ee6039178904c46c5519b4cbc0af587399785703998aee01d4fcaea2e3ae5e book 274,378 27,700,354 39-40 ef5db9d56983735f7282d794e7247ea2120424d2a8a5a375a1216e47a1df1b5c last_trade_price 48,531 2,733,637 41-41 f30e30c6f9672db4f04ef17c63774a614878a36827a9c9dbfaae5578749d387e market_resolved 1,070 172,264 42-42 c83d5b46fb7265b11149ed04e590bd96e4a73c6b696fc71564e54007e32ee10c new_market 532 63,761 43-43 e5d469a5e49e3633e47819286416cece9cbd929a3da2b92b421080a3468bbafa price_change 92,544,082 883,100,335 44-397 1cbe25ff015def99b812a003de80e6b67501c73e7be1124ac8ba5f0480fbb456 tick_size_change 2,924 104,952 398-398 94373d5da2c8fc52487210ac03f5ebbc78dc80bf326a545c36645160039ddcf5 EVENT MIX count share price_change 92,544,082 89.84% best_bid_ask 10,139,092 9.84% book 274,378 0.27% last_trade_price 48,531 0.05% tick_size_change 2,924 <0.01% market_resolved 1,070 <0.01% new_market 532 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,139,226 10,139,092 134 67,013 PARTIAL book 274,402 274,378 24 76,893 PARTIAL last_trade_price 48,531 48,531 0 2,987 PARTIAL market_resolved 1,070 1,070 0 1,068 PARTIAL new_market 532 532 0 424 PARTIAL price_change 92,545,260 92,544,082 1,178 116,110 PARTIAL tick_size_change 2,924 2,924 0 731 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,138,218 9,821,939 4ms 8ms 65ms 4.3s 0 transport_latency_assumed best_bid_ask e 10,138,298 17,308 40ms 45ms 127ms 5.3s 0 transport_latency_assumed best_bid_ask f 10,138,230 7,378 46ms 52ms 143ms 9.9s 0 transport_latency_assumed best_bid_ask h 10,138,094 292,467 18ms 23ms 86ms 2.2min 0 transport_latency_assumed book c 152,669 142,298 9ms 31.0min 29.7d 95.9d 0 book_staleness book e 151,409 46,573 49ms 29.7min 29.7d 114.4d 0 book_staleness book f 142,250 38,490 53ms 26.2min 26.5d 114.4d 0 book_staleness book h 146,270 47,017 25ms 27.9min 29.3d 114.4d 0 book_staleness last_trade_price c 48,401 45,888 5ms 17ms 155ms 1.2s 0 transport_latency_assumed last_trade_price e 48,470 215 43ms 107ms 1.6s 5.3s 0 transport_latency_assumed last_trade_price f 48,431 94 49ms 126ms 5.4s 9.8s 0 transport_latency_assumed last_trade_price h 48,440 2,334 19ms 41ms 217ms 4.7s 0 transport_latency_assumed market_resolved c 1,068 1,009 5ms 10.7s 52.7s 58.1s 0 transport_latency_assumed market_resolved e 1,068 38 41ms 10.9s 52.7s 58.3s 0 transport_latency_assumed market_resolved f 1,068 not meas. 47ms 11.4s 52.8s 58.8s 0 transport_latency_assumed market_resolved h 1,068 23 19ms 14.2s 56.1s 1.0min 0 transport_latency_assumed new_market c 424 218 226ms 12.5s 19.9s 22.5s 0 transport_latency_assumed new_market e 424 74 511ms 17.4s 23.1s 24.3s 0 transport_latency_assumed new_market f 424 97 242ms 11.5s 17.2s 18.8s 0 transport_latency_assumed new_market h 424 143 243ms 15.7s 20.1s 21.3s 0 transport_latency_assumed price_change c 92,434,472 88,967,248 5ms 10ms 91ms 4.5s 0 transport_latency_assumed price_change e 92,316,976 239,497 41ms 50ms 226ms 10.3s 0 transport_latency_assumed price_change f 92,407,376 135,260 47ms 58ms 252ms 10.6s 0 transport_latency_assumed price_change h 92,346,192 3,202,077 18ms 26ms 135ms 2.2min 0 transport_latency_assumed tick_size_change c 2,924 2,829 4ms 8ms 49ms 241ms 0 transport_latency_assumed tick_size_change e 2,924 4 40ms 44ms 88ms 241ms 0 transport_latency_assumed tick_size_change f 2,924 not meas. 47ms 51ms 93ms 185ms 0 transport_latency_assumed tick_size_change h 2,924 91 18ms 20ms 46ms 85ms 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/07/2026-09-21T07.parquet sha256sum 2026-09-21T07.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.