Hour audit: 2026-09-03T00
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-03T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T00:00:00.021810338+00:00 · last event 2026-09-03T00:59:59.999998649+00:00
VOLUME 107,299,695 rows · 1,095,823,733 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 106,812,082 · h: 106,762,523 · e: 106,344,250 · b: 102,375,290 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 58,995 (0.05%) · h: 456,233 (0.43%) · e: 106,343,347 (99.11%) · b: 441,120 (0.41%) (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 107,299,695 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 c5daaae36a0caf01878e6363c1fd894e0aaebe516cb3a945d79577afe4633462
the corpus checksum ledger names this file with the same digest
joined 107,301,043 to merged 107,299,695, minus 1,348 (minus 0.0013%)
boundary drops 1,348 · 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-03T01:55:10Z 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,394,104 135,090,275 0-47 fbf26ba3bc7c872fc953757fabf3af9948ae04be257c4d63c74c1c7e07ac1aac book 563,764 56,312,187 48-50 24fb4acec382a4bc27a112fe8cdde7f08c30ba25419dc8f012eda2b36fdff2f0 last_trade_price 64,027 3,581,166 51-51 d5b3f794167d1636cf821d7ddaf7f3b036a69b63dbf5b279f9ec0af388992f3c market_resolved 1,096 146,275 52-52 1e88e5460e6dbbf40407aa6cd1109ea3c58c6894501cd22b24b5ca31702e42b7 new_market 602 66,928 53-53 6feb968c3dc8696373832445155504ffbd425ae745b2907ed16ca37941261fdd price_change 94,272,654 899,277,508 54-413 08174b2f822d1c163749b289622dbf012ee62b911e6a901daaff412ad0f7e572 tick_size_change 3,448 126,069 414-414 8b43b637b577240c7519af80c288fb8036ea7997a94f864b88943183ea9b45fd EVENT MIX count share price_change 94,272,654 87.86% best_bid_ask 12,394,104 11.55% book 563,764 0.53% last_trade_price 64,027 0.06% tick_size_change 3,448 <0.01% market_resolved 1,096 <0.01% new_market 602 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,394,216 12,394,104 112 824 FULL book 563,820 563,764 56 188,397 FULL last_trade_price 64,027 64,027 0 73 FULL market_resolved 1,096 1,096 0 18 FULL new_market 602 602 0 0 FULL price_change 94,273,834 94,272,654 1,180 298 FULL tick_size_change 3,448 3,448 0 47 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,835,699 8 56ms 88ms 559ms 29.4s 0 transport_latency_assumed best_bid_ask c 12,391,048 2,062 4ms 9ms 68ms 3.3s 0 transport_latency_assumed best_bid_ask e 12,364,891 12,364,808 41ms 89ms 959ms 28.6s 0 transport_latency_assumed best_bid_ask h 12,388,697 27,226 18ms 29ms 144ms 23.2s 0 transport_latency_assumed book b 520,593 364,739 1.8min 5.6h 28.0d 96.1d 0 book_staleness book c 173,611 40,335 9ms 25.7min 11.4d 96.1d 0 book_staleness book e 146,159 146,113 105ms 1.8min 19.5h 39.1d 0 book_staleness book h 137,718 12,577 29ms 624ms 3.6h 96.1d 0 book_staleness last_trade_price b 59,606 9 97ms 4.2s 22.0s 29.4s 0 transport_latency_assumed last_trade_price c 63,983 15 10ms 41ms 215ms 5.0s 0 transport_latency_assumed last_trade_price e 60,763 60,763 70ms 3.8s 14.7s 28.8s 0 transport_latency_assumed last_trade_price h 63,881 3,240 31ms 406ms 1.8s 6.7s 0 transport_latency_assumed market_resolved b 935 187 61ms 4.4min 5.9min 5.9min 0 transport_latency_assumed market_resolved c 892 14 5ms 16ms 1.0min 1.1min 0 transport_latency_assumed market_resolved e 892 892 40ms 420ms 50.6s 1.5min 0 transport_latency_assumed market_resolved h 892 3 18ms 128ms 50.6s 1.0min 0 transport_latency_assumed new_market b 429 21 195ms 16.3s 38.1s 6.8min 0 transport_latency_assumed new_market c 427 39 49ms 15.9s 35.2s 59.9s 0 transport_latency_assumed new_market e 427 427 188ms 14.3s 36.1s 1.7min 0 transport_latency_assumed new_market h 427 115 86ms 15.1s 38.1s 1.0min 0 transport_latency_assumed price_change b 89,954,764 76,156 56ms 109ms 3.2s 29.4s 0 transport_latency_assumed price_change c 94,178,673 16,530 4ms 8ms 93ms 3.8s 0 transport_latency_assumed price_change e 93,767,674 93,766,900 41ms 121ms 3.7s 28.8s 0 transport_latency_assumed price_change h 94,167,460 413,068 18ms 31ms 314ms 23.3s 0 transport_latency_assumed tick_size_change b 3,264 not meas. 56ms 70ms 180ms 308ms 0 transport_latency_assumed tick_size_change c 3,448 not meas. 5ms 8ms 27ms 223ms 0 transport_latency_assumed tick_size_change e 3,444 3,444 41ms 118ms 345ms 2.3s 0 transport_latency_assumed tick_size_change h 3,448 4 18ms 37ms 78ms 117ms 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/00/2026-09-03T00.parquet sha256sum 2026-09-03T00.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.