Hour audit: 2026-09-06T04
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: c. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-06T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-06T04:00:00.069568520+00:00 · last event 2026-09-06T04:59:59.999971331+00:00
VOLUME 106,428,880 rows · 1,059,259,514 bytes (1010.19 MiB) · 7 products, all holding rows
WITNESSES efgh — 4 machines contributed rows
captured f: 106,320,133 · h: 106,294,650 · g: 106,258,180 · e: 106,025,935 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 119,148 (0.11%) · h: 44,892 (0.04%) · g: 106,255,366 (99.84%) · e: 9,474 (0.01%) (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 106,428,880 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: c
INTEGRITY sha256 8c32202c04b94aad8a35db731d4d49d5b4b5416a3662d1ec6fc5fc5771e60196
the corpus checksum ledger names this file with the same digest
joined 106,431,702 to merged 106,428,880, minus 2,822 (minus 0.0027%)
boundary drops 2,822 · 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-06T08:29:05Z as efgh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,207,294 119,500,140 0-42 c67b486b450f35f70e76147d989f2637e7f8d7b95ca38f0388d4b2494c4fc092 book 239,553 24,044,060 43-43 774a09686f4cfffbd04398e23e4a32abf3cfef61c5d5cd72517f8913aefaa945 last_trade_price 44,720 2,645,578 44-44 1cbfa6a8e0964c4514ac52134867a450e2af1dd18578d5d5d601f34855effd31 market_resolved 3,508 575,357 45-45 780b319599e6c41bd47e2379110347a59f7b2f50e5a94f3834138dd17a5336a0 new_market 4,115 433,652 46-46 52c5d10531e0bb1e8a92da1283ead2ad876253c76ba6974de28d59ec900eb713 price_change 94,923,866 910,638,649 47-409 18a74ca8627c3f2b28278226e6cffedbc92a5acfa0a167e2bbde77bcf5327e09 tick_size_change 5,824 210,864 410-410 eb6082774ef692e0154032ee740ab08f4646a61bf350c14e090eae885a4740f3 EVENT MIX count share price_change 94,923,866 89.19% best_bid_ask 11,207,294 10.53% book 239,553 0.23% last_trade_price 44,720 0.04% tick_size_change 5,824 <0.01% new_market 4,115 <0.01% market_resolved 3,508 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,207,486 11,207,294 192 55,673 PARTIAL book 239,571 239,553 18 69,493 PARTIAL last_trade_price 44,720 44,720 0 3,554 PARTIAL market_resolved 3,508 3,508 0 3,499 PARTIAL new_market 4,115 4,115 0 2,931 PARTIAL price_change 94,926,478 94,923,866 2,612 97,222 PARTIAL tick_size_change 5,824 5,824 0 1,456 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 11,198,031 529 38ms 46ms 312ms 11.3s 0 transport_latency_assumed best_bid_ask f 11,204,872 2,972 48ms 57ms 326ms 6.4s 0 transport_latency_assumed best_bid_ask g 11,203,068 11,202,876 81ms 108ms 661ms 35.4s 0 transport_latency_assumed best_bid_ask h 11,205,452 917 18ms 39ms 631ms 1.2min 0 transport_latency_assumed book e 102,899 7,131 41ms 2.2s 9.6h 80.7d 0 book_staleness book f 145,877 44,886 61ms 6.2h 21.1d 99.2d 0 book_staleness book g 149,808 149,794 122ms 6.7h 21.6d 80.8d 0 book_staleness book h 142,689 37,742 36ms 5.7h 14.6d 99.2d 0 book_staleness last_trade_price e 44,133 3 44ms 116ms 2.6s 11.0s 0 transport_latency_assumed last_trade_price f 44,698 216 54ms 133ms 1.7s 6.4s 0 transport_latency_assumed last_trade_price g 44,494 44,494 91ms 255ms 11.4s 35.4s 0 transport_latency_assumed last_trade_price h 44,637 7 23ms 75ms 992ms 1.2min 0 transport_latency_assumed market_resolved e 3,499 9 44ms 123ms 454ms 40.7s 0 transport_latency_assumed market_resolved f 3,499 not meas. 52ms 136ms 433ms 769ms 0 transport_latency_assumed market_resolved g 3,499 3,499 93ms 256ms 714ms 1.5s 0 transport_latency_assumed market_resolved h 3,499 not meas. 28ms 68ms 271ms 7.0s 0 transport_latency_assumed new_market e 2,931 230 210ms 45.5s 1.0min 1.8h 0 transport_latency_assumed new_market f 2,931 752 235ms 46.8s 1.0min 2.0h 0 transport_latency_assumed new_market g 2,931 2,931 375ms 46.4s 59.0s 1.6h 0 transport_latency_assumed new_market h 2,931 202 179ms 46.4s 1.1min 2.0h 0 transport_latency_assumed price_change e 94,668,646 1,572 39ms 53ms 403ms 11.3s 0 transport_latency_assumed price_change f 94,912,432 70,322 48ms 64ms 394ms 6.5s 0 transport_latency_assumed price_change g 94,848,556 94,845,948 82ms 132ms 898ms 35.5s 0 transport_latency_assumed price_change h 94,889,618 6,024 18ms 44ms 681ms 1.2min 0 transport_latency_assumed tick_size_change e 5,796 not meas. 38ms 61ms 251ms 700ms 0 transport_latency_assumed tick_size_change f 5,824 not meas. 48ms 56ms 281ms 710ms 0 transport_latency_assumed tick_size_change g 5,824 5,824 82ms 112ms 623ms 3.6s 0 transport_latency_assumed tick_size_change h 5,824 not meas. 18ms 35ms 297ms 4.9s 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-06/04/2026-09-06T04.parquet sha256sum 2026-09-06T04.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.