Hour audit: 2026-09-04T12
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-04T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T12:00:00.020296171+00:00 · last event 2026-09-04T12:59:59.999999285+00:00
VOLUME 103,352,488 rows · 1,033,075,449 bytes (985.22 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured b: 103,171,818 · h: 103,064,728 · e: 102,416,365 · c: 102,211,185 (each machine's own feed; these overlap and do not sum to the file)
supplied b: 10,822 (0.01%) · h: 836,511 (0.81%) · e: 102,415,329 (99.09%) · c: 89,826 (0.09%) (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 103,352,488 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 f9763fbc8d0e72ff7f64999f7a3d5b4e7e8cd8c537e0d09619935c952febf01d
the corpus checksum ledger names this file with the same digest
joined 103,353,952 to merged 103,352,488, minus 1,464 (minus 0.0014%)
boundary drops 1,464 · 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-04T13:54:58Z 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,947,982 99,451,040 0-34 e5f73bc4f997db4085452bddaf975090e3dffa5cfa84e86d3a885fb1e383a76b book 322,399 32,514,928 35-36 bec95e6e72988c113dbf415e29054699276c963c112ebd7d3ab2e910fd902926 last_trade_price 81,548 4,516,493 37-37 a8802eb50c830636088c0b82ec0a0a1e04e70bc42f7f7907256a8ac3025c8799 market_resolved 623 102,748 38-38 0373326901646b97fe48129647148ae52a520c5da86ad04b21b3035d666015c7 new_market 1,058 118,595 39-39 2208e86690e4d295a78e587cdf01a0c2db4dcf99a5dc2cc1c4244f42d87193ec price_change 93,996,142 895,092,606 40-398 d103c4967e8b56f73a8f2803994a56e2598edc8012f27d2f3e7c0f9ce57888e9 tick_size_change 2,736 99,122 399-399 dc8ad49eb248c84b9e91059c6268945fb8f655af40da8c4c7be0c7bc71269d1b EVENT MIX count share price_change 93,996,142 90.95% best_bid_ask 8,947,982 8.66% book 322,399 0.31% last_trade_price 81,548 0.08% tick_size_change 2,736 <0.01% new_market 1,058 <0.01% market_resolved 623 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,948,084 8,947,982 102 1,560 FULL book 322,731 322,399 332 67,113 FULL last_trade_price 81,548 81,548 0 89 FULL market_resolved 623 623 0 16 FULL new_market 1,058 1,058 0 0 FULL price_change 93,997,172 93,996,142 1,030 2,459 FULL tick_size_change 2,736 2,736 0 13 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,946,000 10 49ms 63ms 218ms 17.6s 0 transport_latency_assumed best_bid_ask c 8,842,043 662 4ms 7ms 68ms 2.0s 0 transport_latency_assumed best_bid_ask e 8,886,538 8,886,452 39ms 52ms 273ms 15.3s 0 transport_latency_assumed best_bid_ask h 8,946,689 60,858 18ms 27ms 137ms 16.3s 0 transport_latency_assumed book b 181,282 10,270 53ms 406ms 9.3h 97.6d 0 book_staleness book c 252,523 79,452 8ms 1.5h 15.7d 97.6d 0 book_staleness book e 185,314 185,216 43ms 2.6s 12.4h 97.6d 0 book_staleness book h 216,291 47,461 25ms 6.7min 12.5d 97.6d 0 book_staleness last_trade_price b 81,497 10 59ms 162ms 3.8s 17.7s 0 transport_latency_assumed last_trade_price c 80,776 16 9ms 37ms 205ms 5.0s 0 transport_latency_assumed last_trade_price e 81,024 81,024 48ms 197ms 3.1s 15.3s 0 transport_latency_assumed last_trade_price h 81,425 498 24ms 72ms 394ms 5.8s 0 transport_latency_assumed market_resolved b 616 not meas. 51ms 490ms 54.8s 55.9s 0 transport_latency_assumed market_resolved c 616 3 4ms 60ms 54.2s 2.0min 0 transport_latency_assumed market_resolved e 600 600 41ms 445ms 55.8s 1.9min 0 transport_latency_assumed market_resolved h 616 20 19ms 196ms 54.9s 56.0s 0 transport_latency_assumed new_market b 781 40 155ms 14.9s 30.3s 59.3s 0 transport_latency_assumed new_market c 781 61 48ms 11.4s 27.7s 1.2min 0 transport_latency_assumed new_market e 781 781 139ms 15.4s 30.2s 1.2min 0 transport_latency_assumed new_market h 781 176 112ms 16.0s 1.1min 1.1min 0 transport_latency_assumed price_change b 93,958,906 492 49ms 70ms 298ms 17.7s 0 transport_latency_assumed price_change c 93,031,734 9,632 4ms 8ms 77ms 3.4s 0 transport_latency_assumed price_change e 93,259,400 93,258,548 39ms 68ms 396ms 15.3s 0 transport_latency_assumed price_change h 93,816,190 727,470 18ms 30ms 162ms 16.6s 0 transport_latency_assumed tick_size_change b 2,736 not meas. 49ms 62ms 133ms 150ms 0 transport_latency_assumed tick_size_change c 2,712 not meas. 4ms 6ms 29ms 88ms 0 transport_latency_assumed tick_size_change e 2,708 2,708 39ms 51ms 172ms 245ms 0 transport_latency_assumed tick_size_change h 2,736 28 18ms 24ms 72ms 140ms 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/12/2026-09-04T12.parquet sha256sum 2026-09-04T12.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.