Hour audit: 2026-09-03T09
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-03T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T09:00:00.003161106+00:00 · last event 2026-09-03T09:59:59.999951293+00:00
VOLUME 91,124,631 rows · 894,403,962 bytes (852.97 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 90,602,588 · h: 88,914,558 · e: 88,140,387 · b: 73,535,570 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 91,310 (0.10%) · h: 2,879,147 (3.16%) · e: 88,138,411 (96.72%) · b: 15,763 (0.02%) (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 91,124,631 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 434e56d116eddffce02ea30b980025bb5b51c46f71a44b4a151bf9a3e10378db
the corpus checksum ledger names this file with the same digest
joined 91,126,828 to merged 91,124,631, minus 2,197 (minus 0.0024%)
boundary drops 2,197 · 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-03T10:50: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 8,365,178 94,464,366 0-31 8afc34a1b334e6a425b59b22ed5cf8ff16aa9ce83aba667895c070bcce85d51b book 168,589 15,955,883 32-32 080b112d3320a555c7bf033afed48379138a771d6bb52b362db4a7684af81057 last_trade_price 69,206 3,811,971 33-33 deeb7e2d5a0449b25e7daef6a6ae3d5da6687aab8eea1f6d8a19c34f44cc3fd4 market_resolved 769 120,833 34-34 e5d55f9f1da74ea81da275d52c6156aa5b1dea1c648dde04dae85653548071b0 new_market 795 88,248 35-35 b9246a77defa3cd9d6c16f2e661881e916c96b89ada9482bcdcc091424a74f0d price_change 82,517,642 778,833,753 36-350 7f8848ee3d166b2e48a5aaab365a421f32e3c4cb93e7c8c2307a668681ca0527 tick_size_change 2,452 90,924 351-351 3d37924f530892d1249100b6b77ae78b2abd412ede81a4339888747c0dc69624 EVENT MIX count share price_change 82,517,642 90.55% best_bid_ask 8,365,178 9.18% book 168,589 0.19% last_trade_price 69,206 0.08% tick_size_change 2,452 <0.01% new_market 795 <0.01% market_resolved 769 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,365,255 8,365,178 77 77 FULL book 168,593 168,589 4 9,099 FULL last_trade_price 69,206 69,206 0 0 FULL market_resolved 769 769 0 0 FULL new_market 795 795 0 0 FULL price_change 82,519,758 82,517,642 2,116 47,466 FULL tick_size_change 2,452 2,452 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,356,992 4 53ms 73ms 625ms 34.6s 0 transport_latency_assumed best_bid_ask c 8,364,959 352 6ms 10ms 63ms 5.9s 0 transport_latency_assumed best_bid_ask e 8,354,905 8,354,857 39ms 81ms 1.0s 22.7s 0 transport_latency_assumed best_bid_ask h 8,364,616 9,965 18ms 25ms 143ms 5.8s 0 transport_latency_assumed book b 152,812 13,982 143ms 15.4s 13.1h 96.5d 0 book_staleness book c 146,003 2,961 9ms 36ms 5.7min 77.9d 0 book_staleness book e 145,265 145,263 116ms 5.8s 3.5h 12.6d 0 book_staleness book h 143,966 6,383 30ms 354ms 2.1s 77.9d 0 book_staleness last_trade_price b 66,828 7 103ms 4.7s 18.1s 34.7s 0 transport_latency_assumed last_trade_price c 69,116 26 12ms 43ms 193ms 3.3s 0 transport_latency_assumed last_trade_price e 66,607 66,607 90ms 3.9s 15.7s 22.7s 0 transport_latency_assumed last_trade_price h 69,098 2,566 29ms 347ms 1.2s 3.3s 0 transport_latency_assumed market_resolved b 746 not meas. 54ms 450ms 56.8s 56.8s 0 transport_latency_assumed market_resolved c 746 not meas. 6ms 24ms 57.5s 57.5s 0 transport_latency_assumed market_resolved e 746 746 39ms 591ms 58.4s 58.5s 0 transport_latency_assumed market_resolved h 746 23 18ms 148ms 52.9s 52.9s 0 transport_latency_assumed new_market b 590 70 86ms 16.3s 48.5s 1.3min 0 transport_latency_assumed new_market c 590 15 52ms 15.4s 41.9s 46.4s 0 transport_latency_assumed new_market e 590 590 186ms 19.3s 46.3s 1.9min 0 transport_latency_assumed new_market h 590 120 93ms 14.8s 48.5s 1.2min 0 transport_latency_assumed price_change b 64,955,150 1,700 54ms 116ms 4.9s 34.7s 0 transport_latency_assumed price_change c 82,018,722 87,956 6ms 10ms 86ms 7.2s 0 transport_latency_assumed price_change e 79,569,822 79,567,896 39ms 124ms 3.8s 22.8s 0 transport_latency_assumed price_change h 80,333,090 2,860,090 18ms 30ms 271ms 6.4s 0 transport_latency_assumed tick_size_change b 2,452 not meas. 53ms 64ms 161ms 4.3s 0 transport_latency_assumed tick_size_change c 2,452 not meas. 6ms 9ms 36ms 54ms 0 transport_latency_assumed tick_size_change e 2,452 2,452 39ms 99ms 169ms 1.0s 0 transport_latency_assumed tick_size_change h 2,452 not meas. 18ms 22ms 57ms 303ms 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/09/2026-09-03T09.parquet sha256sum 2026-09-03T09.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.