Hour audit: 2026-09-21T19
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-21T19 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T19:00:00.002507728+00:00 · last event 2026-09-21T19:59:59.999987120+00:00
VOLUME 107,463,727 rows · 1,166,665,554 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 106,117,017 · f: 105,516,912 · e: 104,821,257 · c: 94,862,209 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 18,774,378 (17.47%) · f: 916,580 (0.85%) · e: 1,619,920 (1.51%) · c: 86,152,849 (80.17%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 3a0e0b1a687bbc40b57272cb2295d39c6f4297af0fb2ebc5e43a4e880d96d471
the corpus checksum ledger names this file with the same digest
joined 107,464,825 to merged 107,463,727, minus 1,098 (minus 0.0010%)
boundary drops 1,098 · 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-21T20:55:21Z 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,043,939 119,407,703 0-38 adeb2131bea7e777fe181d475fced7a1c74ff64c32634132cc9431f1b758970c book 1,147,397 67,637,913 39-43 b240d9d5fa758b4260629c05546c20c172088d7436a6144eea267610475970b5 last_trade_price 62,969 3,534,799 44-44 e8750b1a7cbb175aabaffe31e78d07bbae148024124021b0dd2df11c9a442260 market_resolved 933 136,541 45-45 40dc8488f02eda6d5eca2fcdb7adf90fd8ea394e0c2d9b85b1ffa4a82e9f5734 new_market 9,023 927,103 46-46 df42aad4f48514f97b0dc55a2f3e35c1966c06b2ddc246342ffc5ee931f92279 price_change 96,196,222 973,678,841 47-413 336e634487b9cfab2eec756cb8a3025621b716ea1268c383915c1d2e25f8c06b tick_size_change 3,244 119,372 414-414 91e22c46f231c3bb0c9f3ffad15e2b5e3cb09bfe7cfad85b7e57e59f0effbb89 EVENT MIX count share price_change 96,196,222 89.52% best_bid_ask 10,043,939 9.35% book 1,147,397 1.07% last_trade_price 62,969 0.06% new_market 9,023 <0.01% tick_size_change 3,244 <0.01% market_resolved 933 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,044,055 10,043,939 116 74,190 PARTIAL book 1,147,507 1,147,397 110 164,143 PARTIAL last_trade_price 62,969 62,969 0 3,276 PARTIAL market_resolved 933 933 0 848 PARTIAL new_market 9,023 9,023 0 6,013 PARTIAL price_change 96,197,094 96,196,222 872 127,735 PARTIAL tick_size_change 3,244 3,244 0 811 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,875,384 8,077,650 6ms 27ms 231ms 3.4s 0 transport_latency_assumed best_bid_ask e 10,010,525 150,506 43ms 97ms 478ms 30.9s 0 transport_latency_assumed best_bid_ask f 10,028,728 78,448 48ms 106ms 487ms 30.0s 0 transport_latency_assumed best_bid_ask h 10,036,917 1,737,335 18ms 45ms 497ms 51.8s 0 transport_latency_assumed book c 1,099,704 1,075,825 5.0min 3.2d 44.1d 114.9d 0 book_staleness book e 147,955 22,934 112ms 51.3s 12.0d 96.4d 0 book_staleness book f 142,323 13,396 108ms 9.7s 2.2d 114.9d 0 book_staleness book h 146,272 35,242 26ms 2.3s 1.1d 96.4d 0 book_staleness last_trade_price c 55,438 50,152 7ms 44ms 265ms 1.5s 0 transport_latency_assumed last_trade_price e 57,440 774 71ms 2.5s 14.3s 30.4s 0 transport_latency_assumed last_trade_price f 59,444 807 84ms 2.9s 14.5s 30.0s 0 transport_latency_assumed last_trade_price h 62,409 11,236 20ms 121ms 887ms 18.1s 0 transport_latency_assumed market_resolved c 791 642 7ms 43.0s 4.3min 5.4min 0 transport_latency_assumed market_resolved e 848 175 50ms 39.3s 1.0min 2.1min 0 transport_latency_assumed market_resolved f 848 8 51ms 26.6s 1.0min 1.1min 0 transport_latency_assumed market_resolved h 848 108 21ms 27.9s 1.0min 1.0min 0 transport_latency_assumed new_market c 6,122 4,384 73ms 1.8min 5.7min 12.3min 0 transport_latency_assumed new_market e 6,010 1,007 174ms 46.1s 10.3min 12.3min 0 transport_latency_assumed new_market f 6,013 1,238 187ms 57.8s 11.2min 15.2min 0 transport_latency_assumed new_market h 6,011 2,394 112ms 39.0s 10.7min 12.3min 0 transport_latency_assumed price_change c 84,821,926 76,941,484 6ms 32ms 246ms 10.1s 0 transport_latency_assumed price_change e 94,595,239 1,444,499 44ms 158ms 5.3s 31.2s 0 transport_latency_assumed price_change f 95,276,312 822,670 49ms 171ms 5.0s 30.0s 0 transport_latency_assumed price_change h 95,861,316 16,987,569 18ms 58ms 646ms 54.1s 0 transport_latency_assumed tick_size_change c 2,844 2,712 6ms 13ms 94ms 471ms 0 transport_latency_assumed tick_size_change e 3,240 25 44ms 77ms 193ms 1.4s 0 transport_latency_assumed tick_size_change f 3,244 13 48ms 72ms 179ms 1.1s 0 transport_latency_assumed tick_size_change h 3,244 494 18ms 40ms 175ms 2.8s 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/19/2026-09-21T19.parquet sha256sum 2026-09-21T19.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.