Hour audit: 2026-09-04T10
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-04T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T10:00:00.002564665+00:00 · last event 2026-09-04T10:59:59.999990075+00:00
VOLUME 96,921,984 rows · 997,058,806 bytes (950.87 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 95,110,618 · e: 88,568,786 · b: 86,702,565 · h: 86,594,639 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 2,019,892 (2.08%) · e: 88,566,616 (91.38%) · b: 173,053 (0.18%) · h: 6,162,423 (6.36%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,921,984 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 6be69e1c3affe4edaf8acb5319646c7756b8c0c18df8395cf36a063f3e94769c
the corpus checksum ledger names this file with the same digest
joined 96,927,244 to merged 96,921,984, minus 5,260 (minus 0.0054%)
boundary drops 5,260 · 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-04T11:52:00Z 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,056,209 89,574,861 0-30 d0c1d4c147c35a11cd3a7311445f5c3b1bdb383dbfa3a98a7ae9a8e501cf882b book 1,027,428 77,137,726 31-34 d018a77306b66d6408d9b8d0e1d87fc751bea01b4f94d1b9a75f777cd06d9b7a last_trade_price 65,547 3,656,176 35-35 a7614cd36bf02ddf5f3ca851d44ec4aa21ef3d4f31b6bccac8f3e520257269f4 market_resolved 629 103,332 36-36 95e7dd1d2c48b2421740b832a72fbc3e95416daa0b7cf4d995baf04644683b3a new_market 919 100,962 37-37 f06b6c0c23e679a79f71dbbd67a8033576303b71c8d73ff94a20d598768732f3 price_change 87,768,608 825,284,708 38-372 d84100495f5aa958b48288e66de3003a8a3ad356ed426a99d0fc37194cf3e76b tick_size_change 2,644 97,472 373-373 45aae4c2deac2883ef67c0f13df62e915052a139916dca2890c5381953796683 EVENT MIX count share price_change 87,768,608 90.56% best_bid_ask 8,056,209 8.31% book 1,027,428 1.06% last_trade_price 65,547 0.07% tick_size_change 2,644 <0.01% new_market 919 <0.01% market_resolved 629 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,056,337 8,056,209 128 640 FULL book 1,031,498 1,027,428 4,070 133,085 FULL last_trade_price 65,547 65,547 0 58 FULL market_resolved 629 629 0 3 FULL new_market 919 919 0 0 FULL price_change 87,769,670 87,768,608 1,062 33,590 FULL tick_size_change 2,644 2,644 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,053,051 44 48ms 61ms 187ms 10.9s 0 transport_latency_assumed best_bid_ask c 7,959,340 517 3ms 7ms 61ms 5.0s 0 transport_latency_assumed best_bid_ask e 7,957,784 7,957,682 37ms 48ms 237ms 5.0s 0 transport_latency_assumed best_bid_ask h 8,054,146 97,966 18ms 24ms 117ms 10.3s 0 transport_latency_assumed book b 451,713 163,272 1.0min 10.2h 26.9d 97.5d 0 book_staleness book c 470,102 189,917 1.1min 10.3h 27.0d 97.5d 0 book_staleness book e 449,566 448,118 1.0min 9.5h 31.6d 97.5d 0 book_staleness book h 461,630 226,121 1.1min 10.3h 27.0d 97.5d 0 book_staleness last_trade_price b 65,428 5 57ms 173ms 1.4s 10.9s 0 transport_latency_assumed last_trade_price c 65,116 8 8ms 35ms 190ms 5.0s 0 transport_latency_assumed last_trade_price e 65,293 65,293 44ms 167ms 930ms 5.2s 0 transport_latency_assumed last_trade_price h 65,496 241 23ms 77ms 362ms 10.2s 0 transport_latency_assumed market_resolved b 628 not meas. 50ms 238ms 537ms 714ms 0 transport_latency_assumed market_resolved c 625 1 4ms 8ms 38ms 2.3min 0 transport_latency_assumed market_resolved e 628 628 38ms 214ms 518ms 760ms 0 transport_latency_assumed market_resolved h 628 not meas. 18ms 115ms 201ms 1.1s 0 transport_latency_assumed new_market b 667 60 148ms 14.5s 35.9s 56.7s 0 transport_latency_assumed new_market c 667 107 50ms 17.6s 36.3s 1.0min 0 transport_latency_assumed new_market e 667 667 117ms 12.0s 43.1s 1.6min 0 transport_latency_assumed new_market h 667 85 102ms 402ms 53.3s 1.7min 0 transport_latency_assumed price_change b 78,128,434 9,672 48ms 64ms 279ms 10.9s 0 transport_latency_assumed price_change c 86,612,136 1,829,342 4ms 7ms 78ms 5.0s 0 transport_latency_assumed price_change e 80,092,208 80,091,588 37ms 63ms 321ms 5.1s 0 transport_latency_assumed price_change h 78,009,428 5,838,006 18ms 27ms 155ms 13.3s 0 transport_latency_assumed tick_size_change b 2,644 not meas. 49ms 88ms 228ms 296ms 0 transport_latency_assumed tick_size_change c 2,632 not meas. 4ms 7ms 48ms 337ms 0 transport_latency_assumed tick_size_change e 2,640 2,640 37ms 66ms 129ms 176ms 0 transport_latency_assumed tick_size_change h 2,644 4 18ms 32ms 102ms 163ms 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/10/2026-09-04T10.parquet sha256sum 2026-09-04T10.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.