Hour audit: 2026-09-03T10
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-03T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T10:00:00.014187826+00:00 · last event 2026-09-03T10:59:59.999982121+00:00
VOLUME 91,225,295 rows · 889,317,876 bytes (848.12 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 90,737,139 · h: 89,249,157 · e: 88,481,411 · b: 74,373,242 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 77,303 (0.08%) · h: 2,659,828 (2.92%) · e: 88,480,579 (96.99%) · b: 7,585 (0.01%) (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 91,225,295 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 f5b9ee6460130bf0514aa00b2c050e9369638f4cf7a9a0fccc9817cca319af14
the corpus checksum ledger names this file with the same digest
joined 91,226,797 to merged 91,225,295, minus 1,502 (minus 0.0016%)
boundary drops 1,502 · 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-03T11:52:29Z 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,292,108 92,930,805 0-31 3bc8142dba97208ae27e0b41ba91746ea452cf0e8b795b91c2c6f21076745af3 book 146,011 13,556,008 32-32 930896a95e64ad3157e429f1bf2630202b6956eee670ffd78abcc83a4072d491 last_trade_price 65,340 3,547,528 33-33 b50da5b251b417002744667476ada03ecf6487f481a575b8ed8d0b0105de3b3e market_resolved 1,015 155,125 34-34 429e32dfd8d66b5f3a289181a32a3f439f9e60278d46f6afb138fa1f291f3054 new_market 955 93,357 35-35 2d7a96d3ff2a151d52321b02cbe3d29157c890c4a81bbf9addbe6c57b854b0c7 price_change 82,717,278 777,899,205 36-351 4ea694fecc914a6bb34b3787594284697604fd89fc88c59dfb1181a1ae4347a6 tick_size_change 2,588 95,034 352-352 4fa5fcbceb2633998f39350c2a16ffec873581a5258c01c5f248d9a8fac0acd3 EVENT MIX count share price_change 82,717,278 90.67% best_bid_ask 8,292,108 9.09% book 146,011 0.16% last_trade_price 65,340 0.07% tick_size_change 2,588 <0.01% market_resolved 1,015 <0.01% new_market 955 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,292,188 8,292,108 80 149 FULL book 146,011 146,011 0 2,936 FULL last_trade_price 65,340 65,340 0 0 FULL market_resolved 1,015 1,015 0 0 FULL new_market 955 955 0 0 FULL price_change 82,718,700 82,717,278 1,422 47,335 FULL tick_size_change 2,588 2,588 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,286,436 36 53ms 72ms 513ms 24.0s 0 transport_latency_assumed best_bid_ask c 8,291,377 504 5ms 8ms 62ms 5.5s 0 transport_latency_assumed best_bid_ask e 8,282,093 8,282,037 40ms 77ms 850ms 17.3s 0 transport_latency_assumed best_bid_ask h 8,291,298 9,531 18ms 24ms 129ms 8.2s 0 transport_latency_assumed book b 136,564 4,489 111ms 5.1s 3.6h 78.0d 0 book_staleness book c 134,890 655 7ms 26ms 620ms 30.8d 0 book_staleness book e 137,240 137,240 111ms 5.2s 4.5h 43.8d 0 book_staleness book h 134,912 3,627 26ms 246ms 1.5s 30.8d 0 book_staleness last_trade_price b 63,996 5 93ms 3.8s 12.3s 24.1s 0 transport_latency_assumed last_trade_price c 65,150 6 11ms 39ms 195ms 4.7s 0 transport_latency_assumed last_trade_price e 63,870 63,870 89ms 3.8s 11.0s 17.1s 0 transport_latency_assumed last_trade_price h 65,279 1,459 27ms 254ms 1.1s 5.4s 0 transport_latency_assumed market_resolved b 970 35 54ms 444ms 59.5s 59.6s 0 transport_latency_assumed market_resolved c 970 not meas. 5ms 581ms 53.5s 53.5s 0 transport_latency_assumed market_resolved e 970 970 41ms 1.3s 54.7s 54.7s 0 transport_latency_assumed market_resolved h 970 10 18ms 223ms 1.0min 1.0min 0 transport_latency_assumed new_market b 608 56 221ms 23.2s 52.6s 1.1min 0 transport_latency_assumed new_market c 608 88 62ms 24.1s 55.0s 1.3min 0 transport_latency_assumed new_market e 608 608 208ms 25.2s 42.5s 1.1min 0 transport_latency_assumed new_market h 608 203 115ms 23.6s 49.7s 1.1min 0 transport_latency_assumed price_change b 65,882,080 2,964 53ms 116ms 3.9s 24.1s 0 transport_latency_assumed price_change c 82,241,556 76,050 5ms 8ms 75ms 5.7s 0 transport_latency_assumed price_change e 79,994,042 79,993,266 41ms 121ms 3.6s 17.3s 0 transport_latency_assumed price_change h 80,753,502 2,644,998 18ms 29ms 236ms 9.5s 0 transport_latency_assumed tick_size_change b 2,588 not meas. 53ms 65ms 183ms 1.1s 0 transport_latency_assumed tick_size_change c 2,588 not meas. 5ms 7ms 38ms 195ms 0 transport_latency_assumed tick_size_change e 2,588 2,588 40ms 95ms 152ms 6.0s 0 transport_latency_assumed tick_size_change h 2,588 not meas. 18ms 21ms 63ms 124ms 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/10/2026-09-03T10.parquet sha256sum 2026-09-03T10.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.