Hour audit: 2026-11-02T04
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-11-02T04.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-11-02T04 · 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 80,859,000 rows · 7 products, all holding rows
WITNESSES ipqr — 4 machines contributed rows
captured q: 123,493,874 · r: 123,482,908 · i: 123,480,687 · p: 119,624,831 (each machine's own feed; these overlap and do not sum to the file)
supplied q: 123,493,586 (99.44%) · r: 48,063 (0.04%) · i: 57,692 (0.05%) · p: 589,511 (0.47%) (rows of the merged file that came from it; these partition it)
5 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 124,189,594 to merged 124,188,852, minus 742 (minus 0.0006%)
boundary drops 742 · 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 8,574,300 not meas. not meas. not published book 547,206 not meas. not meas. not published last_trade_price 42,505 not meas. not meas. not published market_resolved 2,349 not meas. not meas. not published new_market 879 not meas. not meas. not published price_change 71,687,793 not meas. not meas. not published tick_size_change 3,968 not meas. not meas. not published EVENT MIX count share price_change 71,687,793 88.66% best_bid_ask 8,574,300 10.60% book 547,206 0.68% last_trade_price 42,505 0.05% tick_size_change 3,968 <0.01% market_resolved 2,349 <0.01% new_market 879 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,972,742 13,972,702 40 611 FULL book 835,845 835,665 180 199,338 FULL last_trade_price 42,505 42,505 0 66 FULL market_resolved 2,349 2,349 0 13 FULL new_market 879 879 0 0 FULL price_change 109,331,306 109,330,784 522 288 FULL tick_size_change 3,968 3,968 0 128 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask i 13,967,791 4 19ms 21ms 87ms 2.3min 0 not stated best_bid_ask p 13,479,231 2,095 3ms 5ms 33ms 6.3s 0 not stated best_bid_ask q 13,970,572 13,970,556 13ms 15ms 44ms 6.8s 0 not stated best_bid_ask r 13,969,501 47 11ms 13ms 48ms 6.3s 0 not stated book i 185,360 57,622 8.6s 2.1d 71.6d 156.3d 0 not stated book p 701,146 569,991 4.8min 2.9d 71.6d 156.2d 0 not stated book q 160,670 160,670 23ms 1.2d 68.4d 156.3d 0 not stated book r 172,439 47,382 559ms 1.5d 68.4d 156.3d 0 not stated last_trade_price i 42,386 not meas. 20ms 26ms 144ms 40.5s 0 not stated last_trade_price p 40,951 9 4ms 6ms 101ms 1.5s 0 not stated last_trade_price q 42,491 42,491 14ms 16ms 86ms 1.5s 0 not stated last_trade_price r 42,419 5 12ms 15ms 103ms 1.6s 0 not stated market_resolved i 1,910 not meas. 19ms 41.0s 53.2s 2.2min 0 not stated market_resolved p 1,905 383 3ms 45ms 3.4min 4.2min 0 not stated market_resolved q 1,917 1,917 13ms 38.3s 50.7s 2.1min 0 not stated market_resolved r 1,917 49 11ms 33.2s 54.0s 2.0min 0 not stated new_market i 562 26 189ms 32.6s 42.9s 1.4min 0 not stated new_market p 562 193 29ms 32.5s 43.0s 1.5min 0 not stated new_market q 562 562 82ms 33.2s 43.9s 1.6min 0 not stated new_market r 562 98 120ms 32.0s 45.4s 1.3min 0 not stated price_change i 109,278,710 40 19ms 22ms 104ms 2.3min 0 not stated price_change p 105,397,580 16,840 4ms 5ms 45ms 6.8s 0 not stated price_change q 109,313,694 109,313,422 13ms 15ms 57ms 6.8s 0 not stated price_change r 109,292,102 482 11ms 13ms 62ms 6.7s 0 not stated tick_size_change i 3,968 not meas. 19ms 21ms 26ms 157ms 0 not stated tick_size_change p 3,456 not meas. 3ms 5ms 8ms 209ms 0 not stated tick_size_change q 3,968 3,968 13ms 14ms 20ms 54ms 0 not stated tick_size_change r 3,968 not meas. 11ms 13ms 67ms 129ms 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-11-02/04/ 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.