Hour audit: 2026-08-30T07
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: b. 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-08-30T07 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T07:00:00.037347430+00:00 · last event 2026-08-30T07:59:59.999973507+00:00
VOLUME 86,020,520 rows · 824,467,992 bytes (786.27 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 85,967,800 · a: 85,958,953 · h: 85,861,620 · e: 85,853,987 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 27,674 (0.03%) · a: 18,380 (0.02%) · h: 122,283 (0.14%) · e: 85,852,183 (99.80%) (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 86,020,520 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 fe4782c81e3652dd563466a39d5852e62e97a234413de6af9653e65f19c804ea
the corpus checksum ledger names this file with the same digest
joined 86,022,332 to merged 86,020,520, minus 1,812 (minus 0.0021%)
boundary drops 1,812 · 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-08-31T14:10:58Z as aceh
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 8,140,565 88,960,836 0-31 9f1297a9a87c575e03be4d3fd7b16bf22784e924bbb822c44b0ff862d9ce54ef book 154,615 15,459,102 32-32 ca136d5c1010c858c4349970f67fa4be04b3caeb836a4b9af3a17a4a67959189 last_trade_price 45,695 2,610,062 33-33 fc9c956b03a3d3ca4274aa58c68bc694075b626dea91dfbffa6d8edeefc155d6 market_resolved 575 95,028 34-34 3f48b46b72c9f0141adb9c453a063cb875bc7d3fe1f30391895a7e0f3d223d8b new_market 1,056 109,782 35-35 0bfa12dcf2575a65ace9bf5051bc7b029e8104c1e8ef1f521b5cac5ff7ce2c82 price_change 77,676,338 716,187,402 36-332 34671f225885ae6e8109c70253b0c789ed6db0545f744bcaab965a8dcfcef797 tick_size_change 1,676 61,035 333-333 0b4ce951328e5dd6ae03fad6162933038da569d4373ba34d33eeed1d9bc8db6c EVENT MIX count share price_change 77,676,338 90.30% best_bid_ask 8,140,565 9.46% book 154,615 0.18% last_trade_price 45,695 0.05% tick_size_change 1,676 <0.01% new_market 1,056 <0.01% market_resolved 575 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,140,659 8,140,565 94 64,048 PARTIAL book 154,615 154,615 0 30,531 PARTIAL last_trade_price 45,695 45,695 0 3,267 PARTIAL market_resolved 575 575 0 571 PARTIAL new_market 1,056 1,056 0 725 PARTIAL price_change 77,678,056 77,676,338 1,718 121,840 PARTIAL tick_size_change 1,676 1,676 0 419 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,138,552 119 36ms 42ms 209ms 7.8s 0 transport_latency_assumed best_bid_ask c 8,140,096 508 3ms 6ms 45ms 3.2s 0 transport_latency_assumed best_bid_ask e 8,138,817 8,138,723 43ms 67ms 462ms 11.7s 0 transport_latency_assumed best_bid_ask h 8,133,992 1,215 11ms 14ms 120ms 8.0s 0 transport_latency_assumed book a 112,423 17,006 64ms 1.4min 7.7d 73.9d 0 book_staleness book c 112,318 17,487 6ms 1.3min 7.7d 92.4d 0 book_staleness book e 112,646 112,646 89ms 1.3min 7.7d 73.9d 0 book_staleness book h 99,742 7,476 17ms 799ms 1.6h 73.8d 0 book_staleness last_trade_price a 45,626 5 47ms 641ms 5.8s 7.8s 0 transport_latency_assumed last_trade_price c 45,676 7 8ms 35ms 187ms 5.0s 0 transport_latency_assumed last_trade_price e 45,668 45,668 61ms 1.9s 7.6s 11.7s 0 transport_latency_assumed last_trade_price h 44,800 15 17ms 147ms 1.6s 6.6s 0 transport_latency_assumed market_resolved a 571 4 37ms 233ms 407ms 494ms 0 transport_latency_assumed market_resolved c 571 not meas. 3ms 6ms 45ms 1.0min 0 transport_latency_assumed market_resolved e 571 571 43ms 242ms 2.9s 1.0min 0 transport_latency_assumed market_resolved h 571 not meas. 11ms 27ms 706ms 58.4s 0 transport_latency_assumed new_market a 725 108 220ms 15.1s 25.8s 30.2s 0 transport_latency_assumed new_market c 725 108 85ms 17.2s 23.7s 56.1s 0 transport_latency_assumed new_market e 725 725 228ms 16.8s 24.7s 27.3s 0 transport_latency_assumed new_market h 725 115 108ms 17.8s 24.6s 1.1min 0 transport_latency_assumed price_change a 77,659,380 1,138 37ms 45ms 401ms 7.8s 0 transport_latency_assumed price_change c 77,666,738 9,564 4ms 6ms 53ms 3.2s 0 transport_latency_assumed price_change e 77,553,884 77,552,174 43ms 88ms 1.0s 11.7s 0 transport_latency_assumed price_change h 77,580,114 113,462 11ms 15ms 178ms 8.0s 0 transport_latency_assumed tick_size_change a 1,676 not meas. 37ms 42ms 108ms 289ms 0 transport_latency_assumed tick_size_change c 1,676 not meas. 4ms 5ms 16ms 218ms 0 transport_latency_assumed tick_size_change e 1,676 1,676 43ms 77ms 167ms 499ms 0 transport_latency_assumed tick_size_change h 1,676 not meas. 11ms 14ms 31ms 55ms 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-08-30/07/2026-08-30T07.parquet sha256sum 2026-08-30T07.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.