Hour audit: 2026-09-03T08
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-03T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T08:00:00.002914426+00:00 · last event 2026-09-03T08:59:59.999997908+00:00
VOLUME 79,130,198 rows · 772,874,453 bytes (737.07 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 78,570,161 · h: 77,105,416 · e: 75,845,026 · b: 61,139,514 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,113 (0.14%) · h: 3,150,270 (3.98%) · e: 75,843,989 (95.85%) · b: 28,826 (0.04%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 79,130,198 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 05003e1f6f2cbaa342ac90b2ac77c8f4286f5553fcc2ad2e212b8410609463f2
the corpus checksum ledger names this file with the same digest
joined 79,131,657 to merged 79,130,198, minus 1,459 (minus 0.0018%)
boundary drops 1,459 · 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-03T09:48:35Z 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 7,102,606 81,782,527 0-27 e1268e3a5e93eafe6627077ade9e7e491eeade01a8e745e27c26de999bfc2428 book 211,622 20,882,604 28-28 3427af2191501a784f9eb662c37d05f72b5b8d6b53b4e151540856546760beca last_trade_price 61,947 3,444,091 29-29 f8db30b506f3af93e3b47bb6dfae1721d88d3c0d42d77743ff3a90b658924032 market_resolved 529 88,365 30-30 be27345939647ca4ac43a2bf5a188cea64cdfea0eaa1d254a4b088420209b1fb new_market 890 89,643 31-31 56638de865550b728fb155effc239ff09c012023745a3465fdc062363533ffd6 price_change 71,750,224 665,593,742 32-305 585b7adf0a7a46bab39da4483b42dd5d4e83a8a5c7b68f49270edcd4eff47a2e tick_size_change 2,380 88,099 306-306 14b0f3fa530c966fe755c0addc514096d6d344de2ab19a61e9d84978be6a451c EVENT MIX count share price_change 71,750,224 90.67% best_bid_ask 7,102,606 8.98% book 211,622 0.27% last_trade_price 61,947 0.08% tick_size_change 2,380 <0.01% new_market 890 <0.01% market_resolved 529 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,102,704 7,102,606 98 96 FULL book 211,632 211,622 10 34,819 FULL last_trade_price 61,948 61,947 1 1 FULL market_resolved 529 529 0 2 FULL new_market 890 890 0 0 FULL price_change 71,751,574 71,750,224 1,350 48,867 FULL tick_size_change 2,380 2,380 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 7,093,501 4 54ms 74ms 671ms 20.6s 0 transport_latency_assumed best_bid_ask c 7,102,552 350 10ms 18ms 67ms 2.0s 0 transport_latency_assumed best_bid_ask e 7,081,993 7,081,912 39ms 91ms 1.5s 23.9s 0 transport_latency_assumed best_bid_ask h 7,102,220 20,340 18ms 24ms 150ms 7.5s 0 transport_latency_assumed book b 150,874 26,752 213ms 5.8min 11.8d 77.9d 0 book_staleness book c 143,134 14,464 14ms 4.1s 14.9h 96.4d 0 book_staleness book e 155,563 155,559 322ms 43.0min 3.1d 96.4d 0 book_staleness book h 134,938 14,847 34ms 655ms 4.0h 77.9d 0 book_staleness last_trade_price b 59,329 5 113ms 5.6s 15.1s 20.6s 0 transport_latency_assumed last_trade_price c 61,913 11 17ms 46ms 202ms 4.4s 0 transport_latency_assumed last_trade_price e 57,998 57,998 102ms 5.8s 19.7s 23.9s 0 transport_latency_assumed last_trade_price h 61,918 3,933 30ms 374ms 1.5s 5.4s 0 transport_latency_assumed market_resolved b 529 not meas. 55ms 484ms 754ms 942ms 0 transport_latency_assumed market_resolved c 529 not meas. 10ms 19ms 132ms 309ms 0 transport_latency_assumed market_resolved e 527 527 41ms 437ms 2.0s 12.9s 0 transport_latency_assumed market_resolved h 529 2 19ms 146ms 270ms 343ms 0 transport_latency_assumed new_market b 583 97 237ms 22.5s 55.8s 1.2min 0 transport_latency_assumed new_market c 583 20 57ms 23.4s 43.7s 59.7s 0 transport_latency_assumed new_market e 583 583 216ms 24.2s 36.4s 1.1min 0 transport_latency_assumed new_market h 583 190 103ms 20.9s 41.9s 1.1min 0 transport_latency_assumed price_change b 53,832,318 1,968 54ms 132ms 8.3s 20.6s 0 transport_latency_assumed price_change c 71,259,070 92,268 10ms 18ms 102ms 2.0s 0 transport_latency_assumed price_change e 68,545,982 68,545,030 40ms 139ms 6.4s 23.9s 0 transport_latency_assumed price_change h 69,802,848 3,110,958 18ms 30ms 342ms 8.4s 0 transport_latency_assumed tick_size_change b 2,380 not meas. 54ms 65ms 195ms 1.2s 0 transport_latency_assumed tick_size_change c 2,380 not meas. 10ms 18ms 42ms 248ms 0 transport_latency_assumed tick_size_change e 2,380 2,380 40ms 106ms 177ms 2.9s 0 transport_latency_assumed tick_size_change h 2,380 not meas. 18ms 23ms 78ms 276ms 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/08/2026-09-03T08.parquet sha256sum 2026-09-03T08.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.