Hour audit: 2026-09-04T17
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-04T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T17:00:00.005569035+00:00 · last event 2026-09-04T17:59:59.999966007+00:00
VOLUME 109,477,706 rows · 1,147,258,989 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 108,539,423 · h: 108,534,562 · e: 108,460,100 · b: 100,215,285 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 14,891 (0.01%) · h: 91,004 (0.08%) · e: 108,454,906 (99.07%) · b: 916,905 (0.84%) (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 109,477,706 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 cdd7596e5f1272d5fc9d3c055132f8ae0362bcb7be6594b672cfaea433a3740e
the corpus checksum ledger names this file with the same digest
joined 109,490,097 to merged 109,477,706, minus 12,391 (minus 0.0113%)
boundary drops 12,391 · 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-04T19:39:55Z 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 11,092,049 124,235,451 0-42 12de8488885f1610d14129622c18e9ad4aecb16f6ac7e1c709057454044a71f7 book 964,170 70,200,477 43-46 1dfe9ec87339e29ea158c61b72ba4da6bd02c57dfa132886902a7c8e0ddf60d7 last_trade_price 65,798 3,680,668 47-47 6a44983c49481378ebd466869e25d8778e15ecb5fe0194eafec36836a29a0431 market_resolved 1,465 181,321 48-48 205dac2cd78498ef4acbc6920df63218d74e0af8d0a308cd404cbeac56a4b4f5 new_market 4,698 469,198 49-49 d36d88cffe29be133476bcd225023952fe59456dfadb7fdbc26570f8720cbeed price_change 97,344,986 947,079,505 50-421 91843cf8ca63993d576686c058e62ee0711f9444dae7f381ede3025006f5a353 tick_size_change 4,540 165,524 422-422 6526f9247970577c0b929d4632630af3b88135e0a77034629bc13de8931dcbde EVENT MIX count share price_change 97,344,986 88.92% best_bid_ask 11,092,049 10.13% book 964,170 0.88% last_trade_price 65,798 0.06% new_market 4,698 <0.01% tick_size_change 4,540 <0.01% market_resolved 1,465 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,093,253 11,092,049 1,204 1,338 FULL book 964,344 964,170 174 188,103 FULL last_trade_price 65,798 65,798 0 176 FULL market_resolved 1,465 1,465 0 17 FULL new_market 4,699 4,698 1 1 FULL price_change 97,355,998 97,344,986 11,012 537 FULL tick_size_change 4,540 4,540 0 76 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 10,173,937 402 49ms 77ms 377ms 19.9s 0 transport_latency_assumed best_bid_ask c 11,090,124 1,541 3ms 8ms 157ms 10.1s 0 transport_latency_assumed best_bid_ask e 11,086,585 11,086,173 39ms 73ms 413ms 28.3s 0 transport_latency_assumed best_bid_ask h 11,089,787 3,933 18ms 31ms 390ms 47.9s 0 transport_latency_assumed book b 942,083 810,017 2.6min 14.8h 32.9d 97.8d 0 book_staleness book c 145,767 5,673 5ms 72ms 48.0min 90.1d 0 book_staleness book e 144,416 144,416 42ms 401ms 27.9min 38.0d 0 book_staleness book h 142,823 4,064 23ms 120ms 55.7s 79.2d 0 book_staleness last_trade_price b 59,935 3 64ms 260ms 3.5s 20.0s 0 transport_latency_assumed last_trade_price c 65,741 4 8ms 43ms 398ms 5.0s 0 transport_latency_assumed last_trade_price e 65,490 65,490 48ms 234ms 4.4s 28.2s 0 transport_latency_assumed last_trade_price h 65,748 301 24ms 81ms 751ms 9.6s 0 transport_latency_assumed market_resolved b 1,288 334 58ms 8.0min 14.2min 14.3min 0 transport_latency_assumed market_resolved c 1,094 22 3ms 22ms 59.3s 1.0min 0 transport_latency_assumed market_resolved e 1,094 1,094 39ms 194ms 708ms 1.0min 0 transport_latency_assumed market_resolved h 1,094 15 18ms 127ms 46.5s 1.0min 0 transport_latency_assumed new_market b 3,168 445 217ms 35.0s 5.7min 10.2min 0 transport_latency_assumed new_market c 3,103 317 86ms 23.9s 1.5min 2.2min 0 transport_latency_assumed new_market e 3,103 3,103 167ms 28.3s 1.5min 1.8min 0 transport_latency_assumed new_market h 3,104 833 122ms 25.4s 1.4min 2.2min 0 transport_latency_assumed price_change b 89,030,634 105,704 50ms 94ms 520ms 20.0s 0 transport_latency_assumed price_change c 97,229,054 7,334 3ms 9ms 196ms 10.1s 0 transport_latency_assumed price_change e 97,154,876 97,150,094 39ms 96ms 591ms 28.3s 0 transport_latency_assumed price_change h 97,227,466 81,854 18ms 36ms 449ms 50.5s 0 transport_latency_assumed tick_size_change b 4,240 not meas. 50ms 166ms 577ms 750ms 0 transport_latency_assumed tick_size_change c 4,540 not meas. 3ms 41ms 254ms 375ms 0 transport_latency_assumed tick_size_change e 4,536 4,536 39ms 143ms 439ms 689ms 0 transport_latency_assumed tick_size_change h 4,540 4 18ms 69ms 718ms 1.3s 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/17/2026-09-04T17.parquet sha256sum 2026-09-04T17.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.