Hour audit: 2026-09-03T03
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-03T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T03:00:00.027818533+00:00 · last event 2026-09-03T03:59:59.999994024+00:00
VOLUME 98,061,718 rows · 962,333,948 bytes (917.75 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 97,918,955 · e: 97,741,929 · h: 95,989,218 · b: 94,785,959 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 33,274 (0.03%) · e: 97,740,721 (99.67%) · h: 258,503 (0.26%) · b: 29,220 (0.03%) (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 98,061,718 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 a41891f61c6ca6ee64ed6b536d14cd000e70fb28c3ff7bd1f895669ee582256f
the corpus checksum ledger names this file with the same digest
joined 98,063,336 to merged 98,061,718, minus 1,618 (minus 0.0016%)
boundary drops 1,618 · 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-03T04:53:02Z 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 9,332,622 102,976,855 0-35 6e245e50e4d57c7221749b17161df5659b803b43bbef3d3cad0dafddc522eb3c book 281,271 28,088,473 36-37 70f6be9fe834da85b71688712562b5497ee41291f138e98bda8c35e81732dd8b last_trade_price 58,642 3,244,162 38-38 3bebd66d6e727b9145a50526a337a02ec4397339accd76cad5546e6bb4d09686 market_resolved 1,282 188,559 39-39 9e11ee78cbfe8af349a8ab310fa08d8927c32c6182431ae1f5d5616e0bbdb415 new_market 387 45,252 40-40 aa915012a76957907f4819fb13ebd0a087da1fad8476442957fde7637c294962 price_change 88,385,370 826,590,594 41-378 95054020edb024a2f073555fab22e0646350381a285c5c1d660744431126e8a0 tick_size_change 2,144 79,234 379-379 a962f5dc816771e8e5f51903c221704386c45f96221965e5830d2cb235635211 EVENT MIX count share price_change 88,385,370 90.13% best_bid_ask 9,332,622 9.52% book 281,271 0.29% last_trade_price 58,642 0.06% tick_size_change 2,144 <0.01% market_resolved 1,282 <0.01% new_market 387 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,332,746 9,332,622 124 3,411 FULL book 281,303 281,271 32 68,478 FULL last_trade_price 58,642 58,642 0 128 FULL market_resolved 1,282 1,282 0 21 FULL new_market 387 387 0 0 FULL price_change 88,386,832 88,385,370 1,462 5,408 FULL tick_size_change 2,144 2,144 0 23 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,040,662 not meas. 55ms 70ms 374ms 22.9s 0 transport_latency_assumed best_bid_ask c 9,332,372 367 4ms 7ms 39ms 1.8s 0 transport_latency_assumed best_bid_ask e 9,325,852 9,325,758 38ms 70ms 854ms 30.9s 0 transport_latency_assumed best_bid_ask h 9,143,349 6,497 17ms 22ms 114ms 5.3s 0 transport_latency_assumed book b 148,684 28,177 144ms 23.4min 11.6d 77.7d 0 book_staleness book c 152,001 27,845 7ms 10.8min 11.6d 96.2d 0 book_staleness book e 160,975 160,963 281ms 1.1h 22.4d 96.2d 0 book_staleness book h 185,502 64,286 67ms 2.9h 22.4d 96.2d 0 book_staleness last_trade_price b 56,422 7 80ms 3.0s 11.9s 23.0s 0 transport_latency_assumed last_trade_price c 58,586 12 10ms 36ms 152ms 5.0s 0 transport_latency_assumed last_trade_price e 57,452 57,452 76ms 3.5s 12.4s 30.9s 0 transport_latency_assumed last_trade_price h 58,336 1,171 26ms 290ms 1.3s 5.0s 0 transport_latency_assumed market_resolved b 1,145 81 56ms 235ms 2.9s 2.3min 0 transport_latency_assumed market_resolved c 1,160 4 4ms 93ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 1,160 1,160 38ms 417ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 1,153 37 18ms 433ms 1.0min 2.0min 0 transport_latency_assumed new_market b 290 21 119ms 12.6s 51.3s 58.0s 0 transport_latency_assumed new_market c 290 26 41ms 326ms 15.7s 56.0s 0 transport_latency_assumed new_market e 290 290 150ms 10.1s 16.9s 1.0min 0 transport_latency_assumed new_market h 290 50 69ms 12.4s 57.3s 1.7min 0 transport_latency_assumed price_change b 85,536,668 934 55ms 83ms 2.1s 23.2s 0 transport_latency_assumed price_change c 88,372,402 5,020 4ms 7ms 47ms 3.3s 0 transport_latency_assumed price_change e 88,194,056 88,192,954 39ms 105ms 2.8s 30.9s 0 transport_latency_assumed price_change h 86,598,488 186,462 17ms 25ms 230ms 6.2s 0 transport_latency_assumed tick_size_change b 2,088 not meas. 55ms 66ms 127ms 521ms 0 transport_latency_assumed tick_size_change c 2,144 not meas. 4ms 7ms 41ms 116ms 0 transport_latency_assumed tick_size_change e 2,144 2,144 38ms 55ms 161ms 2.4s 0 transport_latency_assumed tick_size_change h 2,100 not meas. 17ms 22ms 136ms 220ms 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/03/2026-09-03T03.parquet sha256sum 2026-09-03T03.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.