Hour audit: 2026-09-11T22
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-11T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-11T22:00:00.001941948+00:00 · last event 2026-09-11T22:59:59.999963438+00:00
VOLUME 110,772,299 rows · 1,152,180,181 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured e: 108,567,374 · h: 108,392,445 · g: 108,234,772 · c: 86,338,492 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,888,887 (1.71%) · h: 26,813,449 (24.21%) · g: 113,741 (0.10%) · c: 81,956,222 (73.99%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 6da9ff82ca04824de6bb0f2fb9054aa3657b5288796129cce4c6b473f9b1b6b6
the corpus checksum ledger names this file with the same digest
joined 110,777,981 to merged 110,772,299, minus 5,682 (minus 0.0051%)
boundary drops 5,682 · 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-12T02:35:05Z 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 10,166,518 113,072,717 0-38 2ef9de471ae804ca25d05d636a4ac76ca600c99a10ae42922949a5eb524474bf book 2,356,446 101,564,231 39-47 166a0cb9b76fb3c5fbc357d5532fed0979d5422bbc52aac59c36d9ce0a8454fb last_trade_price 57,246 3,155,395 48-48 4bd1468c6bda0a4c8c63e8a0c095adad67823868e05e5e4e0c11b3269b756889 market_resolved 3,571 388,189 49-49 38338ca706b71245d5d0445312b1640d96b5cfdff9bfb71946f5aba92c78af8f new_market 3,690 273,120 50-50 6d623a64ecd82f355833bb764a6624e711423215f98ca5ab918b19489301a2a2 price_change 98,182,916 932,397,482 51-425 1b3b110fac7d1e5a4985069cfe5154bc90f8f40b308f0796eae42bd4de988ae8 tick_size_change 1,912 70,565 426-426 2b648a929abc86a40433b5d09199415bc9dae36a6e14abd394deb832c8b752ae EVENT MIX count share price_change 98,182,916 88.63% best_bid_ask 10,166,518 9.18% book 2,356,446 2.13% last_trade_price 57,246 0.05% new_market 3,690 <0.01% market_resolved 3,571 <0.01% tick_size_change 1,912 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,166,744 10,166,518 226 71,796 PARTIAL book 2,358,216 2,356,446 1,770 215,922 PARTIAL last_trade_price 57,249 57,246 3 2,870 PARTIAL market_resolved 3,572 3,571 1 2,309 PARTIAL new_market 3,690 3,690 0 1,656 PARTIAL price_change 98,186,598 98,182,916 3,682 124,832 PARTIAL tick_size_change 1,912 1,912 0 478 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,925,025 7,527,036 5ms 12ms 232ms 13.1s 0 transport_latency_assumed best_bid_ask e 10,163,204 166,245 39ms 49ms 318ms 21.5s 0 transport_latency_assumed best_bid_ask g 10,156,358 8,513 83ms 116ms 804ms 49.9s 0 transport_latency_assumed best_bid_ask h 10,155,331 2,464,724 17ms 26ms 409ms 1.5min 0 transport_latency_assumed book c 2,263,907 2,228,151 15.4min 5.1h 31.1d 105.0d 0 book_staleness book e 238,420 51,936 1.8s 3.6h 20.3d 105.0d 0 book_staleness book g 145,342 12,259 97ms 9.1min 3.1d 105.0d 0 book_staleness book h 208,242 64,100 56ms 2.4h 12.3d 105.0d 0 book_staleness last_trade_price c 46,835 44,094 10ms 53ms 521ms 5.0s 0 transport_latency_assumed last_trade_price e 56,977 1,023 50ms 403ms 4.1s 21.4s 0 transport_latency_assumed last_trade_price g 55,791 151 100ms 959ms 13.3s 49.8s 0 transport_latency_assumed last_trade_price h 56,115 11,978 23ms 90ms 761ms 39.0s 0 transport_latency_assumed market_resolved c 3,062 2,910 8ms 12.0min 17.4min 17.7min 0 transport_latency_assumed market_resolved e 2,308 90 42ms 195ms 588ms 59.8s 0 transport_latency_assumed market_resolved g 2,309 5 94ms 377ms 1.1s 2.2min 0 transport_latency_assumed market_resolved h 2,305 566 19ms 85ms 57.1s 1.1min 0 transport_latency_assumed new_market c 2,818 2,124 3.3min 12.2min 13.4min 20.2min 0 transport_latency_assumed new_market e 1,656 484 237ms 21.4s 51.1s 19.1min 0 transport_latency_assumed new_market g 1,656 245 416ms 22.7s 52.7s 12.2min 0 transport_latency_assumed new_market h 1,656 837 167ms 21.9s 54.3s 6.0min 0 transport_latency_assumed price_change c 76,095,617 72,150,751 5ms 13ms 248ms 15.4s 0 transport_latency_assumed price_change e 98,102,897 1,669,034 40ms 58ms 525ms 21.6s 0 transport_latency_assumed price_change g 97,871,404 92,564 83ms 145ms 1.4s 50.2s 0 transport_latency_assumed price_change h 97,966,884 24,270,567 18ms 31ms 437ms 1.5min 0 transport_latency_assumed tick_size_change c 1,228 1,156 5ms 13ms 169ms 217ms 0 transport_latency_assumed tick_size_change e 1,912 75 40ms 533ms 697ms 776ms 0 transport_latency_assumed tick_size_change g 1,912 4 88ms 955ms 1.7s 3.7s 0 transport_latency_assumed tick_size_change h 1,912 677 18ms 190ms 799ms 10.0s 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-11/22/2026-09-11T22.parquet sha256sum 2026-09-11T22.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.