Hour audit: 2026-09-01T13
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-01T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-01T13:00:00.037333618+00:00 · last event 2026-09-01T13:59:59.999949397+00:00
VOLUME 99,615,368 rows · 1,020,708,851 bytes (973.42 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 99,036,107 · e: 98,116,721 · c: 70,917,959 · b: 117,455 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,104,375 (1.11%) · e: 98,113,552 (98.49%) · c: 365,773 (0.37%) · b: 31,668 (0.03%) (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 99,615,368 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 2811ab9321243e523779b63c9b6b17384876abfd1ce8e2806f24cacb108fe859
the corpus checksum ledger names this file with the same digest
joined 99,618,766 to merged 99,615,368, minus 3,398 (minus 0.0034%)
boundary drops 3,398 · 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-02T12:52:28Z 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,106,721 99,208,049 0-34 25c7ceb870848cbd5ed68153286c7576ffec14657717be641cef14010f96164f book 837,758 68,965,331 35-38 e2cc4af07aa048666b23a45d9002fd575f7c55e19e5acd55a1e0ad2ba5a21f70 last_trade_price 87,465 4,749,071 39-39 f5bd48d3188d28790a918b588a77160321d6f15ecdc6e80532713071f2a056bb market_resolved 1,154 146,036 40-40 ef82a083aef9d98c19f2ce0d4526b7724f0c20a3a77b88638657b42a71a7b11e new_market 2,598 317,698 41-41 375670d78f008045ce390fc6206aed634e8f4d4e3c5d6aa8c422c0883e101a51 price_change 89,576,136 846,060,761 42-383 c1c793fb3f955f08ab38caedefe18bee6fe80e1869b751f70efb145039a6744c tick_size_change 3,536 128,231 384-384 1d05768291705786cd95caa059c0553a234471143c23a34b3ef93f826b88a175 EVENT MIX count share price_change 89,576,136 89.92% best_bid_ask 9,106,721 9.14% book 837,758 0.84% last_trade_price 87,465 0.09% tick_size_change 3,536 <0.01% new_market 2,598 <0.01% market_resolved 1,154 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,106,848 9,106,721 127 66,298 FULL book 838,126 837,758 368 173,089 FULL last_trade_price 87,467 87,465 2 3,822 FULL market_resolved 1,154 1,154 0 884 PARTIAL new_market 2,601 2,598 3 2,007 FULL price_change 89,579,034 89,576,136 2,898 123,282 FULL tick_size_change 3,536 3,536 0 884 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,726 not meas. 53ms 112ms 614ms 725ms 0 transport_latency_assumed best_bid_ask c 6,419,689 829 5ms 9ms 61ms 11.4s 0 transport_latency_assumed best_bid_ask e 9,071,509 9,071,382 41ms 89ms 2.5s 23.0s 0 transport_latency_assumed best_bid_ask h 9,103,389 34,510 18ms 29ms 174ms 7.6s 0 transport_latency_assumed book b 47,829 29,714 2.7min 6.0d 32.2d 94.6d 0 book_staleness book c 579,840 353,968 1.6min 7.6h 29.8d 94.6d 0 book_staleness book e 325,356 325,196 6.6s 3.5h 24.0d 94.7d 0 book_staleness book h 314,857 128,880 224ms 2.7h 24.0d 94.6d 0 book_staleness last_trade_price b 8 not meas. 68ms 91ms 103ms 104ms 0 transport_latency_assumed last_trade_price c 63,612 120 10ms 39ms 185ms 5.3s 0 transport_latency_assumed last_trade_price e 81,449 81,447 84ms 6.0s 15.9s 22.8s 0 transport_latency_assumed last_trade_price h 87,088 5,898 27ms 329ms 1.9s 6.5s 0 transport_latency_assumed market_resolved c 874 256 7ms 15.1min 19.1min 19.1min 0 transport_latency_assumed market_resolved e 880 880 42ms 364ms 1.0min 1.2min 0 transport_latency_assumed market_resolved h 884 18 19ms 133ms 58.0s 1.0min 0 transport_latency_assumed new_market b 2,000 1,954 2.0h 3.1h 3.5h 3.5h 0 transport_latency_assumed new_market c 425 136 86ms 14.9min 15.0min 15.1min 0 transport_latency_assumed new_market e 425 425 181ms 10.7s 22.3s 25.0s 0 transport_latency_assumed new_market h 425 83 82ms 14.6s 24.0s 55.0s 0 transport_latency_assumed price_change b 58,892 not meas. 53ms 71ms 404ms 918ms 0 transport_latency_assumed price_change c 63,850,743 10,464 5ms 10ms 81ms 13.6s 0 transport_latency_assumed price_change e 88,633,566 88,630,686 42ms 153ms 7.0s 23.1s 0 transport_latency_assumed price_change h 89,525,928 934,986 18ms 36ms 363ms 7.8s 0 transport_latency_assumed tick_size_change c 2,776 not meas. 5ms 9ms 36ms 70ms 0 transport_latency_assumed tick_size_change e 3,536 3,536 41ms 53ms 150ms 21.5s 0 transport_latency_assumed tick_size_change h 3,536 not meas. 18ms 26ms 80ms 4.6s 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-01/13/2026-09-01T13.parquet sha256sum 2026-09-01T13.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.