Hour audit: 2026-09-22T01
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: g. 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-22T01 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-22T01:00:00.000242709+00:00 · last event 2026-09-22T01:59:59.999991786+00:00
VOLUME 122,879,496 rows · 1,259,168,329 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 122,432,637 · h: 122,099,505 · e: 121,761,571 · f: 117,720,365 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 116,187,250 (94.55%) · h: 5,739,829 (4.67%) · e: 397,632 (0.32%) · f: 554,785 (0.45%) (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 122,879,496 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 9300b6bdb823a3f939b78791cd5f946b34c03893ebe46bd422bcec98f9b3a2ef
the corpus checksum ledger names this file with the same digest
joined 122,881,764 to merged 122,879,496, minus 2,268 (minus 0.0018%)
boundary drops 2,268 · 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-22T02:59:13Z as cefh
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,542,134 129,288,337 0-44 7f4509fc08c14c793d2ff53ab166aaad6ce1bfb0c7a40ddad7c1b0c32d2dfa88 book 521,252 49,086,620 45-46 7b929eb3c37b247211a540551dca19d89c63ca031a92e9e43037cd8eb6492f8a last_trade_price 49,239 2,778,382 47-47 44931bc9817160911f63bd75c10a016a892c47fc837160100eaa2e08a23d00ef market_resolved 800 111,316 48-48 759eb3864d2b952c35c53a7522dc4d6658b6a0ab2720f30e9dd638c8f7f53078 new_market 501 57,686 49-49 8afd910f7dc7c7cbe82419a5b6560c62cc894fd83cef595f8e483af8ec5735b8 price_change 110,762,338 1,076,332,595 50-472 3f3e7c1a0ec3ea1be60db2e657dc6927cadda4ba98cf66972bbb65a9e2a144d4 tick_size_change 3,232 117,014 473-473 23053931ff17fba56ee25c0653d10e85a11ef096911d21e2d95904d3de5b6084 EVENT MIX count share price_change 110,762,338 90.14% best_bid_ask 11,542,134 9.39% book 521,252 0.42% last_trade_price 49,239 0.04% tick_size_change 3,232 <0.01% market_resolved 800 <0.01% new_market 501 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,542,196 11,542,134 62 72,229 PARTIAL book 521,318 521,252 66 176,357 PARTIAL last_trade_price 49,239 49,239 0 2,699 PARTIAL market_resolved 800 800 0 679 PARTIAL new_market 501 501 0 367 PARTIAL price_change 110,764,478 110,762,338 2,140 125,618 PARTIAL tick_size_change 3,232 3,232 0 808 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,541,586 11,013,687 4ms 11ms 78ms 1.5s 0 transport_latency_assumed best_bid_ask e 11,526,611 30,958 41ms 52ms 153ms 5.8s 0 transport_latency_assumed best_bid_ask f 11,086,351 12,705 47ms 58ms 138ms 4.1s 0 transport_latency_assumed best_bid_ask h 11,533,175 484,784 17ms 33ms 93ms 7.2s 0 transport_latency_assumed book c 105,129 96,427 6ms 59ms 9.5h 96.6d 0 book_staleness book e 112,089 13,752 45ms 13.4s 9.8h 96.6d 0 book_staleness book f 479,495 382,335 3.9min 2.5d 40.4d 115.1d 0 book_staleness book h 131,039 28,738 23ms 14.6min 14.6d 115.1d 0 book_staleness last_trade_price c 49,114 45,586 5ms 21ms 165ms 1.1s 0 transport_latency_assumed last_trade_price e 48,467 262 43ms 96ms 1.4s 5.8s 0 transport_latency_assumed last_trade_price f 47,036 185 49ms 100ms 395ms 2.6s 0 transport_latency_assumed last_trade_price h 48,712 3,206 19ms 45ms 169ms 3.5s 0 transport_latency_assumed market_resolved c 679 543 5ms 38.6s 59.9s 1.0min 0 transport_latency_assumed market_resolved e 679 93 44ms 35.3s 53.4s 59.5s 0 transport_latency_assumed market_resolved f 679 87 50ms 47.7s 4.2min 5.7min 0 transport_latency_assumed market_resolved h 679 77 19ms 35.9s 54.0s 59.8s 0 transport_latency_assumed new_market c 367 244 40ms 11.3s 25.6s 1.2min 0 transport_latency_assumed new_market e 367 62 76ms 12.2s 22.4s 1.4min 0 transport_latency_assumed new_market f 370 64 84ms 12.6s 53.6s 4.6min 0 transport_latency_assumed new_market h 367 131 51ms 9.1s 27.3s 1.5min 0 transport_latency_assumed price_change c 110,732,530 105,027,673 5ms 14ms 89ms 1.8s 0 transport_latency_assumed price_change e 110,070,126 352,505 42ms 59ms 279ms 7.3s 0 transport_latency_assumed price_change f 106,103,642 159,401 48ms 63ms 193ms 5.5s 0 transport_latency_assumed price_change h 110,382,301 5,222,759 18ms 37ms 114ms 7.2s 0 transport_latency_assumed tick_size_change c 3,232 3,090 5ms 13ms 54ms 328ms 0 transport_latency_assumed tick_size_change e 3,232 not meas. 41ms 52ms 113ms 194ms 0 transport_latency_assumed tick_size_change f 2,792 8 48ms 59ms 243ms 530ms 0 transport_latency_assumed tick_size_change h 3,232 134 18ms 37ms 78ms 148ms 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-22/01/2026-09-22T01.parquet sha256sum 2026-09-22T01.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.