Hour audit: 2026-08-27T21
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-27T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-27T21:00:00.008697771+00:00 · last event 2026-08-27T21:59:59.999955353+00:00
VOLUME 80,600,282 rows · 845,035,319 bytes (805.89 MiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured c: 80,301,724 · h: 80,232,411 · b: 80,230,826 · a: 80,225,187 · e: 78,658,690 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: not measured · b: not measured · a: not measured · e: 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 9fb94e4774195cb90a4fd5f9714d46b2f31db1fdf84b43fbad9ed8cffc4d4e72
the corpus checksum ledger names this file with the same digest
joined 80,601,794 to merged 80,600,282, minus 1,512 (minus 0.0019%)
boundary drops 1,512 · 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,720,930 79,133,454 0-25 d13a99fc1c5b0579c3a4a544de518b713c373d30b3ef477da31333d8a1cd69ad book 485,513 45,396,389 26-27 3aea507283e11ce01298f037702109fdf1b6ed6c26bc96bf8174d73857c1d747 last_trade_price 53,501 3,060,961 28-28 ebacdb8b9a188795e8cca96a875e2083c55b61d1c3c6be64f224b61c59c37b7d market_resolved 1,764 286,117 29-29 2a33dff8cd32e821271d635b258e587cb26a4875940b3085322f185c33189b21 new_market 460 53,619 30-30 99edc12aa0edac737378aa427717511e73bb6e7a267b1a300bc7799f4900f378 price_change 73,335,970 716,102,379 31-310 410abf15f85da1a77f07cab487fcadb09ee3a008d70b470337d3002ceec9059d tick_size_change 2,144 80,172 311-311 6cd93e171f813cbfc2ee151b419ee7e12ea69caa4c0248b35d39554e6b137994 EVENT MIX count share price_change 73,335,970 90.99% best_bid_ask 6,720,930 8.34% book 485,513 0.60% last_trade_price 53,501 0.07% tick_size_change 2,144 <0.01% market_resolved 1,764 <0.01% new_market 460 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,721,050 6,720,930 120 79 FULL book 485,521 485,513 8 128,758 FULL last_trade_price 53,501 53,501 0 1 FULL market_resolved 1,764 1,764 0 5 FULL new_market 460 460 0 0 FULL price_change 73,337,354 73,335,970 1,384 646 FULL tick_size_change 2,144 2,144 0 14 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,717,450 not meas. 40ms 48ms 327ms 17.0s 0 not stated best_bid_ask b 6,717,274 not meas. 49ms 63ms 356ms 19.3s 0 not stated best_bid_ask c 6,720,358 not meas. 4ms 7ms 49ms 5.0s 0 not stated best_bid_ask e 6,661,855 not meas. 47ms 116ms 2.9s 25.8s 0 not stated best_bid_ask h 6,720,242 not meas. 12ms 16ms 87ms 5.6s 0 not stated book a 196,224 not meas. 2.2s 40.8min 19.3d 90.0d 0 not stated book b 207,109 not meas. 3.7s 47.7min 19.3d 90.0d 0 not stated book c 203,704 not meas. 35ms 42.7min 19.3d 89.9d 0 not stated book e 170,063 not meas. 4.8s 29.6min 19.3d 90.0d 0 not stated book h 179,290 not meas. 51ms 30.7min 19.3d 90.0d 0 not stated last_trade_price a 52,770 not meas. 69ms 2.8s 8.1s 17.0s 0 not stated last_trade_price b 52,782 not meas. 84ms 3.3s 8.4s 19.2s 0 not stated last_trade_price c 53,439 not meas. 10ms 46ms 206ms 5.0s 0 not stated last_trade_price e 45,002 not meas. 90ms 6.9s 20.5s 25.9s 0 not stated last_trade_price h 53,434 not meas. 19ms 156ms 763ms 5.1s 0 not stated market_resolved a 1,735 not meas. 42ms 186ms 507ms 725ms 0 not stated market_resolved b 1,735 not meas. 53ms 224ms 547ms 1.2s 0 not stated market_resolved c 1,735 not meas. 4ms 8ms 38ms 326ms 0 not stated market_resolved e 1,730 not meas. 50ms 266ms 3.4s 2.4min 0 not stated market_resolved h 1,735 not meas. 13ms 55ms 131ms 284ms 0 not stated new_market a 342 not meas. 157ms 473ms 26.0s 1.7min 0 not stated new_market b 342 not meas. 175ms 505ms 16.9s 1.0min 0 not stated new_market c 342 not meas. 40ms 11.3s 24.5s 1.9min 0 not stated new_market e 342 not meas. 187ms 12.7s 55.5s 3.0min 0 not stated new_market h 342 not meas. 62ms 416ms 14.1s 59.5s 0 not stated price_change a 73,254,522 not meas. 40ms 66ms 2.3s 17.0s 0 not stated price_change b 73,249,440 not meas. 50ms 86ms 2.9s 19.3s 0 not stated price_change c 73,320,002 not meas. 4ms 7ms 75ms 5.2s 0 not stated price_change e 71,777,610 not meas. 47ms 163ms 7.7s 25.9s 0 not stated price_change h 73,275,224 not meas. 12ms 18ms 179ms 7.2s 0 not stated tick_size_change a 2,144 not meas. 40ms 45ms 198ms 337ms 0 not stated tick_size_change b 2,144 not meas. 49ms 61ms 186ms 348ms 0 not stated tick_size_change c 2,144 not meas. 4ms 6ms 32ms 303ms 0 not stated tick_size_change e 2,088 not meas. 49ms 128ms 9.0s 10.1s 0 not stated tick_size_change h 2,144 not meas. 12ms 16ms 35ms 311ms 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-27/21/2026-08-27T21.parquet sha256sum 2026-08-27T21.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.