Hour audit: 2026-08-28T19
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.
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.
1 check 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-08-28T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T19:00:00.023598762+00:00 · last event 2026-08-28T19:59:59.999918699+00:00
VOLUME 113,399,779 rows · 1,269,304,587 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 110,116,924 · e: 108,827,458 · h: 106,040,261 · a: 101,179,298 · b: 85,929,018 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · e: not measured · h: not measured · a: not measured · b: not measured (rows of the merged file that came from it; these partition it)
35 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 sha256 bd11d17307157ed3b96ec35af9dff5a8b3b3688c4e149d348de4ca19c99b6851
the corpus checksum ledger names this file with the same digest
joined 113,400,819 to merged 113,399,779, minus 1,040 (minus 0.0009%)
boundary drops 1,040 · 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 7/8 pass, 1 not evaluated
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
SKIPPED which machines were expected is not published beside this hour
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 8,540,800 103,183,681 0-32 3674d2cd913fec4111760773d6a74472ede851764cbfac14aef692e9a5428f7a book 3,413,014 113,802,749 33-46 befa740403315f9bd2be5d798ba16a6634447bd485a8da05744d506b0a75c9fe last_trade_price 76,041 4,340,100 47-47 55c64b1f75b0f4341664b98dd81bce95624e8cc6be0e6e1778031ebd797a300a market_resolved 1,181 129,940 48-48 2fd4d58f8d5be67e4719b25a7ee6a253e8127a2af593673391b717916c441b16 new_market 3,003 207,564 49-49 48f0daa1aef55922d3b0405d4ebcea8dcf8bdd5c37499f6fc86e460f05cc0013 price_change 101,357,880 1,046,058,247 50-436 5664a08f593b87ac0f1090e7068817b01613452b8750a0044bd94adae73c02b6 tick_size_change 7,860 288,125 437-437 58635e8447ab0edca1fe978c1aafe93a2a61898371f20cefa3c410ebf6b600d0 EVENT MIX count share price_change 101,357,880 89.38% best_bid_ask 8,540,800 7.53% book 3,413,014 3.01% last_trade_price 76,041 0.07% tick_size_change 7,860 <0.01% new_market 3,003 <0.01% market_resolved 1,181 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,540,890 8,540,800 90 4,160 FULL book 3,413,036 3,413,014 22 182,232 FULL last_trade_price 76,041 76,041 0 760 FULL market_resolved 1,181 1,181 0 49 FULL new_market 3,003 3,003 0 13 FULL price_change 101,358,808 101,357,880 928 1,517 FULL tick_size_change 7,860 7,860 0 518 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,809,031 not meas. 39ms 66ms 416ms 20.5s 0 not stated best_bid_ask b 6,461,287 not meas. 49ms 76ms 435ms 17.7s 0 not stated best_bid_ask c 8,540,266 not meas. 6ms 13ms 155ms 9.7s 0 not stated best_bid_ask e 8,495,824 not meas. 38ms 186ms 4.8s 51.2s 0 not stated best_bid_ask h 8,204,057 not meas. 14ms 30ms 215ms 9.6s 0 not stated book a 892,357 not meas. 1.4min 9.1h 26.3d 90.9d 0 not stated book b 3,080,913 not meas. 2.3min 14.4h 26.3d 90.9d 0 not stated book c 158,130 not meas. 9ms 34ms 2.5s 26.3d 0 not stated book e 161,782 not meas. 145ms 9.7s 1.9h 9.7d 0 not stated book h 526,577 not meas. 46.0s 6.6h 21.9d 90.9d 0 not stated last_trade_price a 68,380 not meas. 63ms 2.0s 11.5s 20.6s 0 not stated last_trade_price b 57,574 not meas. 67ms 1.9s 9.9s 17.7s 0 not stated last_trade_price c 75,947 not meas. 11ms 44ms 239ms 5.0s 0 not stated last_trade_price e 71,685 not meas. 99ms 6.1s 15.4s 34.8s 0 not stated last_trade_price h 73,088 not meas. 21ms 125ms 620ms 7.2s 0 not stated market_resolved a 757 not meas. 40ms 7.9min 9.2min 9.3min 0 not stated market_resolved b 937 not meas. 198ms 14.6min 21.9min 23.4min 0 not stated market_resolved c 767 not meas. 6ms 10ms 72ms 59.9s 0 not stated market_resolved e 765 not meas. 37ms 378ms 2.1s 1.0min 0 not stated market_resolved h 805 not meas. 14ms 104ms 5.8min 5.8min 0 not stated new_market a 1,284 not meas. 240ms 22.5s 5.4min 2.0h 0 not stated new_market b 2,269 not meas. 4.0min 15.2min 17.7min 2.3h 0 not stated new_market c 1,206 not meas. 76ms 12.9s 26.8s 3.4min 0 not stated new_market e 1,216 not meas. 198ms 12.7s 36.2s 3.5min 0 not stated new_market h 1,208 not meas. 102ms 13.6s 47.6s 4.2min 0 not stated price_change a 92,400,233 not meas. 39ms 91ms 2.1s 20.6s 0 not stated price_change b 76,320,010 not meas. 50ms 97ms 2.0s 17.7s 0 not stated price_change c 101,332,748 not meas. 6ms 12ms 161ms 9.9s 0 not stated price_change e 100,088,338 not meas. 38ms 455ms 9.5s 51.8s 0 not stated price_change h 97,227,030 not meas. 14ms 30ms 247ms 9.6s 0 not stated tick_size_change a 7,256 not meas. 38ms 51ms 180ms 1.3s 0 not stated tick_size_change b 6,028 not meas. 49ms 61ms 262ms 614ms 0 not stated tick_size_change c 7,860 not meas. 6ms 10ms 90ms 668ms 0 not stated tick_size_change e 7,848 not meas. 38ms 147ms 1.5s 15.1s 0 not stated tick_size_change h 7,496 not meas. 14ms 25ms 132ms 1.3s 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/2026-08-28/19/2026-08-28T19.parquet sha256sum 2026-08-28T19.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.