Hour audit: 2026-09-22T16
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-22T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T16:00:00.000006719+00:00 · last event 2026-09-22T16:59:59.999817693+00:00
VOLUME 103,766,381 rows · 1,172,624,131 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefhik — 6 machines contributed rows
captured k: 103,393,174 · c: 103,392,731 · h: 103,296,196 · f: 102,860,795 · e: 102,763,168 · i: 100,096,577 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 9,955,684 (9.59%) · c: 89,760,624 (86.50%) · h: 2,448,965 (2.36%) · f: 124,686 (0.12%) · e: 162,161 (0.16%) · i: 1,314,261 (1.27%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 103,766,381 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 ba273f87559e7926f543346de855e89f70619c7bb07fb5ab052a10f6a73be5ee
the corpus checksum ledger names this file with the same digest
joined 103,767,423 to merged 103,766,381, minus 1,042 (minus 0.0010%)
boundary drops 1,042 · 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-23T00:13:14Z as cefhik
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 10,064,354 124,295,933 0-38 f66cb09b23191c5cbfca59f2472f3ce00a199335352e6f1ac7c863f05f1ff622 book 525,088 45,094,198 39-41 05165d18c9fbf9509bcc9218ece60f2512069572f4b6d2fc854b59699c3631a9 last_trade_price 67,175 3,872,066 42-42 102179739dfc7ebc0c0675667ce78d8a2413e12dfb55c47ef73dafbf657658a6 market_resolved 1,110 182,432 43-43 9dfcd760c7c25154bf09b5b7162b0bd693ddf39348fa3e520e9289945c81a2ec new_market 5,868 587,111 44-44 5fb381d5aaa933562fc02c1212ab0e7fb443dc56b97810c6a8ebafecbf9f92d3 price_change 93,100,138 997,305,322 45-400 398a4783e75f3dcbef2721ce623cd705052a93468ccc8491f8ed744fafc93fc1 tick_size_change 2,648 99,053 401-401 ee170b67705cab3a7419f7a8a0f8a6a30539a42b9124ff4b176bad1009d9a736 EVENT MIX count share price_change 93,100,138 89.72% best_bid_ask 10,064,354 9.70% book 525,088 0.51% last_trade_price 67,175 0.06% new_market 5,868 <0.01% tick_size_change 2,648 <0.01% market_resolved 1,110 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,064,442 10,064,354 88 262 FULL book 525,162 525,088 74 113,816 FULL last_trade_price 67,175 67,175 0 7 FULL market_resolved 1,110 1,110 0 1 FULL new_market 5,868 5,868 0 47 FULL price_change 93,101,018 93,100,138 880 330 FULL tick_size_change 2,648 2,648 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,059,315 8,851,904 5ms 21ms 196ms 11.9s 0 transport_latency_assumed best_bid_ask e 10,053,788 12,688 42ms 81ms 438ms 20.4s 0 transport_latency_assumed best_bid_ask f 10,053,928 7,108 49ms 90ms 442ms 20.2s 0 transport_latency_assumed best_bid_ask h 10,060,815 210,849 18ms 38ms 282ms 45.1s 0 transport_latency_assumed best_bid_ask i 9,935,430 120,870 22ms 52ms 974ms 15.5s 0 transport_latency_assumed best_bid_ask k 10,061,750 860,935 12ms 26ms 188ms 44.5s 0 transport_latency_assumed book c 225,643 192,364 21ms 4.0h 27.9d 115.8d 0 book_staleness book e 169,207 28,651 120ms 7.3min 15.3d 115.8d 0 book_staleness book f 191,950 47,949 208ms 23.5min 17.1d 115.8d 0 book_staleness book h 170,767 29,937 29ms 6.7min 13.3d 97.3d 0 book_staleness book i 300,063 152,799 5.8s 13.5h 21.0d 115.8d 0 book_staleness book k 208,258 73,388 27ms 28.1min 20.4d 115.8d 0 book_staleness last_trade_price c 66,793 56,803 6ms 36ms 243ms 10.3s 0 transport_latency_assumed last_trade_price e 64,802 79 75ms 1.4s 13.0s 20.5s 0 transport_latency_assumed last_trade_price f 64,624 39 84ms 2.3s 12.6s 20.2s 0 transport_latency_assumed last_trade_price h 66,793 1,644 20ms 92ms 459ms 45.7s 0 transport_latency_assumed last_trade_price i 60,556 598 25ms 709ms 5.0s 15.5s 0 transport_latency_assumed last_trade_price k 66,909 8,012 13ms 50ms 251ms 37.2s 0 transport_latency_assumed market_resolved c 1,099 875 6ms 17.2s 51.2s 1.0min 0 transport_latency_assumed market_resolved e 1,099 3 54ms 14.6s 49.1s 57.4s 0 transport_latency_assumed market_resolved f 1,099 7 70ms 782ms 57.6s 58.5s 0 transport_latency_assumed market_resolved h 1,099 133 25ms 10.2s 45.1s 51.9s 0 transport_latency_assumed market_resolved i 1,098 28 26ms 17.6s 51.9s 1.5min 0 transport_latency_assumed market_resolved k 1,099 64 17ms 15.9s 50.7s 59.2s 0 transport_latency_assumed new_market c 3,605 1,228 87ms 1.6min 9.6min 24.9d 0 transport_latency_assumed new_market e 3,652 608 153ms 1.7min 154.8d 215.8d 0 transport_latency_assumed new_market f 3,652 549 152ms 1.7min 154.8d 215.8d 0 transport_latency_assumed new_market h 3,652 1,253 85ms 1.9min 154.8d 215.8d 0 transport_latency_assumed new_market i 3,652 868 103ms 1.7min 154.8d 215.8d 0 transport_latency_assumed new_market k 3,652 1,362 83ms 1.5min 154.8d 215.8d 0 transport_latency_assumed price_change c 93,033,628 80,655,128 6ms 27ms 220ms 11.9s 0 transport_latency_assumed price_change e 92,467,972 120,132 43ms 156ms 4.4s 20.6s 0 transport_latency_assumed price_change f 92,542,894 69,034 50ms 167ms 5.2s 20.2s 0 transport_latency_assumed price_change h 92,990,422 2,205,088 19ms 49ms 338ms 45.1s 0 transport_latency_assumed price_change i 89,793,166 1,039,074 23ms 109ms 2.8s 15.5s 0 transport_latency_assumed price_change k 93,048,858 9,011,682 12ms 32ms 210ms 50.4s 0 transport_latency_assumed tick_size_change c 2,648 2,322 5ms 15ms 142ms 229ms 0 transport_latency_assumed tick_size_change e 2,648 not meas. 42ms 69ms 210ms 494ms 0 transport_latency_assumed tick_size_change f 2,648 not meas. 49ms 72ms 254ms 406ms 0 transport_latency_assumed tick_size_change h 2,648 61 18ms 36ms 120ms 371ms 0 transport_latency_assumed tick_size_change i 2,612 24 23ms 48ms 408ms 3.3s 0 transport_latency_assumed tick_size_change k 2,648 241 12ms 22ms 81ms 247ms 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/16/2026-09-22T16.parquet sha256sum 2026-09-22T16.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.