Hour audit: 2026-10-31T07
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-31T07.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-31T07 · 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 81,610,905 rows · 7 products, all holding rows
WITNESSES iop — 3 machines contributed rows
captured p: 135,989,546 · o: 135,856,574 · i: 135,848,418 (each machine's own feed; these overlap and do not sum to the file)
supplied p: 135,989,508 (99.92%) · o: 66,267 (0.05%) · i: 46,990 (0.03%) (rows of the merged file that came from it; these partition it)
1 product-machine pair 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 136,103,019 to merged 136,102,765, minus 254 (minus 0.0002%)
boundary drops 254 · 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 10,679,097 not meas. not meas. not published book 227,787 not meas. not meas. not published last_trade_price 60,649 not meas. not meas. not published market_resolved 2,075 not meas. not meas. not published new_market 1,553 not meas. not meas. not published price_change 70,633,868 not meas. not meas. not published tick_size_change 5,876 not meas. not meas. not published EVENT MIX count share price_change 70,633,868 86.55% best_bid_ask 10,679,097 13.09% book 227,787 0.28% last_trade_price 60,649 0.07% tick_size_change 5,876 <0.01% market_resolved 2,075 <0.01% new_market 1,553 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 18,257,354 18,257,322 32 54 FULL book 375,712 375,708 4 115,061 FULL last_trade_price 60,649 60,649 0 1 FULL market_resolved 2,075 2,075 0 0 FULL new_market 1,553 1,553 0 0 FULL price_change 117,399,800 117,399,582 218 32 FULL tick_size_change 5,876 5,876 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask i 18,252,585 623 19ms 22ms 376ms 2.0min 0 not stated best_bid_ask o 18,256,562 6,793 12ms 17ms 78ms 6.8s 0 not stated best_bid_ask p 18,249,908 18,249,906 13ms 15ms 57ms 6.9s 0 not stated book i 172,719 39,995 21ms 2.4h 53.9d 135.9d 0 not stated book o 137,113 10,732 14ms 3.7s 5.6d 135.9d 0 not stated book p 324,983 324,981 52.4s 2.1d 69.7d 154.4d 0 not stated last_trade_price i 60,617 65 20ms 30ms 584ms 16.0s 0 not stated last_trade_price o 60,644 90 13ms 20ms 132ms 3.0s 0 not stated last_trade_price p 60,494 60,494 14ms 18ms 339ms 5.6s 0 not stated market_resolved i 1,968 30 19ms 387ms 38.2s 51.3s 0 not stated market_resolved o 1,968 77 13ms 376ms 32.9s 54.5s 0 not stated market_resolved p 1,968 1,968 13ms 15.6s 33.4s 55.4s 0 not stated new_market i 1,045 213 551ms 1.2min 2.0min 2.2min 0 not stated new_market o 1,045 295 152ms 59.2s 1.3min 1.7min 0 not stated new_market p 1,045 1,045 61ms 1.1min 1.6min 2.0min 0 not stated price_change i 117,353,612 6,064 19ms 23ms 415ms 2.1min 0 not stated price_change o 117,393,366 48,276 12ms 18ms 90ms 7.0s 0 not stated price_change p 117,345,276 117,345,242 13ms 15ms 76ms 7.0s 0 not stated tick_size_change i 5,872 not meas. 19ms 22ms 1.8s 8.6s 0 not stated tick_size_change o 5,876 4 12ms 17ms 34ms 93ms 0 not stated tick_size_change p 5,872 5,872 13ms 15ms 32ms 130ms 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-31/07/ 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.