Hour audit: 2026-09-20T02
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-20T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T02:00:00.000764923+00:00 · last event 2026-09-20T02:59:59.999954010+00:00
VOLUME 127,452,439 rows · 1,354,583,887 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 126,721,379 · e: 126,653,195 · c: 122,226,955 · g: 121,729,379 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,768,013 (8.45%) · e: 535,476 (0.42%) · c: 115,687,888 (90.77%) · g: 461,062 (0.36%) (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 127,452,439 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 1613b093d249d40c9ccf2f566856248b48cd102b200b6729d8550dca1c79f6d0
the corpus checksum ledger names this file with the same digest
joined 127,465,692 to merged 127,452,439, minus 13,253 (minus 0.0104%)
boundary drops 13,253 · 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-20T07:59:38Z 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,814,540 175,357,485 0-60 15e6e6faf481502ead1774714333054e9eeadf470b8741572a5d4534141b7111 book 854,953 63,433,864 61-64 56e0c6c95cbe49ea4095264d339e989cf09d630505914b0ad7449106651fab08 last_trade_price 59,486 3,416,356 65-65 4d88108d1798c34b01666687e4cf5e5a9b524eb5cef9c6384d2d33dc26364aeb market_resolved 4,822 702,020 66-66 407e089f0bc0455fa927aa37fea6f1c68db7a844899258e843ad78da44e9bba9 new_market 1,062 111,782 67-67 b41d8212b72e37a6c6c32cc11807b035e85a6dad65d0ec9e1f5f7da4c09659fb price_change 110,707,484 1,109,749,716 68-490 290d267fbccbcf40f98f4f2cdfba995ca4c6e14ba26b09fc5dec78580cc8ef20 tick_size_change 10,092 364,144 491-491 20da88a8dd4065306d4214251a07990f167bc0df8ed6a52d994ed29ca91df1da EVENT MIX count share price_change 110,707,484 86.86% best_bid_ask 15,814,540 12.41% book 854,953 0.67% last_trade_price 59,486 0.05% tick_size_change 10,092 <0.01% market_resolved 4,822 <0.01% new_market 1,062 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,814,995 15,814,540 455 83,983 PARTIAL book 863,365 854,953 8,412 184,502 PARTIAL last_trade_price 59,486 59,486 0 4,119 PARTIAL market_resolved 4,822 4,822 0 4,376 PARTIAL new_market 1,062 1,062 0 712 PARTIAL price_change 110,711,870 110,707,484 4,386 143,902 PARTIAL tick_size_change 10,092 10,092 0 2,519 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 15,191,306 14,449,178 5ms 11ms 94ms 7.9s 0 transport_latency_assumed best_bid_ask e 15,812,070 60,015 41ms 48ms 145ms 10.7s 0 transport_latency_assumed best_bid_ask g 15,146,997 2,705 79ms 95ms 286ms 15.1s 0 transport_latency_assumed best_bid_ask h 15,812,727 1,302,642 17ms 26ms 111ms 30.9s 0 transport_latency_assumed book c 577,056 383,461 3.4min 1.3d 38.3d 113.2d 0 book_staleness book e 137,101 10,692 44ms 50.0s 8.4d 94.7d 0 book_staleness book g 578,661 437,889 2.8min 1.3d 38.3d 113.2d 0 book_staleness book h 146,812 22,911 21ms 7.0min 12.6d 113.2d 0 book_staleness last_trade_price c 57,358 53,291 6ms 21ms 219ms 2.4s 0 transport_latency_assumed last_trade_price e 59,025 376 43ms 97ms 2.3s 10.7s 0 transport_latency_assumed last_trade_price g 56,308 11 82ms 197ms 2.8s 15.1s 0 transport_latency_assumed last_trade_price h 59,389 5,808 18ms 46ms 480ms 9.6s 0 transport_latency_assumed market_resolved c 4,393 4,261 5ms 23ms 5.6min 8.4min 0 transport_latency_assumed market_resolved e 4,367 20 44ms 122ms 274ms 1.0min 0 transport_latency_assumed market_resolved g 4,286 186 88ms 243ms 4.7min 5.2min 0 transport_latency_assumed market_resolved h 4,367 355 26ms 57ms 117ms 41.1s 0 transport_latency_assumed new_market c 714 525 69ms 22.4s 49.5min 5.7h 0 transport_latency_assumed new_market e 710 163 163ms 28.3s 50.1s 5.8h 0 transport_latency_assumed new_market g 713 57 257ms 29.1s 54.3s 1.6h 0 transport_latency_assumed new_market h 710 317 115ms 26.6s 42.5s 58.9s 0 transport_latency_assumed price_change c 106,386,284 100,788,062 5ms 13ms 106ms 7.9s 0 transport_latency_assumed price_change e 110,629,830 464,178 41ms 52ms 196ms 10.7s 0 transport_latency_assumed price_change g 105,933,314 20,214 79ms 100ms 387ms 15.2s 0 transport_latency_assumed price_change h 110,687,282 9,435,030 18ms 29ms 130ms 31.8s 0 transport_latency_assumed tick_size_change c 9,844 9,110 5ms 14ms 129ms 249ms 0 transport_latency_assumed tick_size_change e 10,092 32 41ms 46ms 121ms 295ms 0 transport_latency_assumed tick_size_change g 9,100 not meas. 79ms 93ms 232ms 1.9s 0 transport_latency_assumed tick_size_change h 10,092 950 18ms 24ms 82ms 1.1s 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/02/2026-09-20T02.parquet sha256sum 2026-09-20T02.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.