Hour audit: 2026-09-03T11
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-03T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T11:00:00.016362703+00:00 · last event 2026-09-03T11:59:59.999967660+00:00
VOLUME 96,375,928 rows · 980,343,855 bytes (934.93 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 95,813,864 · h: 94,347,052 · e: 93,185,140 · b: 80,036,371 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 125,226 (0.13%) · h: 3,027,805 (3.14%) · e: 93,183,691 (96.69%) · b: 39,206 (0.04%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,375,928 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 d2040a917f62aa6464f8eee36f07f56c07704742a8b1dd5edc97ecad8335e937
the corpus checksum ledger names this file with the same digest
joined 96,377,639 to merged 96,375,928, minus 1,711 (minus 0.0018%)
boundary drops 1,711 · 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 merged 2026-09-03T12:53:43Z as bceh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM an incident recorded by the venue intersects this hour: Venue investigated order-cancellation problems, 2026-09-03T11:41Z to 2026-09-03T12:11ZThe 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,723,217 98,704,570 0-29 c96716a5aeabd6b8e3085493d58ab8c5b52988176822f2e1242e87e534170d6e book 249,487 24,733,267 30-30 32628b0635cf55604a5b50bd95053b353b8b00b1734f04d6b21aadccab2cb346 last_trade_price 69,386 3,834,470 31-31 9b31e41c9f4872c56fbc5b1e10cfd6f20ab2e08d4307db69234246140524b9c9 market_resolved 744 121,123 32-32 50f9e7aa06343d4c447d22c7a8c777ebd260cf74ce8740939773184e06e42424 new_market 1,326 139,328 33-33 f96376fbca5319182e21840ebe26b8d465b7136063e0c873442cd811d34dfffb price_change 88,329,076 851,616,001 34-370 ae4e4ac303b9ae38c393e049d339f069c7105956fde30f1fa57c6ee8f7466c7b tick_size_change 2,692 97,673 371-371 de2c7f19ac2b3bcdf7f96724144e3d7b988e386539320c5ec4440e7c733f31d8 EVENT MIX count share price_change 88,329,076 91.65% best_bid_ask 7,723,217 8.01% book 249,487 0.26% last_trade_price 69,386 0.07% tick_size_change 2,692 <0.01% new_market 1,326 <0.01% market_resolved 744 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,723,350 7,723,217 133 216 FULL book 249,487 249,487 0 46,037 FULL last_trade_price 69,388 69,386 2 0 FULL market_resolved 744 744 0 1 FULL new_market 1,326 1,326 0 0 FULL price_change 88,330,652 88,329,076 1,576 63,507 FULL tick_size_change 2,692 2,692 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 7,717,928 142 53ms 81ms 655ms 18.0s 0 transport_latency_assumed best_bid_ask c 7,722,615 788 5ms 9ms 110ms 2.3s 0 transport_latency_assumed best_bid_ask e 7,706,722 7,706,609 41ms 101ms 1.5s 24.0s 0 transport_latency_assumed best_bid_ask h 7,721,853 15,678 18ms 26ms 181ms 34.8s 0 transport_latency_assumed book b 175,554 31,892 145ms 2.8min 11.9d 96.5d 0 book_staleness book c 174,681 30,197 8ms 1.9min 6.3d 96.5d 0 book_staleness book e 167,390 167,390 123ms 1.5min 3.8d 39.9d 0 book_staleness book h 159,510 20,008 27ms 2.3s 15.5h 96.5d 0 book_staleness last_trade_price b 68,390 3 85ms 2.3s 11.0s 18.0s 0 transport_latency_assumed last_trade_price c 69,324 8 11ms 43ms 207ms 4.5s 0 transport_latency_assumed last_trade_price e 67,432 67,432 74ms 2.6s 13.3s 24.0s 0 transport_latency_assumed last_trade_price h 69,353 1,943 27ms 184ms 975ms 6.6s 0 transport_latency_assumed market_resolved b 731 not meas. 53ms 365ms 651ms 874ms 0 transport_latency_assumed market_resolved c 732 6 5ms 10ms 58.7s 1.0min 0 transport_latency_assumed market_resolved e 732 732 41ms 337ms 2.9s 59.9s 0 transport_latency_assumed market_resolved h 732 6 18ms 104ms 236ms 466ms 0 transport_latency_assumed new_market b 918 123 238ms 18.1s 29.8s 1.1min 0 transport_latency_assumed new_market c 918 63 68ms 17.1s 32.9s 1.2min 0 transport_latency_assumed new_market e 918 918 223ms 18.4s 34.0s 1.0min 0 transport_latency_assumed new_market h 918 222 113ms 15.6s 28.3s 1.1min 0 transport_latency_assumed price_change b 72,070,158 7,046 53ms 133ms 2.5s 18.0s 0 transport_latency_assumed price_change c 87,842,902 94,164 5ms 10ms 218ms 3.7s 0 transport_latency_assumed price_change e 85,239,254 85,237,918 41ms 154ms 3.1s 24.0s 0 transport_latency_assumed price_change h 86,391,994 2,989,948 18ms 32ms 314ms 35.0s 0 transport_latency_assumed tick_size_change b 2,692 not meas. 53ms 69ms 501ms 1.0s 0 transport_latency_assumed tick_size_change c 2,692 not meas. 5ms 12ms 374ms 531ms 0 transport_latency_assumed tick_size_change e 2,692 2,692 41ms 109ms 503ms 3.5s 0 transport_latency_assumed tick_size_change h 2,692 not meas. 18ms 30ms 317ms 399ms 0 transport_latency_assumed
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-09-03/11/2026-09-03T11.parquet sha256sum 2026-09-03T11.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.