Hour audit: 2026-10-28T03
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
2026-10-28T03.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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
4 checks could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-28T03 · corpus v3.1 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 68,054,617 rows · 7 products, all holding rows
WITNESSES imopq — 5 machines contributed rows
captured m: 134,670,789 · p: 134,660,655 · q: 134,628,477 · o: 134,457,260 · i: 134,324,723 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 243,507 (0.18%) · p: 134,658,277 (99.53%) · q: 192,635 (0.14%) · o: 154,286 (0.11%) · i: 38,912 (0.03%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count, and the figures above do not reconcile to the file's row count, so the split is incomplete by an unrecorded amount
INTEGRITY not measured (the manifest publishes no digest for this file)
checksum ledger not read
joined 135,294,972 to merged 135,287,617, minus 7,355 (minus 0.0054%)
boundary drops 7,355 · 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 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 4/8 pass, 4 not evaluated
PASS all products present
PASS row counts reconcile
SKIPPED the byte ranges could not be checked
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
SKIPPED the checksum ledger could not be read
SKIPPED the hour's minutes have not been measured
PASS a boundary guard ran
UPSTREAM status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 7,717,965 not meas. not meas. not published book 548,161 not meas. not meas. not published last_trade_price 44,080 not meas. not meas. not published market_resolved 1,629 not meas. not meas. not published new_market 1,716 not meas. not meas. not published price_change 59,738,794 not meas. not meas. not published tick_size_change 2,272 not meas. not meas. not published EVENT MIX count share price_change 59,738,794 87.78% best_bid_ask 7,717,965 11.34% book 548,161 0.81% last_trade_price 44,080 0.06% tick_size_change 2,272 <0.01% new_market 1,716 <0.01% market_resolved 1,629 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,684,647 14,684,583 64 53 FULL book 1,082,707 1,075,853 6,854 246,268 FULL last_trade_price 44,081 44,080 1 4 FULL market_resolved 1,629 1,629 0 11 FULL new_market 1,716 1,716 0 0 FULL price_change 119,477,920 119,477,484 436 42 FULL tick_size_change 2,272 2,272 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask i 14,681,393 30 22ms 25ms 77ms 2.9s 0 not stated best_bid_ask m 14,678,671 2,138 5ms 9ms 60ms 5.7s 0 not stated best_bid_ask o 14,680,240 2,073 5ms 9ms 62ms 4.5s 0 not stated best_bid_ask p 14,680,297 14,680,297 5ms 7ms 41ms 4.6s 0 not stated best_bid_ask q 14,680,511 45 14ms 17ms 67ms 7.7s 0 not stated book i 173,739 37,777 110ms 1.1d 52.6d 151.2d 0 not stated book m 505,908 223,835 18.1min 3.3d 66.6d 151.2d 0 not stated book o 294,585 134,737 49.1s 37.6min 5.8h 8.4h 0 not stated book p 490,187 487,821 17.3min 3.2d 66.6d 151.2d 0 not stated book q 464,024 191,683 15.7min 3.0d 66.6d 151.2d 0 not stated last_trade_price i 43,954 5 22ms 28ms 181ms 2.5s 0 not stated last_trade_price m 44,034 11 6ms 11ms 149ms 2.5s 0 not stated last_trade_price o 44,045 19 6ms 12ms 122ms 2.7s 0 not stated last_trade_price p 44,038 44,038 6ms 9ms 156ms 3.0s 0 not stated last_trade_price q 44,019 7 15ms 19ms 171ms 2.5s 0 not stated market_resolved i 1,269 not meas. 22ms 27.1s 52.8s 53.3s 0 not stated market_resolved m 1,276 51 6ms 19.3s 1.0min 2.1min 0 not stated market_resolved o 1,274 226 6ms 27.0s 59.6s 2.1min 0 not stated market_resolved p 1,269 1,269 5ms 12ms 44.3s 47.0s 0 not stated market_resolved q 1,269 83 15ms 26.9s 52.5s 53.0s 0 not stated new_market i 1,078 82 88ms 29.7s 50.5s 1.5min 0 not stated new_market m 1,078 222 73ms 21.7s 36.6s 1.7min 0 not stated new_market o 1,078 221 71ms 20.5s 34.8s 1.9min 0 not stated new_market p 1,078 1,078 29ms 19.4s 52.1s 1.6min 0 not stated new_market q 1,078 113 80ms 29.9s 37.4s 1.6min 0 not stated price_change i 119,421,018 1,018 22ms 26ms 87ms 3.2s 0 not stated price_change m 119,437,550 17,250 5ms 10ms 63ms 14.0s 0 not stated price_change o 119,433,766 17,006 5ms 10ms 66ms 5.2s 0 not stated price_change p 119,441,518 119,441,506 5ms 7ms 48ms 5.9s 0 not stated price_change q 119,435,304 704 14ms 17ms 75ms 7.7s 0 not stated tick_size_change i 2,272 not meas. 21ms 24ms 112ms 332ms 0 not stated tick_size_change m 2,272 not meas. 5ms 9ms 159ms 415ms 0 not stated tick_size_change o 2,272 4 6ms 12ms 230ms 597ms 0 not stated tick_size_change p 2,268 2,268 5ms 7ms 159ms 400ms 0 not stated tick_size_change q 2,272 not meas. 14ms 16ms 194ms 2.7s 0 not stated
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.1/2026-10-28/03/ sha256sum # 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.