Hour audit: 2026-09-02T19
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-02T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T19:00:00.019100094+00:00 · last event 2026-09-02T19:59:59.999861306+00:00
VOLUME 124,697,042 rows · 1,350,855,561 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 122,698,534 · e: 121,658,460 · c: 118,292,262 · b: 98,528,357 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,198,738 (0.96%) · e: 121,629,022 (97.54%) · c: 411,164 (0.33%) · b: 1,458,118 (1.17%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 124,697,042 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 793e61b49d3fd2df2f0a77e818f583ce5d86794a266076052c222a204e9778c2
the corpus checksum ledger names this file with the same digest
joined 124,740,299 to merged 124,697,042, minus 43,257 (minus 0.0347%)
boundary drops 43,257 · 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-02T22:04:32Z 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 12,582,316 146,810,486 0-47 acc78eb1873930caf33c502dfad158544e2f884af52a6d2338d7d96c5864a4a3 book 2,160,288 97,908,564 48-56 a3fd2b1ad09de1322f430c7271e1365d28ca8f3e2f1e342a3512f4739723ac08 last_trade_price 77,580 4,364,461 57-57 e8455764cd561d847369d7a5fe92fbc1b612df9e14e1fc8fd4e25d844e0eacea market_resolved 1,385 151,674 58-58 e5324971cff448ccc78bb824d4b1457ae105512865727b3eb242c9c540eba74a new_market 16,647 1,288,468 59-59 14ce26cc19ba2e380a6300a1f779dea1e77ca6dbdaac2d196644b84d23f0fbe9 price_change 109,850,106 1,098,597,238 60-479 daa77607a88914e68d25a7c103e35ccac6eec2b12cc4a9d784f8eb92f7474c47 tick_size_change 8,720 316,674 480-480 5c79148a80ba63014d79170ca5d961db9b6874536420128773a7ff442b905864 EVENT MIX count share price_change 109,850,106 88.09% best_bid_ask 12,582,316 10.09% book 2,160,288 1.73% last_trade_price 77,580 0.06% new_market 16,647 0.01% tick_size_change 8,720 <0.01% market_resolved 1,385 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,585,935 12,582,316 3,619 8,238 FULL book 2,161,188 2,160,288 900 173,390 FULL last_trade_price 77,610 77,580 30 537 FULL market_resolved 1,385 1,385 0 16 FULL new_market 16,647 16,647 0 109 FULL price_change 109,888,814 109,850,106 38,708 4,338 FULL tick_size_change 8,720 8,720 0 534 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,955,371 290 56ms 279ms 1.2s 25.4s 0 transport_latency_assumed best_bid_ask c 12,078,208 3,001 5ms 42ms 445ms 6.8s 0 transport_latency_assumed best_bid_ask e 12,530,618 12,528,459 44ms 379ms 4.3s 48.0s 0 transport_latency_assumed best_bid_ask h 12,575,999 50,566 19ms 106ms 1.1s 1.2min 0 transport_latency_assumed book b 1,938,588 1,451,271 2.4min 8.7h 31.3d 95.9d 0 book_staleness book c 595,975 383,952 52.9s 2.3h 26.3d 95.9d 0 book_staleness book e 266,736 266,680 2.4s 51.9min 24.3d 95.9d 0 book_staleness book h 224,118 58,385 80ms 10.1min 11.3d 95.9d 0 book_staleness last_trade_price b 57,360 6 120ms 3.4s 14.5s 25.3s 0 transport_latency_assumed last_trade_price c 74,869 75 12ms 85ms 499ms 5.1s 0 transport_latency_assumed last_trade_price e 71,048 71,023 128ms 4.4s 20.8s 37.8s 0 transport_latency_assumed last_trade_price h 77,419 6,476 39ms 416ms 3.8s 54.5s 0 transport_latency_assumed market_resolved b 1,213 436 310ms 12.0min 17.4min 17.4min 0 transport_latency_assumed market_resolved c 900 42 5ms 73ms 3.8min 4.5min 0 transport_latency_assumed market_resolved e 906 906 44ms 641ms 56.3s 56.4s 0 transport_latency_assumed market_resolved h 906 1 22ms 208ms 57.3s 57.4s 0 transport_latency_assumed new_market b 12,461 4,847 28.7s 9.9min 14.7min 15.1min 0 transport_latency_assumed new_market c 7,723 1,162 126ms 1.8min 7.0min 10.1min 0 transport_latency_assumed new_market e 7,826 7,826 304ms 1.1min 6.9min 10.1min 0 transport_latency_assumed new_market h 7,798 2,812 199ms 1.0min 7.3min 10.5min 0 transport_latency_assumed price_change b 86,556,780 1,268 57ms 350ms 3.9s 25.4s 0 transport_latency_assumed price_change c 105,526,603 22,932 5ms 44ms 451ms 6.8s 0 transport_latency_assumed price_change e 108,772,622 108,745,424 45ms 508ms 8.7s 48.6s 0 transport_latency_assumed price_change h 109,803,574 1,080,482 20ms 121ms 1.3s 1.2min 0 transport_latency_assumed tick_size_change b 6,584 not meas. 55ms 265ms 746ms 3.3s 0 transport_latency_assumed tick_size_change c 7,984 not meas. 5ms 31ms 386ms 690ms 0 transport_latency_assumed tick_size_change e 8,704 8,704 49ms 364ms 2.5s 6.3s 0 transport_latency_assumed tick_size_change h 8,720 16 19ms 148ms 881ms 14.9s 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-02/19/2026-09-02T19.parquet sha256sum 2026-09-02T19.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.