Hour audit: 2026-09-22T00
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-22T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-22T00:00:00.000275149+00:00 · last event 2026-09-22T00:59:59.999913554+00:00
VOLUME 120,402,577 rows · 1,261,673,108 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 118,625,978 · e: 118,238,995 · f: 114,328,844 · c: 101,077,992 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,824,991 (19.79%) · e: 1,043,305 (0.87%) · f: 558,236 (0.46%) · c: 94,976,045 (78.88%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 c9ec32fe4d324605302446999619ffa4d27c850f3797f7e844474f65624ddb54
the corpus checksum ledger names this file with the same digest
joined 120,403,880 to merged 120,402,577, minus 1,303 (minus 0.0011%)
boundary drops 1,303 · 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-22T01:57:01Z 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 10,977,517 124,446,656 0-41 fd5d36e54378d0b272ed8d33af09a1ecf98cf1354570139e3d5f7e67d6dc687f book 1,677,293 78,023,139 42-48 40374559b0911040c4df4887def7b8d1c232c498d20417c6fe68e68e7c444a87 last_trade_price 52,559 2,958,448 49-49 df8941a4e537c754f5e64f5328b787e08c03302c1126ed02796f9d911bf7c4c5 market_resolved 1,099 153,964 50-50 c5e677ed9a0cb7a3b1e3c7cf37f37b1136642af46435589c68d0b21d4621f64f new_market 1,355 146,514 51-51 fa09d8c84ef92293fdc21a1a69043f71b8d8381d669b6e10c3c53849789157cb price_change 107,690,610 1,054,496,748 52-462 77933e761379f4da61a425279370765592b47dee6c644a19ce4511c8adc97b80 tick_size_change 2,144 79,753 463-463 51291ad8b99f492fafa4024ee14445bb871ebc31e462be2cf916453139f725dd EVENT MIX count share price_change 107,690,610 89.44% best_bid_ask 10,977,517 9.12% book 1,677,293 1.39% last_trade_price 52,559 0.04% tick_size_change 2,144 <0.01% new_market 1,355 <0.01% market_resolved 1,099 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,977,617 10,977,517 100 74,158 PARTIAL book 1,677,449 1,677,293 156 178,101 PARTIAL last_trade_price 52,560 52,559 1 3,011 PARTIAL market_resolved 1,099 1,099 0 949 PARTIAL new_market 1,355 1,355 0 961 PARTIAL price_change 107,691,656 107,690,610 1,046 126,131 PARTIAL tick_size_change 2,144 2,144 0 536 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,199,571 8,675,021 5ms 15ms 99ms 3.1s 0 transport_latency_assumed best_bid_ask e 10,970,167 89,123 42ms 57ms 186ms 10.6s 0 transport_latency_assumed best_bid_ask f 10,585,554 29,585 48ms 63ms 179ms 14.2s 0 transport_latency_assumed best_bid_ask h 10,974,510 2,183,788 18ms 31ms 116ms 6.3s 0 transport_latency_assumed book c 1,527,042 1,499,911 11.1min 3.3d 43.6d 115.1d 0 book_staleness book e 128,241 12,440 46ms 6.4min 14.6d 96.6d 0 book_staleness book f 462,753 134,265 3.8min 2.3d 40.2d 115.1d 0 book_staleness book h 125,221 30,677 22ms 2.7min 12.7d 115.1d 0 book_staleness last_trade_price c 44,179 40,547 6ms 27ms 159ms 1.2s 0 transport_latency_assumed last_trade_price e 51,959 500 44ms 165ms 2.3s 10.6s 0 transport_latency_assumed last_trade_price f 50,028 384 50ms 132ms 953ms 4.6s 0 transport_latency_assumed last_trade_price h 52,300 11,128 19ms 51ms 224ms 3.8s 0 transport_latency_assumed market_resolved c 887 761 6ms 4.3min 10.0min 10.0min 0 transport_latency_assumed market_resolved e 949 95 43ms 543ms 44.6s 52.6s 0 transport_latency_assumed market_resolved f 947 8 50ms 9.7s 55.8s 5.4min 0 transport_latency_assumed market_resolved h 949 235 18ms 171ms 45.1s 53.0s 0 transport_latency_assumed new_market c 999 663 68ms 1.1min 4.7min 6.0min 0 transport_latency_assumed new_market e 961 141 126ms 36.0s 1.6min 2.5min 0 transport_latency_assumed new_market f 964 142 122ms 23.5s 2.5min 5.1min 0 transport_latency_assumed new_market h 961 409 74ms 35.7s 1.8min 2.8min 0 transport_latency_assumed price_change c 90,303,502 84,757,482 5ms 18ms 109ms 3.1s 0 transport_latency_assumed price_change e 107,084,574 940,990 42ms 67ms 343ms 10.6s 0 transport_latency_assumed price_change f 103,226,522 393,848 48ms 71ms 273ms 16.4s 0 transport_latency_assumed price_change h 107,469,893 21,598,290 18ms 35ms 144ms 6.8s 0 transport_latency_assumed tick_size_change c 1,812 1,660 5ms 19ms 144ms 311ms 0 transport_latency_assumed tick_size_change e 2,144 16 42ms 59ms 164ms 567ms 0 transport_latency_assumed tick_size_change f 2,076 4 48ms 59ms 179ms 221ms 0 transport_latency_assumed tick_size_change h 2,144 464 18ms 31ms 99ms 185ms 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/00/2026-09-22T00.parquet sha256sum 2026-09-22T00.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.