Hour audit: 2026-08-28T23
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-28T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-28T23:00:00.034934170+00:00 · last event 2026-08-28T23:59:59.999996502+00:00
VOLUME 109,718,124 rows · 1,167,432,816 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES abceh — 5 machines contributed rows
captured h: 109,223,772 · c: 109,207,324 · a: 109,108,808 · e: 108,678,753 · b: 9,755,637 (each machine's own feed; these overlap and do not sum to the file)
supplied h: not measured · c: not measured · a: not measured · e: 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 57b4f6a36fdb2a386a68ac4e019b28ed8d1abf920dd73574bffdac96424a1028
the corpus checksum ledger names this file with the same digest
joined 109,719,914 to merged 109,718,124, minus 1,790 (minus 0.0016%)
boundary drops 1,790 · 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 7,971,244 93,327,200 0-30 1dd46aadb8acf2103d7f5de5494b9d3e41e5ed9bf0a02091bdebba1b0fc8dfde book 623,266 58,026,792 31-33 14462a98b9d7fba4a5914cd104c6a194758b4ab2e6c5133cc9b954334b9d0c74 last_trade_price 61,723 3,495,858 34-34 9436411ef23bf5a55443661bfff6500d226cca09a955d57fd29107975a86e92f market_resolved 1,158 181,124 35-35 1f7cf84cf27045409b11f730919235ac319944496010f593b84fafc8e4b8ae39 new_market 1,945 165,429 36-36 2f7ba92c1f8f1a40d965fd6043520de9e07826f6afd11954249ec81efb75e215 price_change 101,056,488 1,010,897,636 37-422 e7854202b0b92573c80e6d6157115e910c5090e7c32609ef70afa6eeb6ff643d tick_size_change 2,300 85,836 423-423 b17d0924cf7840a74bccd77aa576d6900f66cfde16709032799b65da44491a16 EVENT MIX count share price_change 101,056,488 92.11% best_bid_ask 7,971,244 7.27% book 623,266 0.57% last_trade_price 61,723 0.06% tick_size_change 2,300 <0.01% new_market 1,945 <0.01% market_resolved 1,158 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,971,396 7,971,244 152 36,628 FULL book 623,346 623,266 80 175,384 FULL last_trade_price 61,723 61,723 0 2,496 FULL market_resolved 1,158 1,158 0 950 FULL new_market 1,945 1,945 0 728 FULL price_change 101,058,046 101,056,488 1,558 20,934 FULL tick_size_change 2,300 2,300 0 489 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,965,074 not meas. 39ms 61ms 410ms 16.1s 0 not stated best_bid_ask b 752,488 not meas. 53ms 131ms 695ms 18.8s 0 not stated best_bid_ask c 7,971,088 not meas. 4ms 9ms 120ms 1.8s 0 not stated best_bid_ask e 7,953,979 not meas. 43ms 154ms 3.0s 36.6s 0 not stated best_bid_ask h 7,970,978 not meas. 13ms 23ms 249ms 42.0s 0 not stated book a 127,882 not meas. 64ms 2.4s 31.5min 72.6d 0 not stated book b 494,697 not meas. 2.8min 17.6h 26.5d 91.0d 0 not stated book c 137,490 not meas. 7ms 142ms 7.7h 72.6d 0 not stated book e 128,804 not meas. 87ms 6.2s 49.9min 2.4d 0 not stated book h 132,650 not meas. 21ms 284ms 1.1h 72.5d 0 not stated last_trade_price a 59,951 not meas. 61ms 1.6s 8.3s 16.1s 0 not stated last_trade_price b 6,789 not meas. 112ms 3.2s 18.2s 18.8s 0 not stated last_trade_price c 61,676 not meas. 9ms 41ms 228ms 5.0s 0 not stated last_trade_price e 59,358 not meas. 79ms 3.9s 15.0s 33.6s 0 not stated last_trade_price h 61,698 not meas. 19ms 148ms 922ms 9.4s 0 not stated market_resolved a 1,119 not meas. 40ms 397ms 51.1s 53.5s 0 not stated market_resolved b 171 not meas. 61ms 323ms 655ms 737ms 0 not stated market_resolved c 1,119 not meas. 4ms 17ms 45.9s 59.4s 0 not stated market_resolved e 1,119 not meas. 44ms 548ms 47.8s 1.0min 0 not stated market_resolved h 1,119 not meas. 13ms 93ms 1.0min 1.0min 0 not stated new_market a 1,023 not meas. 239ms 22.0s 1.2min 2.5h 0 not stated new_market b 703 not meas. 5.7min 22.8min 1.7h 2.0h 0 not stated new_market c 1,023 not meas. 84ms 24.0s 1.2min 1.6h 0 not stated new_market e 1,023 not meas. 216ms 20.3s 55.3s 2.5h 0 not stated new_market h 1,023 not meas. 149ms 18.2s 1.2min 1.0h 0 not stated price_change a 100,951,459 not meas. 40ms 77ms 1.0s 16.3s 0 not stated price_change b 8,500,445 not meas. 53ms 178ms 4.0s 18.8s 0 not stated price_change c 101,032,628 not meas. 4ms 8ms 132ms 2.6s 0 not stated price_change e 100,532,170 not meas. 44ms 202ms 5.4s 38.6s 0 not stated price_change h 101,054,004 not meas. 13ms 22ms 279ms 42.0s 0 not stated tick_size_change a 2,300 not meas. 40ms 125ms 586ms 1.1s 0 not stated tick_size_change b 344 not meas. 61ms 786ms 1.4s 1.4s 0 not stated tick_size_change c 2,300 not meas. 4ms 32ms 461ms 744ms 0 not stated tick_size_change e 2,300 not meas. 44ms 247ms 2.6s 5.2s 0 not stated tick_size_change h 2,300 not meas. 13ms 37ms 562ms 821ms 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/23/2026-08-28T23.parquet sha256sum 2026-08-28T23.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.