Hour audit: 2026-08-29T10
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-29T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T10:00:00.001823882+00:00 · last event 2026-08-29T10:59:59.999901474+00:00
VOLUME 97,463,485 rows · 988,477,322 bytes (942.69 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured h: 97,432,710 · c: 97,427,230 · a: 97,422,125 · e: 97,304,723 (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 (rows of the merged file that came from it; these partition it)
28 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 ff08ef9695b359a3246b0f6fefc9923286a47ab506276cbabe722e1970b0ef13
the corpus checksum ledger names this file with the same digest
joined 97,464,448 to merged 97,463,485, minus 963 (minus 0.0010%)
boundary drops 963 · 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,955,378 83,366,980 0-26 d8c1e8cee8025acce9591a8a68499f0f10720b5b668100f330076d98b03e507d book 142,904 14,098,436 27-27 310ac187f4944d68f4ae56dcbc659afbc601241b1f75e8d520ef335089badb82 last_trade_price 57,304 3,363,475 28-28 5a0bc739aa5c541613f485aac57a24d87ee398dd05b20c374be007f52f8e6996 market_resolved 508 79,160 29-29 65b409ab7022d5a9b74d51616497e91cc95c0b43e1d4252c8e9945d1c471c67d new_market 2,023 198,187 30-30 d51ad288b0c4ffef610b9354757082bf4da4012f25de472a5a42a57f80fa9601 price_change 90,300,012 886,063,696 31-375 e78fe111c8d97c78c227c0d79d415f3294806879eff1f82e460de0771164dbf2 tick_size_change 5,356 195,321 376-376 733a0e7354af4a3d282a1e2ffd2623407afaeb30868948abf273b1332bbaa3d7 EVENT MIX count share price_change 90,300,012 92.65% best_bid_ask 6,955,378 7.14% book 142,904 0.15% last_trade_price 57,304 0.06% tick_size_change 5,356 <0.01% new_market 2,023 <0.01% market_resolved 508 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,955,450 6,955,378 72 71,343 PARTIAL book 142,905 142,904 1 15,029 PARTIAL last_trade_price 57,304 57,304 0 4,087 PARTIAL market_resolved 508 508 0 483 PARTIAL new_market 2,023 2,023 0 1,309 PARTIAL price_change 90,300,902 90,300,012 890 134,912 PARTIAL tick_size_change 5,356 5,356 0 1,339 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 6,952,342 not meas. 37ms 46ms 386ms 11.8s 0 not stated best_bid_ask c 6,954,161 not meas. 4ms 7ms 135ms 2.2s 0 not stated best_bid_ask e 6,947,057 not meas. 43ms 108ms 2.1s 30.9s 0 not stated best_bid_ask h 6,953,293 not meas. 12ms 17ms 174ms 48.1s 0 not stated book a 128,060 not meas. 44ms 3.1s 3.9h 73.0d 0 not stated book c 121,520 not meas. 7ms 27ms 1.7min 73.0d 0 not stated book e 128,330 not meas. 58ms 5.8s 3.9h 17.7d 0 not stated book h 119,579 not meas. 17ms 82ms 1.4s 20.9d 0 not stated last_trade_price a 57,239 not meas. 49ms 690ms 6.3s 11.8s 0 not stated last_trade_price c 57,279 not meas. 9ms 38ms 222ms 5.0s 0 not stated last_trade_price e 56,856 not meas. 62ms 2.3s 9.6s 28.9s 0 not stated last_trade_price h 57,278 not meas. 17ms 74ms 715ms 9.3s 0 not stated market_resolved a 483 not meas. 38ms 342ms 1.0min 1.0min 0 not stated market_resolved c 483 not meas. 4ms 10ms 131ms 317ms 0 not stated market_resolved e 483 not meas. 44ms 423ms 1.0min 1.0min 0 not stated market_resolved h 483 not meas. 13ms 76ms 264ms 6.5s 0 not stated new_market a 1,309 not meas. 187ms 17.1s 23.6s 1.2min 0 not stated new_market c 1,309 not meas. 81ms 18.5s 24.9s 57.8s 0 not stated new_market e 1,309 not meas. 239ms 17.4s 25.1s 1.0min 0 not stated new_market h 1,309 not meas. 151ms 18.8s 25.4s 1.2min 0 not stated price_change a 90,277,336 not meas. 38ms 56ms 571ms 11.8s 0 not stated price_change c 90,287,122 not meas. 4ms 8ms 159ms 3.3s 0 not stated price_change e 90,165,332 not meas. 43ms 126ms 3.3s 31.0s 0 not stated price_change h 90,295,412 not meas. 12ms 19ms 216ms 48.3s 0 not stated tick_size_change a 5,356 not meas. 38ms 43ms 109ms 404ms 0 not stated tick_size_change c 5,356 not meas. 4ms 6ms 23ms 305ms 0 not stated tick_size_change e 5,356 not meas. 43ms 109ms 268ms 2.1s 0 not stated tick_size_change h 5,356 not meas. 12ms 16ms 35ms 250ms 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-29/10/2026-08-29T10.parquet sha256sum 2026-08-29T10.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.