Hour audit: 2026-09-03T05
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-03T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T05:00:00.020887604+00:00 · last event 2026-09-03T05:59:59.999985372+00:00
VOLUME 92,335,376 rows · 920,342,339 bytes (877.71 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 92,152,783 · e: 91,622,645 · h: 90,880,712 · b: 89,703,294 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 89,844 (0.10%) · e: 91,621,511 (99.23%) · h: 566,050 (0.61%) · b: 57,971 (0.06%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,335,376 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 b77bdad2ce49f32b86dee2a5fc7042ec3acff563a69a272cc960a8da455ce716
the corpus checksum ledger names this file with the same digest
joined 92,336,909 to merged 92,335,376, minus 1,533 (minus 0.0017%)
boundary drops 1,533 · 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-03T06:51:37Z 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,613,327 96,844,424 0-32 f95fc6000e6a449734d74798570c70cb1befaaa2724eef541ba063381b260804 book 376,864 37,266,668 33-34 9bc8d0549da965a4cd298672f3df5cbeff96d7b22b6547df654571d27111fa96 last_trade_price 61,212 3,342,768 35-35 ce8df3e5eb6bd57fb3bac09dbd2b0b1a24fa87113e2aa700240d328018520d57 market_resolved 963 150,886 36-36 eacf4b8bd224addd82e8901ebac501f5f04488a6cc8d922573996e87e434e673 new_market 788 84,358 37-37 d545951321247083371385d2a1a3b20ef5ec170a5a33744d776f867e12ad1a2e price_change 83,279,990 781,517,152 38-355 d3566ee52c37f771b166399f6324d36db4b1f9e7d0f8032970610eeba90ad380 tick_size_change 2,232 82,674 356-356 b476e56554cb7483a956e6adf98b6d71879325d1f25109677c7f5cdcf1f679c5 EVENT MIX count share price_change 83,279,990 90.19% best_bid_ask 8,613,327 9.33% book 376,864 0.41% last_trade_price 61,212 0.07% tick_size_change 2,232 <0.01% market_resolved 963 <0.01% new_market 788 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,613,452 8,613,327 125 3,072 FULL book 376,878 376,864 14 104,466 FULL last_trade_price 61,214 61,212 2 126 FULL market_resolved 963 963 0 23 FULL new_market 788 788 0 0 FULL price_change 83,281,382 83,279,990 1,392 5,220 FULL tick_size_change 2,232 2,232 0 25 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,381,346 2 55ms 74ms 509ms 18.2s 0 transport_latency_assumed best_bid_ask c 8,612,933 1,435 4ms 7ms 47ms 1.8s 0 transport_latency_assumed best_bid_ask e 8,596,043 8,595,963 41ms 81ms 1.7s 22.8s 0 transport_latency_assumed best_bid_ask h 8,512,812 15,927 18ms 23ms 143ms 10.1s 0 transport_latency_assumed book b 199,808 57,573 1.4s 3.0h 22.5d 96.3d 0 book_staleness book c 203,609 64,445 11ms 2.9h 22.5d 96.3d 0 book_staleness book e 200,611 200,605 1.7s 2.5h 21.6d 96.3d 0 book_staleness book h 180,279 54,241 49ms 50.8min 11.7d 96.3d 0 book_staleness last_trade_price b 58,937 3 87ms 4.5s 14.6s 18.2s 0 transport_latency_assumed last_trade_price c 61,184 97 10ms 38ms 174ms 4.8s 0 transport_latency_assumed last_trade_price e 58,356 58,354 71ms 4.9s 15.9s 22.8s 0 transport_latency_assumed last_trade_price h 60,744 2,758 27ms 293ms 1.2s 4.8s 0 transport_latency_assumed market_resolved b 922 7 56ms 349ms 733ms 2.4min 0 transport_latency_assumed market_resolved c 937 13 4ms 7ms 45.2s 45.3s 0 transport_latency_assumed market_resolved e 937 937 42ms 213ms 667ms 1.5s 0 transport_latency_assumed market_resolved h 929 6 18ms 89ms 503ms 2.2min 0 transport_latency_assumed new_market b 556 16 236ms 22.5s 1.1min 2.4min 0 transport_latency_assumed new_market c 556 52 62ms 21.4s 1.0min 1.1min 0 transport_latency_assumed new_market e 556 556 208ms 19.0s 1.0min 1.1min 0 transport_latency_assumed new_market h 556 164 109ms 21.8s 1.0min 1.3min 0 transport_latency_assumed price_change b 81,059,553 370 55ms 100ms 4.2s 18.2s 0 transport_latency_assumed price_change c 83,271,332 23,802 4ms 7ms 66ms 1.8s 0 transport_latency_assumed price_change e 82,763,910 82,762,864 42ms 122ms 5.4s 22.8s 0 transport_latency_assumed price_change h 82,123,204 492,954 18ms 27ms 295ms 10.2s 0 transport_latency_assumed tick_size_change b 2,172 not meas. 55ms 67ms 171ms 298ms 0 transport_latency_assumed tick_size_change c 2,232 not meas. 4ms 6ms 27ms 254ms 0 transport_latency_assumed tick_size_change e 2,232 2,232 41ms 97ms 181ms 306ms 0 transport_latency_assumed tick_size_change h 2,188 not meas. 18ms 27ms 107ms 313ms 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/05/2026-09-03T05.parquet sha256sum 2026-09-03T05.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.