Hour audit: 2026-08-29T07
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-29T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-08-29T07:00:00.035938805+00:00 · last event 2026-08-29T07:59:59.999971547+00:00
VOLUME 90,153,239 rows · 879,272,184 bytes (838.54 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 90,101,215 · h: 90,093,243 · a: 90,065,256 · e: 90,025,681 (each machine's own feed; these overlap and do not sum to the file)
supplied c: not measured · h: 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 e0ff316859f510cbef3bea0577c486818fc9795931acf75ee106885a446e7148
the corpus checksum ledger names this file with the same digest
joined 90,154,502 to merged 90,153,239, minus 1,263 (minus 0.0014%)
boundary drops 1,263 · 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,912,254 98,119,048 0-33 0260665009d2f50c479a7c337834d4e0829d40749f84379189e069c1d19b37ae book 150,511 15,449,854 34-34 b129f51a0a79a35436d3668c3bc518ca775cab1b721179a3deb0fea775662f25 last_trade_price 46,487 2,711,271 35-35 223f6fe225e9ba2e8f277100035b8112159e13de5db89368e293ab154a1b839b market_resolved 523 81,611 36-36 ebfc8a875fc704aa8c7f86085aa78653c1008a324bd841de34d7527bd97a5c93 new_market 1,240 122,200 37-37 5e6f3008255e85e88e283538ed7a93dfdcf8345866cd58c89d51ff5032d1fb03 price_change 81,040,436 761,693,668 38-347 376d8788fa69695c8f72cea8aa511025bbae01046bb07c1ffb23658ffe66bbf1 tick_size_change 1,788 65,375 348-348 d3e5861678eeec1c3fb5ab3264a0d8ad5cd0482e85767c4e525e1f4c893c3b52 EVENT MIX count share price_change 81,040,436 89.89% best_bid_ask 8,912,254 9.89% book 150,511 0.17% last_trade_price 46,487 0.05% tick_size_change 1,788 <0.01% new_market 1,240 <0.01% market_resolved 523 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,912,360 8,912,254 106 70,155 PARTIAL book 150,521 150,511 10 29,077 PARTIAL last_trade_price 46,490 46,487 3 3,483 PARTIAL market_resolved 523 523 0 497 PARTIAL new_market 1,240 1,240 0 798 PARTIAL price_change 81,041,580 81,040,436 1,144 148,209 PARTIAL tick_size_change 1,788 1,788 0 447 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,909,457 not meas. 34ms 40ms 264ms 11.3s 0 not stated best_bid_ask c 8,911,790 not meas. 6ms 9ms 72ms 1.6s 0 not stated best_bid_ask e 8,909,091 not meas. 45ms 90ms 1.6s 14.7s 0 not stated best_bid_ask h 8,911,103 not meas. 11ms 14ms 125ms 18.9s 0 not stated book a 108,694 not meas. 58ms 23.0s 1.1d 91.4d 0 not stated book c 103,212 not meas. 9ms 100ms 5.6h 72.9d 0 not stated book e 122,212 not meas. 130ms 2.3min 6.7d 91.4d 0 not stated book h 103,286 not meas. 18ms 449ms 5.6h 72.9d 0 not stated last_trade_price a 46,046 not meas. 50ms 1.0s 5.5s 11.3s 0 not stated last_trade_price c 46,464 not meas. 11ms 40ms 201ms 5.0s 0 not stated last_trade_price e 46,155 not meas. 68ms 2.7s 9.9s 14.7s 0 not stated last_trade_price h 46,373 not meas. 17ms 88ms 817ms 6.6s 0 not stated market_resolved a 497 not meas. 37ms 439ms 55.4s 55.4s 0 not stated market_resolved c 497 not meas. 6ms 10ms 60ms 367ms 0 not stated market_resolved e 497 not meas. 45ms 907ms 55.4s 55.4s 0 not stated market_resolved h 497 not meas. 12ms 95ms 55.7s 55.8s 0 not stated new_market a 798 not meas. 240ms 16.6s 21.3s 57.0s 0 not stated new_market c 798 not meas. 127ms 15.8s 20.3s 58.8s 0 not stated new_market e 798 not meas. 201ms 15.9s 25.5s 53.5s 0 not stated new_market h 798 not meas. 152ms 16.2s 20.5s 1.7min 0 not stated price_change a 80,997,976 not meas. 34ms 45ms 556ms 11.3s 0 not stated price_change c 81,036,666 not meas. 6ms 9ms 94ms 5.4s 0 not stated price_change e 80,945,140 not meas. 45ms 111ms 2.8s 14.7s 0 not stated price_change h 81,029,398 not meas. 11ms 16ms 170ms 22.6s 0 not stated tick_size_change a 1,788 not meas. 34ms 40ms 215ms 544ms 0 not stated tick_size_change c 1,788 not meas. 6ms 11ms 80ms 153ms 0 not stated tick_size_change e 1,788 not meas. 45ms 115ms 3.2s 5.9s 0 not stated tick_size_change h 1,788 not meas. 12ms 15ms 80ms 301ms 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/07/2026-08-29T07.parquet sha256sum 2026-08-29T07.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.