Hour audit: 2026-09-04T06
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-04T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T06:00:00.000655417+00:00 · last event 2026-09-04T06:59:59.999977454+00:00
VOLUME 82,368,224 rows · 801,668,950 bytes (764.53 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 82,175,646 · e: 62,152,867 · h: 62,058,617 · b: 55,193,902 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 9,970,337 (12.10%) · e: 62,151,785 (75.46%) · h: 10,204,754 (12.39%) · b: 41,348 (0.05%) (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 82,368,224 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 19d000cffe60508753aa4ebbfa336ff5ef9e716bbc4c7d76cacb1bae8733e1b0
the corpus checksum ledger names this file with the same digest
joined 82,369,584 to merged 82,368,224, minus 1,360 (minus 0.0017%)
boundary drops 1,360 · 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-04T07:47:43Z 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,084,656 88,193,882 0-30 4dab3065830b4d10db1bf66982436764684f6ff352f45142e8d6890e88cf9d37 book 333,329 33,121,274 31-32 55ec8771024136fd1de2fc88fe794693987780f624b081d8a0234469e5d4c4f2 last_trade_price 56,651 3,133,113 33-33 7dc4f9781e086f4a474b9797e2116f9cd0313a3fad42e65253a8e04f66c67855 market_resolved 548 88,094 34-34 29cca93a44127ac2786b9986d2a3252de3f53f61590be99facafc2308230a0a4 new_market 1,004 108,055 35-35 aff059acaf93edb0a37c33cb37fda6526ce30f25f95dbfe774d07d6f5cc3abd8 price_change 73,890,276 676,019,348 36-317 3b1441581bd777444043d2be16deb22e227ed16407111438afdce6ef5d4a46bd tick_size_change 1,760 63,684 318-318 32f1d458a71ae0a99017211d96992711422b65df03ae93cf405b43c47cb6e232 EVENT MIX count share price_change 73,890,276 89.71% best_bid_ask 8,084,656 9.82% book 333,329 0.40% last_trade_price 56,651 0.07% tick_size_change 1,760 <0.01% new_market 1,004 <0.01% market_resolved 548 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,084,806 8,084,656 150 92 FULL book 333,365 333,329 36 85,373 FULL last_trade_price 56,651 56,651 0 0 FULL market_resolved 548 548 0 0 FULL new_market 1,004 1,004 0 0 FULL price_change 73,891,450 73,890,276 1,174 99,888 FULL tick_size_change 1,760 1,760 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,082,174 26 49ms 61ms 153ms 2.9s 0 transport_latency_assumed best_bid_ask c 8,084,386 516 4ms 6ms 45ms 3.3s 0 transport_latency_assumed best_bid_ask e 8,082,023 8,081,881 42ms 48ms 206ms 2.1s 0 transport_latency_assumed best_bid_ask h 8,078,129 2,233 17ms 21ms 97ms 19.0s 0 transport_latency_assumed book b 166,282 40,055 59ms 44.5min 12.7d 78.9d 0 book_staleness book c 157,337 34,137 7ms 23.9min 12.7d 97.3d 0 book_staleness book e 245,958 245,948 3.4s 5.0h 16.5d 97.3d 0 book_staleness book h 130,435 13,189 21ms 3.6s 10.2h 78.9d 0 book_staleness last_trade_price b 56,555 3 56ms 120ms 515ms 5.0s 0 transport_latency_assumed last_trade_price c 56,618 20 9ms 38ms 169ms 4.9s 0 transport_latency_assumed last_trade_price e 56,567 56,567 49ms 121ms 587ms 4.9s 0 transport_latency_assumed last_trade_price h 55,814 61 23ms 63ms 270ms 5.1s 0 transport_latency_assumed market_resolved b 547 not meas. 51ms 237ms 638ms 59.9s 0 transport_latency_assumed market_resolved c 547 1 4ms 7ms 24ms 147ms 0 transport_latency_assumed market_resolved e 547 547 43ms 241ms 931ms 59.4s 0 transport_latency_assumed market_resolved h 547 not meas. 18ms 73ms 257ms 59.4s 0 transport_latency_assumed new_market b 720 54 175ms 14.5s 41.2s 1.0min 0 transport_latency_assumed new_market c 720 121 60ms 19.7s 40.9s 1.1min 0 transport_latency_assumed new_market e 720 720 144ms 20.2s 44.2s 47.6s 0 transport_latency_assumed new_market h 720 109 68ms 13.8s 45.1s 1.1min 0 transport_latency_assumed price_change b 46,885,864 1,210 49ms 62ms 217ms 3.2s 0 transport_latency_assumed price_change c 73,874,278 9,935,542 4ms 7ms 60ms 3.7s 0 transport_latency_assumed price_change e 53,765,292 53,764,362 42ms 58ms 257ms 4.5s 0 transport_latency_assumed price_change h 53,791,212 10,189,162 17ms 23ms 132ms 18.8s 0 transport_latency_assumed tick_size_change b 1,760 not meas. 49ms 61ms 142ms 356ms 0 transport_latency_assumed tick_size_change c 1,760 not meas. 4ms 6ms 24ms 51ms 0 transport_latency_assumed tick_size_change e 1,760 1,760 42ms 47ms 122ms 212ms 0 transport_latency_assumed tick_size_change h 1,760 not meas. 17ms 20ms 39ms 265ms 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-04/06/2026-09-04T06.parquet sha256sum 2026-09-04T06.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.