Hour audit: 2026-09-03T06
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-03T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T06:00:00.035120049+00:00 · last event 2026-09-03T06:59:59.999975426+00:00
VOLUME 93,499,394 rows · 999,386,158 bytes (953.09 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured e: 91,141,421 · b: 90,206,487 · h: 89,004,574 · c: 82,923,273 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 91,137,187 (97.47%) · b: 106,915 (0.11%) · h: 1,639,992 (1.75%) · c: 615,300 (0.66%) (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 93,499,394 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 90a1c8f02332b9135403c6023fe29c8807ecc4453d972a56cb4178c251ee95b3
the corpus checksum ledger names this file with the same digest
joined 93,508,494 to merged 93,499,394, minus 9,100 (minus 0.0097%)
boundary drops 9,100 · 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-03T07:51:33Z 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 7,744,115 93,182,268 0-29 4bc1667e6094e1ca7a4f628c0107841ff397192334fa766b051dd72d1ad054c6 book 1,804,638 102,109,357 30-36 25e4d16415d2dc0331ab27f9625233893539fa07237f64746c68cbb7e4699203 last_trade_price 59,083 3,303,869 37-37 09b9fd7c2753a94d929f592c8a1db74c04e3d5a0f684464ca2b53559b63a52a5 market_resolved 884 127,727 38-38 bbb04d1f347e84d0551b98029bad92de043de6f8e04897e5192e3ecbd901b99c new_market 1,338 128,963 39-39 416ea284dce1441ede91cc517c9b5a24f5dd4c7d19ebfe8f218299657935e194 price_change 83,887,468 799,396,804 40-360 2708c739a9f2dc1336ab8f59b085252a0aa01b31daf076f4fc773870c8c0dacb tick_size_change 1,868 69,618 361-361 079f8e2c4893d66a9d7029731ce4fac46e40fde5257c6173a430f5226df1baea EVENT MIX count share price_change 83,887,468 89.72% best_bid_ask 7,744,115 8.28% book 1,804,638 1.93% last_trade_price 59,083 0.06% tick_size_change 1,868 <0.01% new_market 1,338 <0.01% market_resolved 884 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,744,241 7,744,115 126 2,885 FULL book 1,812,348 1,804,638 7,710 74,729 FULL last_trade_price 59,083 59,083 0 257 FULL market_resolved 884 884 0 14 FULL new_market 1,338 1,338 0 0 FULL price_change 83,888,732 83,887,468 1,264 1,945 FULL tick_size_change 1,868 1,868 0 77 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 7,614,228 54 55ms 93ms 1.0s 24.7s 0 transport_latency_assumed best_bid_ask c 6,810,717 1,377 3ms 7ms 129ms 6.8s 0 transport_latency_assumed best_bid_ask e 7,668,776 7,668,692 42ms 122ms 5.0s 42.5s 0 transport_latency_assumed best_bid_ask h 7,489,927 73,992 18ms 26ms 262ms 9.2s 0 transport_latency_assumed book b 375,027 106,685 57.5s 9.3h 25.7d 96.3d 0 book_staleness book c 1,088,128 596,712 2.9min 11.1h 31.8d 96.4d 0 book_staleness book e 755,615 752,417 2.5min 10.2h 31.8d 96.3d 0 book_staleness book h 792,131 348,824 2.5min 10.4h 31.5d 96.4d 0 book_staleness last_trade_price b 54,811 8 147ms 6.8s 17.0s 24.7s 0 transport_latency_assumed last_trade_price c 53,644 74 9ms 44ms 222ms 4.6s 0 transport_latency_assumed last_trade_price e 52,886 52,886 154ms 7.7s 18.0s 42.5s 0 transport_latency_assumed last_trade_price h 56,258 6,115 35ms 668ms 2.4s 8.9s 0 transport_latency_assumed market_resolved b 765 6 56ms 428ms 781ms 1.4min 0 transport_latency_assumed market_resolved c 781 88 4ms 4.0min 8.7min 9.5min 0 transport_latency_assumed market_resolved e 768 768 43ms 338ms 1.5s 59.9s 0 transport_latency_assumed market_resolved h 772 22 18ms 133ms 3.6min 4.2min 0 transport_latency_assumed new_market b 842 82 248ms 20.9s 41.6s 1.2min 0 transport_latency_assumed new_market c 842 159 48ms 4.0min 4.4min 4.4min 0 transport_latency_assumed new_market e 842 842 164ms 21.3s 39.5s 1.0min 0 transport_latency_assumed new_market h 846 255 102ms 16.4s 4.0min 4.0min 0 transport_latency_assumed price_change b 82,158,978 80 55ms 138ms 5.7s 24.8s 0 transport_latency_assumed price_change c 74,967,545 16,890 3ms 8ms 208ms 6.8s 0 transport_latency_assumed price_change e 82,660,666 82,659,714 42ms 174ms 7.6s 42.5s 0 transport_latency_assumed price_change h 80,662,804 1,210,784 18ms 34ms 592ms 9.5s 0 transport_latency_assumed tick_size_change b 1,836 not meas. 55ms 67ms 182ms 306ms 0 transport_latency_assumed tick_size_change c 1,616 not meas. 4ms 7ms 25ms 93ms 0 transport_latency_assumed tick_size_change e 1,868 1,868 42ms 120ms 4.4s 21.8s 0 transport_latency_assumed tick_size_change h 1,836 not meas. 18ms 23ms 79ms 324ms 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-03/06/2026-09-03T06.parquet sha256sum 2026-09-03T06.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.