Hour audit: 2026-09-22T11
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-22T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T11:00:00.000045140+00:00 · last event 2026-09-22T11:59:59.999955668+00:00
VOLUME 104,334,340 rows · 1,124,685,368 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefhi — 5 machines contributed rows
captured h: 103,822,844 · f: 103,782,258 · e: 103,689,909 · i: 102,525,414 · c: 99,206,262 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,155,427 (6.86%) · f: 142,763 (0.14%) · e: 268,414 (0.26%) · i: 2,819,755 (2.70%) · c: 93,947,981 (90.05%) (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 104,334,340 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 211bbd177b5c1418452cb3469e27124cf4f6cbd4c454a9186f39137bc0cc57f4
the corpus checksum ledger names this file with the same digest
joined 104,335,527 to merged 104,334,340, minus 1,187 (minus 0.0011%)
boundary drops 1,187 · 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-22T12:57:29Z as cefhi
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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 8,632,370 102,149,115 0-32 1dc5fbff7393c05e53750a0acde7edb7a4343b70e73fd9275bcfee5da2706ac8 book 594,349 53,355,162 33-35 58c882ceceebc1e0b448ca3431fa018ade7947483df9a8f04042c60cbd8ecf52 last_trade_price 59,968 3,420,817 36-36 4986207ba2064d6bdda12bc7fa0d8d4221c743f6598f6e4066ddd61080dfe53d market_resolved 968 151,769 37-37 cce9741c1aba2df80313cf94665e132c1cc0c4c847c2cca574ac39adb005143e new_market 1,191 121,651 38-38 185eff68ac244f8d994ce66af3cce33fee642274099b29b91cc38c5b3ae06641 price_change 95,042,310 964,179,586 39-401 cc31a657fe34ac018e7e5e6d179e878a6a415138d64b31592afcc0f0b1f3043a tick_size_change 3,184 117,279 402-402 1d61ebc90ecb38562d7db2ee0e3df05421c41d2f6ad1ec65e67161cbdbb49cc7 EVENT MIX count share price_change 95,042,310 91.09% best_bid_ask 8,632,370 8.27% book 594,349 0.57% last_trade_price 59,968 0.06% tick_size_change 3,184 <0.01% new_market 1,191 <0.01% market_resolved 968 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,632,488 8,632,370 118 535 FULL book 594,473 594,349 124 174,980 FULL last_trade_price 59,969 59,968 1 84 FULL market_resolved 968 968 0 37 FULL new_market 1,191 1,191 0 0 FULL price_change 95,043,254 95,042,310 944 260 FULL tick_size_change 3,184 3,184 0 34 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,308,209 7,897,498 5ms 12ms 119ms 3.8s 0 transport_latency_assumed best_bid_ask e 8,627,854 15,691 41ms 53ms 243ms 15.1s 0 transport_latency_assumed best_bid_ask f 8,629,723 7,229 49ms 60ms 255ms 17.7s 0 transport_latency_assumed best_bid_ask h 8,630,940 497,903 19ms 30ms 160ms 58.5s 0 transport_latency_assumed best_bid_ask i 8,576,884 214,049 23ms 34ms 224ms 7.1s 0 transport_latency_assumed book c 541,047 530,358 4.0min 2.9d 40.7d 115.6d 0 book_staleness book e 127,432 6,894 45ms 2.0s 21.3h 97.5d 0 book_staleness book f 126,749 5,023 52ms 2.3s 14.6h 97.0d 0 book_staleness book h 124,260 14,382 23ms 92ms 18.1min 97.0d 0 book_staleness book i 146,636 37,692 27ms 35.8s 21.5h 23.9h 0 book_staleness last_trade_price c 54,711 51,371 6ms 21ms 208ms 3.5s 0 transport_latency_assumed last_trade_price e 59,042 367 45ms 464ms 5.7s 15.1s 0 transport_latency_assumed last_trade_price f 59,477 176 52ms 637ms 10.4s 17.7s 0 transport_latency_assumed last_trade_price h 59,719 6,232 20ms 63ms 406ms 10.3s 0 transport_latency_assumed last_trade_price i 56,003 1,822 24ms 184ms 3.0s 7.1s 0 transport_latency_assumed market_resolved c 896 812 5ms 27ms 3.8min 3.9min 0 transport_latency_assumed market_resolved e 927 97 43ms 12.3s 55.8s 55.9s 0 transport_latency_assumed market_resolved f 927 1 50ms 12.3s 55.8s 55.9s 0 transport_latency_assumed market_resolved h 927 38 19ms 14.0s 57.5s 57.6s 0 transport_latency_assumed market_resolved i 921 20 23ms 80ms 55.0s 55.6s 0 transport_latency_assumed new_market c 764 404 110ms 15.1s 30.9s 1.6min 0 transport_latency_assumed new_market e 764 151 192ms 15.9s 34.2s 1.7min 0 transport_latency_assumed new_market f 764 84 197ms 16.4s 33.1s 1.5min 0 transport_latency_assumed new_market h 764 234 173ms 16.0s 33.7s 1.6min 0 transport_latency_assumed new_market i 764 318 120ms 17.1s 44.3s 1.6min 0 transport_latency_assumed price_change c 90,297,587 85,464,621 5ms 14ms 136ms 3.9s 0 transport_latency_assumed price_change e 94,870,706 245,206 42ms 68ms 654ms 15.1s 0 transport_latency_assumed price_change f 94,961,434 130,250 49ms 75ms 875ms 17.7s 0 transport_latency_assumed price_change h 95,003,050 6,636,427 19ms 35ms 194ms 58.7s 0 transport_latency_assumed price_change i 93,741,022 2,565,806 23ms 46ms 716ms 7.1s 0 transport_latency_assumed tick_size_change c 3,048 2,917 5ms 8ms 41ms 116ms 0 transport_latency_assumed tick_size_change e 3,184 8 42ms 75ms 192ms 706ms 0 transport_latency_assumed tick_size_change f 3,184 not meas. 49ms 55ms 165ms 214ms 0 transport_latency_assumed tick_size_change h 3,184 211 19ms 36ms 84ms 679ms 0 transport_latency_assumed tick_size_change i 3,184 48 23ms 49ms 77ms 1.8s 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/11/2026-09-22T11.parquet sha256sum 2026-09-22T11.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.