Hour audit: 2026-09-20T05
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: f. 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-20T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T05:00:00.000063270+00:00 · last event 2026-09-20T05:59:59.999456415+00:00
VOLUME 123,667,988 rows · 1,286,642,027 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 123,137,672 · e: 123,126,211 · c: 118,820,990 · g: 118,748,882 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,515,474 (7.69%) · e: 722,347 (0.58%) · c: 113,034,897 (91.40%) · g: 395,270 (0.32%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 123,667,988 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 ab9d500d1e48485c6682f5d4435b9bd088a958face4a2f476b61d8eb90577fb0
the corpus checksum ledger names this file with the same digest
joined 123,670,635 to merged 123,667,988, minus 2,647 (minus 0.0021%)
boundary drops 2,647 · 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-20T09:13:45Z as cegh
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 15,273,332 166,420,292 0-58 027e5abdec3d756dbabc59bc5c14059d6f1ed6ee40f2a5f3dcb11b62f8176fd4 book 571,306 53,925,211 59-61 f12116c62ff36d6535d8ae31dd69cb42e6d7e83f3fa50b6e2c0fd549cd226d63 last_trade_price 50,447 2,888,218 62-62 951894800bd7e612d83533551355d4320fa73b8c5253cac1e9e46746777beded market_resolved 2,117 330,577 63-63 f0ca8a1b6be6b7ad060fe6e8519bb54ec03916e0f5416955dcd82c48ccb28c1c new_market 1,218 125,684 64-64 bc958ef8f1c3ca1f9dcda7aa0f461e3748eef465735b538090285cfc602cf01e price_change 107,765,520 1,061,398,524 65-476 1a6746059e7a57c31872529f8e4efd3326cad068ddeeaf23b0393e1315b70da3 tick_size_change 4,048 146,707 477-477 9162abc6158ad0e033375e2048af28c52d9fe0b5c665f3289d32045611fcf8e3 EVENT MIX count share price_change 107,765,520 87.14% best_bid_ask 15,273,332 12.35% book 571,306 0.46% last_trade_price 50,447 0.04% tick_size_change 4,048 <0.01% market_resolved 2,117 <0.01% new_market 1,218 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,273,637 15,273,332 305 78,338 PARTIAL book 571,354 571,306 48 177,280 PARTIAL last_trade_price 50,447 50,447 0 3,661 PARTIAL market_resolved 2,117 2,117 0 2,079 PARTIAL new_market 1,218 1,218 0 808 PARTIAL price_change 107,767,814 107,765,520 2,294 139,379 PARTIAL tick_size_change 4,048 4,048 0 1,012 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 14,666,820 14,054,613 4ms 10ms 91ms 2.6s 0 transport_latency_assumed best_bid_ask e 15,271,626 79,876 43ms 50ms 153ms 7.9s 0 transport_latency_assumed best_bid_ask g 14,675,674 2,943 76ms 92ms 289ms 19.4s 0 transport_latency_assumed best_bid_ask h 15,272,466 1,135,900 18ms 27ms 114ms 48.8s 0 transport_latency_assumed book c 501,544 173,728 3.6min 1.6d 39.2d 113.3d 0 book_staleness book e 117,971 12,646 46ms 56.8s 10.9d 94.8d 0 book_staleness book g 464,320 364,466 3.3min 1.5d 38.6d 113.3d 0 book_staleness book h 116,848 20,466 21ms 35.0s 8.5d 94.8d 0 book_staleness last_trade_price c 47,957 44,893 5ms 21ms 200ms 2.5s 0 transport_latency_assumed last_trade_price e 50,166 632 45ms 100ms 956ms 8.0s 0 transport_latency_assumed last_trade_price g 47,842 36 80ms 187ms 2.1s 19.4s 0 transport_latency_assumed last_trade_price h 50,267 4,886 19ms 45ms 276ms 12.0s 0 transport_latency_assumed market_resolved c 2,038 1,964 4ms 10ms 223ms 2.2min 0 transport_latency_assumed market_resolved e 2,079 39 46ms 135ms 42.3s 1.0min 0 transport_latency_assumed market_resolved g 2,040 16 81ms 225ms 575ms 2.5min 0 transport_latency_assumed market_resolved h 2,079 98 22ms 60ms 42.6s 1.0min 0 transport_latency_assumed new_market c 806 580 74ms 30.9s 47.2s 4.6h 0 transport_latency_assumed new_market e 808 178 165ms 31.0s 1.4min 4.0h 0 transport_latency_assumed new_market g 808 91 259ms 30.7s 53.5s 3.9h 0 transport_latency_assumed new_market h 808 369 105ms 33.7s 51.4s 5.9h 0 transport_latency_assumed price_change c 103,597,857 98,755,293 5ms 13ms 108ms 3.4s 0 transport_latency_assumed price_change e 107,679,513 628,956 43ms 56ms 219ms 8.0s 0 transport_latency_assumed price_change g 103,554,210 27,718 76ms 99ms 407ms 19.5s 0 transport_latency_assumed price_change h 107,691,156 8,353,553 18ms 31ms 138ms 54.7s 0 transport_latency_assumed tick_size_change c 3,968 3,826 5ms 10ms 160ms 319ms 0 transport_latency_assumed tick_size_change e 4,048 20 43ms 48ms 231ms 466ms 0 transport_latency_assumed tick_size_change g 3,988 not meas. 76ms 92ms 608ms 2.1s 0 transport_latency_assumed tick_size_change h 4,048 202 18ms 32ms 356ms 6.4s 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-20/05/2026-09-20T05.parquet sha256sum 2026-09-20T05.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.