Hour audit: 2026-09-11T23
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-11T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-11T23:00:00.000229494+00:00 · last event 2026-09-11T23:59:59.999828315+00:00
VOLUME 118,499,685 rows · 1,244,159,527 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 116,720,480 · e: 116,715,645 · g: 116,620,113 · c: 97,882,070 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,194,812 (19.57%) · e: 1,164,190 (0.98%) · g: 76,266 (0.06%) · c: 94,064,417 (79.38%) (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 118,499,685 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 4fdd68de6c53d3cba6de368401492aa7618067893e58a557cfdb5758d0ed35b4
the corpus checksum ledger names this file with the same digest
joined 118,502,970 to merged 118,499,685, minus 3,285 (minus 0.0028%)
boundary drops 3,285 · 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:57:47Z 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,827,408 120,729,216 0-41 f1048638b671b2abc2a50c03dd4406a02c4b8bd6df67d1c4de2952da53b6ab67 book 1,832,614 92,864,159 42-48 8533de7555e477cbcaede38f11ecb2aefc8e29b7afed87645d22061886d476fb last_trade_price 54,420 3,041,128 49-49 2d94c17cb9cbdbe6193d53aa52e762dd616a4877a85f07c76e3e54766d921da3 market_resolved 918 127,727 50-50 1d31f95f2d070b1f440412f6417aeb68e54a2ed39761bd202750388846ef8716 new_market 881 99,611 51-51 6542fc7c8f075c4f6041013e8140f9182775c661bb1d4e6faf51895804c4c4c0 price_change 105,781,364 1,025,873,622 52-455 bdb69c45103c696026310a5056e4369248e0e9e2f3560142880e8f2168ef83ed tick_size_change 2,080 77,339 456-456 f25139b37179a0e3f5dc915cc44e93b61a3c4f411259771b1765424d3754d044 EVENT MIX count share price_change 105,781,364 89.27% best_bid_ask 10,827,408 9.14% book 1,832,614 1.55% last_trade_price 54,420 0.05% tick_size_change 2,080 <0.01% market_resolved 918 <0.01% new_market 881 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,827,586 10,827,408 178 80,011 PARTIAL book 1,834,041 1,832,614 1,427 214,222 PARTIAL last_trade_price 54,420 54,420 0 3,073 PARTIAL market_resolved 918 918 0 783 PARTIAL new_market 881 881 0 642 PARTIAL price_change 105,783,044 105,781,364 1,680 145,692 PARTIAL tick_size_change 2,080 2,080 0 520 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,939,582 8,621,935 5ms 9ms 92ms 2.9s 0 transport_latency_assumed best_bid_ask e 10,825,989 100,314 39ms 45ms 137ms 3.2s 0 transport_latency_assumed best_bid_ask g 10,824,060 3,400 83ms 105ms 313ms 10.6s 0 transport_latency_assumed best_bid_ask h 10,826,647 2,101,759 17ms 22ms 102ms 10.2s 0 transport_latency_assumed book c 1,798,089 1,785,408 7.9min 6.1h 31.2d 105.1d 0 book_staleness book e 116,211 3,202 41ms 145ms 2.7s 86.5d 0 book_staleness book g 140,300 13,790 95ms 7.2min 2.6d 105.1d 0 book_staleness book h 116,181 30,214 20ms 53ms 2.6s 42.4d 0 book_staleness last_trade_price c 41,854 39,518 10ms 44ms 255ms 4.9s 0 transport_latency_assumed last_trade_price e 54,312 871 47ms 139ms 729ms 4.9s 0 transport_latency_assumed last_trade_price g 54,238 82 98ms 305ms 2.2s 10.3s 0 transport_latency_assumed last_trade_price h 54,313 13,949 23ms 65ms 292ms 5.4s 0 transport_latency_assumed market_resolved c 792 759 5ms 4.7min 5.9min 6.2min 0 transport_latency_assumed market_resolved e 783 5 40ms 123ms 4.2s 55.3s 0 transport_latency_assumed market_resolved g 783 3 89ms 253ms 712ms 58.2s 0 transport_latency_assumed market_resolved h 783 151 18ms 59ms 3.1s 50.5s 0 transport_latency_assumed new_market c 653 459 47ms 586ms 5.5min 10.8min 0 transport_latency_assumed new_market e 642 109 126ms 11.2s 29.6s 1.3min 0 transport_latency_assumed new_market g 642 87 265ms 15.2s 33.5s 3.4min 0 transport_latency_assumed new_market h 642 226 94ms 14.3s 31.8s 5.3min 0 transport_latency_assumed price_change c 87,099,312 83,614,636 5ms 10ms 153ms 3.4s 0 transport_latency_assumed price_change e 105,715,628 1,059,677 39ms 47ms 204ms 3.2s 0 transport_latency_assumed price_change g 105,598,010 58,904 84ms 116ms 423ms 14.0s 0 transport_latency_assumed price_change h 105,719,834 21,048,147 18ms 24ms 154ms 10.2s 0 transport_latency_assumed tick_size_change c 1,788 1,702 5ms 16ms 61ms 159ms 0 transport_latency_assumed tick_size_change e 2,080 12 39ms 49ms 175ms 211ms 0 transport_latency_assumed tick_size_change g 2,080 not meas. 84ms 99ms 233ms 299ms 0 transport_latency_assumed tick_size_change h 2,080 366 18ms 31ms 69ms 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-11/23/2026-09-11T23.parquet sha256sum 2026-09-11T23.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.