Hour audit: 2026-08-28T20
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-28T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T20:00:00.022763222+00:00 · last event 2026-08-28T20:59:59.999985049+00:00
VOLUME 95,555,901 rows · 1,073,838,526 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 94,011,603 · e: 92,330,138 · h: 90,160,812 · b: 86,135,193 · a: 86,048,652 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · e: not measured · h: not measured · b: not measured · a: 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 89064e455ef830e3804b6c379bc17bae9c9f9390e1fa1371268461086ad6502f
the corpus checksum ledger names this file with the same digest
joined 95,557,267 to merged 95,555,901, minus 1,366 (minus 0.0014%)
boundary drops 1,366 · 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 6,986,370 86,754,611 0-26 3be9fb83c7bf01d6e284d16f88c764fe70844f12e3611e835d829af5ae75bc44 book 1,727,395 93,475,883 27-33 b151255fb447cb7b3eb05279051e94037a32306cb3a98b2a5772a7375743ae8d last_trade_price 70,674 4,087,692 34-34 4d9e91e72bb8ba88ddebda17d545de9dc4f15d4cdd68bd03b1c8248d215876ef market_resolved 2,419 322,831 35-35 37d727f1d640de4e7f132179cc39b12c95d6778f43d28ab01eacb6f1ba648421 new_market 3,907 325,012 36-36 821d8caea5b0e6b8745913a112399f73d5bcdbbfdfef8ff84667a7e71c1cba6c price_change 86,757,732 887,509,468 37-367 0d9dcbac934e9533b185ce8daeebaaf8ab4a07690d1895df08f93c3832aba985 tick_size_change 7,404 272,718 368-368 62f084bf15a89d7843aba8fc8dc67d47cb73bcdc668759863e839742fdd361bd EVENT MIX count share price_change 86,757,732 90.79% best_bid_ask 6,986,370 7.31% book 1,727,395 1.81% last_trade_price 70,674 0.07% tick_size_change 7,404 <0.01% new_market 3,907 <0.01% market_resolved 2,419 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,986,500 6,986,370 130 3,671 FULL book 1,727,537 1,727,395 142 179,369 FULL last_trade_price 70,676 70,674 2 644 FULL market_resolved 2,419 2,419 0 64 FULL new_market 3,917 3,907 10 17 FULL price_change 86,758,814 86,757,732 1,082 1,777 FULL tick_size_change 7,404 7,404 0 394 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,312,183 not meas. 40ms 74ms 599ms 28.3s 0 not stated best_bid_ask b 6,320,421 not meas. 49ms 76ms 430ms 17.1s 0 not stated best_bid_ask c 6,985,685 not meas. 6ms 14ms 213ms 9.2s 0 not stated best_bid_ask e 6,931,903 not meas. 42ms 240ms 6.1s 43.4s 0 not stated best_bid_ask h 6,669,114 not meas. 13ms 29ms 347ms 55.5s 0 not stated book a 941,284 not meas. 1.7min 9.1h 26.3d 90.9d 0 not stated book b 973,430 not meas. 1.7min 9.3h 26.3d 90.9d 0 not stated book c 214,348 not meas. 12ms 30.9min 20.3d 90.9d 0 not stated book e 188,185 not meas. 746ms 12.6min 6.3d 72.4d 0 not stated book h 615,757 not meas. 1.3min 7.8h 25.1d 90.9d 0 not stated last_trade_price a 62,520 not meas. 69ms 2.9s 13.3s 28.2s 0 not stated last_trade_price b 63,219 not meas. 68ms 1.7s 9.1s 17.1s 0 not stated last_trade_price c 70,572 not meas. 11ms 47ms 258ms 8.3s 0 not stated last_trade_price e 63,612 not meas. 102ms 6.2s 16.8s 43.4s 0 not stated last_trade_price h 66,175 not meas. 20ms 146ms 960ms 9.8s 0 not stated market_resolved a 1,998 not meas. 44ms 419ms 7.9min 8.9min 0 not stated market_resolved b 2,087 not meas. 58ms 830ms 11.5min 13.7min 0 not stated market_resolved c 1,941 not meas. 6ms 13ms 45.6s 1.0min 0 not stated market_resolved e 1,941 not meas. 44ms 292ms 47.0s 1.0min 0 not stated market_resolved h 1,954 not meas. 16ms 220ms 5.0min 5.2min 0 not stated new_market a 2,095 not meas. 366ms 4.7min 6.1min 59.9min 0 not stated new_market b 2,893 not meas. 611ms 9.6min 10.6min 40.0min 0 not stated new_market c 1,935 not meas. 140ms 15.7s 56.9s 1.3min 0 not stated new_market e 1,925 not meas. 263ms 14.9s 1.8min 19.8min 0 not stated new_market h 1,936 not meas. 183ms 17.7s 1.5min 23.6min 0 not stated price_change a 78,721,748 not meas. 40ms 110ms 3.0s 28.3s 0 not stated price_change b 78,766,295 not meas. 49ms 96ms 2.1s 17.1s 0 not stated price_change c 86,729,718 not meas. 6ms 12ms 224ms 9.7s 0 not stated price_change e 85,135,168 not meas. 43ms 526ms 10.5s 43.4s 0 not stated price_change h 82,799,064 not meas. 13ms 30ms 392ms 55.9s 0 not stated tick_size_change a 6,824 not meas. 40ms 60ms 530ms 25.8s 0 not stated tick_size_change b 6,848 not meas. 49ms 69ms 290ms 694ms 0 not stated tick_size_change c 7,404 not meas. 6ms 12ms 220ms 641ms 0 not stated tick_size_change e 7,404 not meas. 44ms 178ms 6.7s 17.9s 0 not stated tick_size_change h 6,812 not meas. 13ms 31ms 310ms 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/20/2026-08-28T20.parquet sha256sum 2026-08-28T20.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.