Hour audit: 2026-09-03T07
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-03T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T07:00:00.026017420+00:00 · last event 2026-09-03T07:59:59.999996113+00:00
VOLUME 77,116,935 rows · 791,738,164 bytes (755.06 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 74,298,061 · h: 72,072,949 · e: 71,503,772 · b: 54,303,033 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 1,266,647 (1.64%) · h: 3,779,031 (4.90%) · e: 71,501,973 (92.72%) · b: 569,284 (0.74%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 77,116,935 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 98f53214e091919c6f4b455d0551a68899e049df70145d686c253163ba7f4230
the corpus checksum ledger names this file with the same digest
joined 77,119,216 to merged 77,116,935, minus 2,281 (minus 0.0030%)
boundary drops 2,281 · 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-03T08:47:57Z 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 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,733,180 79,192,228 0-25 ee59626d8615d1a2577e30416c11741500992eead09cc1c040d518769884feae book 1,059,406 73,282,481 26-30 6cf114091c382ee7ee0dc1af2c3ab95f50baccb6a253eb698a10a134b0ee884d last_trade_price 55,486 3,077,621 31-31 c1cc8448f535bca75e3876834f61402488c510c39da642a7e1c881d94a490902 market_resolved 548 88,680 32-32 ef20f9e9d407e07d6c5b62611ea552a098ac47d20c375096077494ae5a0067a6 new_market 1,077 106,884 33-33 ac03d49f205d791068bcaa276d59853c3f5f2ebd458e72fea56af1b23948f4cd price_change 69,265,374 635,035,834 34-298 bd01644d6fbd080c46065456041f68b02f91b8fcd5a3b09cd647e754c8add681 tick_size_change 1,864 68,890 299-299 0803f808940e2d73a7045bfc4d2d50f81ee2fb697b94c9d1e60d073baa5aceb2 EVENT MIX count share price_change 69,265,374 89.82% best_bid_ask 6,733,180 8.73% book 1,059,406 1.37% last_trade_price 55,486 0.07% tick_size_change 1,864 <0.01% new_market 1,077 <0.01% market_resolved 548 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,733,268 6,733,180 88 2,531 FULL book 1,060,246 1,059,406 840 92,757 FULL last_trade_price 55,487 55,486 1 141 FULL market_resolved 548 548 0 81 FULL new_market 1,077 1,077 0 0 FULL price_change 69,266,726 69,265,374 1,352 10,230 FULL tick_size_change 1,864 1,864 0 20 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 6,610,343 117,216 54ms 77ms 711ms 25.8s 0 transport_latency_assumed best_bid_ask c 6,481,862 49,284 11ms 16ms 97ms 4.9s 0 transport_latency_assumed best_bid_ask e 6,513,475 6,513,407 40ms 109ms 1.1s 26.0s 0 transport_latency_assumed best_bid_ask h 6,449,416 53,273 17ms 22ms 159ms 6.5s 0 transport_latency_assumed book b 431,526 88,738 2.0min 10.5h 27.3d 96.4d 0 book_staleness book c 668,189 161,802 3.5min 10.9h 31.5d 96.4d 0 book_staleness book e 571,661 571,067 2.3min 10.4h 31.8d 96.4d 0 book_staleness book h 608,835 237,799 3.2min 10.7h 30.6d 96.4d 0 book_staleness last_trade_price b 50,543 1,826 97ms 4.7s 13.8s 25.9s 0 transport_latency_assumed last_trade_price c 51,573 619 18ms 45ms 229ms 3.9s 0 transport_latency_assumed last_trade_price e 50,575 50,574 100ms 5.4s 12.7s 25.9s 0 transport_latency_assumed last_trade_price h 51,263 2,467 27ms 387ms 2.4s 4.8s 0 transport_latency_assumed market_resolved b 498 21 55ms 400ms 802ms 1.4min 0 transport_latency_assumed market_resolved c 502 42 11ms 17ms 2.5min 2.5min 0 transport_latency_assumed market_resolved e 476 476 40ms 410ms 1.1min 1.2min 0 transport_latency_assumed market_resolved h 460 9 18ms 132ms 1.3min 1.3min 0 transport_latency_assumed new_market b 707 77 235ms 19.3s 56.5s 1.2min 0 transport_latency_assumed new_market c 707 68 72ms 15.9s 46.3s 1.2min 0 transport_latency_assumed new_market e 707 707 248ms 23.4s 1.2min 1.5min 0 transport_latency_assumed new_market h 707 225 118ms 18.7s 45.1s 57.2s 0 transport_latency_assumed price_change b 47,207,576 361,374 54ms 122ms 6.4s 25.9s 0 transport_latency_assumed price_change c 67,093,428 1,054,832 12ms 17ms 131ms 5.1s 0 transport_latency_assumed price_change e 64,365,050 64,363,914 41ms 134ms 5.2s 26.0s 0 transport_latency_assumed price_change h 64,960,472 3,485,254 17ms 26ms 335ms 6.5s 0 transport_latency_assumed tick_size_change b 1,840 32 54ms 66ms 224ms 773ms 0 transport_latency_assumed tick_size_change c 1,800 not meas. 12ms 16ms 88ms 394ms 0 transport_latency_assumed tick_size_change e 1,828 1,828 41ms 92ms 223ms 798ms 0 transport_latency_assumed tick_size_change h 1,796 4 17ms 24ms 150ms 305ms 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/07/2026-09-03T07.parquet sha256sum 2026-09-03T07.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.