Hour audit: 2026-09-23T00
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-23T00 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T00:00:00.001659774+00:00 · last event 2026-09-23T00:59:59.999625534+00:00
VOLUME 124,764,149 rows · 1,346,688,874 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured h: 122,864,457 · i: 122,806,730 · f: 118,037,277 · c: 116,586,484 · k: 100,089,437 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,633,175 (4.52%) · i: 1,784,918 (1.43%) · f: 261,002 (0.21%) · c: 105,484,949 (84.55%) · k: 11,600,105 (9.30%) (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 124,764,149 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dd22d78232acecec43effc2f6279a1157d6828ee5f94373df439064a8d772a8c
the corpus checksum ledger names this file with the same digest
joined 124,775,095 to merged 124,764,149, minus 10,946 (minus 0.0088%)
boundary drops 10,946 · 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-23T02:51:05Z as cfhik
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 12,793,915 144,656,426 0-48 969309322412d066a37342ebc5c9cb8cddb34eb30d94fe1c1bf6a577a84f46dd book 1,931,117 89,469,902 49-56 df3237c9f4f11f76fe624f7bd6c0178b68eb8a3dff4dd21676eab27ace361b50 last_trade_price 54,004 3,037,396 57-57 b5acdd5975413a589da068793d9b59bb84b96f6faa7325190d86a16c947b33ff market_resolved 1,218 148,551 58-58 8670077305728a8f7a2df543259ae6e7e9c0c51ead037ec7dc4cc72e94e3a9ef new_market 775 70,791 59-59 fec597f94f884fdb6aa8aa36d68c021abd2de0ce44232c24ccbb19902e7f23c5 price_change 109,980,520 1,107,790,778 60-479 0b13636ecb44859c1adb923d621bd55a0e1b80663ab77c6a38c1ae4f053b2fad tick_size_change 2,600 96,055 480-480 407dd8fb2a8ab5ab98fc76efcf84098bee25d3e1da7b66acca3fac01573de88c EVENT MIX count share price_change 109,980,520 88.15% best_bid_ask 12,793,915 10.25% book 1,931,117 1.55% last_trade_price 54,004 0.04% tick_size_change 2,600 <0.01% market_resolved 1,218 <0.01% new_market 775 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,793,995 12,793,915 80 2,501 FULL book 1,941,069 1,931,117 9,952 191,502 FULL last_trade_price 54,004 54,004 0 418 FULL market_resolved 1,218 1,218 0 37 FULL new_market 775 775 0 0 FULL price_change 109,981,434 109,980,520 914 686 FULL tick_size_change 2,600 2,600 0 157 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,057,725 11,055,444 5ms 15ms 90ms 3.6s 0 transport_latency_assumed best_bid_ask f 12,244,558 6,292 49ms 63ms 173ms 2.7s 0 transport_latency_assumed best_bid_ask h 12,786,931 553,166 18ms 35ms 132ms 1.3min 0 transport_latency_assumed best_bid_ask i 12,774,313 170,217 20ms 31ms 105ms 2.0s 0 transport_latency_assumed best_bid_ask k 10,269,885 1,008,796 12ms 21ms 80ms 2.1s 0 transport_latency_assumed book c 545,040 264,823 6.4min 2.3d 38.3d 116.1d 0 book_staleness book f 540,183 143,142 7.6min 2.3d 38.4d 116.1d 0 book_staleness book h 213,273 66,973 300ms 15.2h 31.4d 116.1d 0 book_staleness book i 146,120 13,707 29ms 27.4min 15.6d 116.1d 0 book_staleness book k 1,672,921 1,442,472 12.8min 3.4d 42.2d 116.1d 0 book_staleness last_trade_price c 51,418 45,257 6ms 28ms 211ms 1.4s 0 transport_latency_assumed last_trade_price f 51,287 264 51ms 112ms 557ms 2.2s 0 transport_latency_assumed last_trade_price h 53,502 2,660 19ms 72ms 455ms 7.8s 0 transport_latency_assumed last_trade_price i 53,822 662 22ms 120ms 520ms 1.2s 0 transport_latency_assumed last_trade_price k 44,430 5,161 13ms 34ms 184ms 1.2s 0 transport_latency_assumed market_resolved c 876 752 5ms 29.8s 6.2min 6.2min 0 transport_latency_assumed market_resolved f 890 22 50ms 345ms 2.7min 4.3min 0 transport_latency_assumed market_resolved h 895 32 18ms 113ms 1.0min 1.0min 0 transport_latency_assumed market_resolved i 893 79 21ms 236ms 1.0min 1.6min 0 transport_latency_assumed market_resolved k 1,106 333 15ms 10.5min 15.7min 18.5min 0 transport_latency_assumed new_market c 434 224 52ms 9.9s 5.6min 5.6min 0 transport_latency_assumed new_market f 434 42 91ms 328ms 13.6s 1.6min 0 transport_latency_assumed new_market h 434 82 81ms 8.1s 14.3s 1.6min 0 transport_latency_assumed new_market i 434 124 83ms 9.3s 34.9s 37.6s 0 transport_latency_assumed new_market k 605 303 137ms 8.9min 13.9min 13.9min 0 transport_latency_assumed price_change c 103,928,551 94,116,263 5ms 19ms 109ms 3.6s 0 transport_latency_assumed price_change f 105,197,389 111,240 49ms 70ms 239ms 3.1s 0 transport_latency_assumed price_change h 109,806,822 5,010,110 18ms 41ms 183ms 1.3min 0 transport_latency_assumed price_change i 109,828,552 1,600,061 21ms 38ms 166ms 2.0s 0 transport_latency_assumed price_change k 88,098,394 9,142,846 13ms 24ms 95ms 2.2s 0 transport_latency_assumed tick_size_change c 2,440 2,186 5ms 19ms 126ms 251ms 0 transport_latency_assumed tick_size_change f 2,536 not meas. 49ms 66ms 126ms 299ms 0 transport_latency_assumed tick_size_change h 2,600 152 18ms 35ms 89ms 303ms 0 transport_latency_assumed tick_size_change i 2,596 68 21ms 32ms 99ms 223ms 0 transport_latency_assumed tick_size_change k 2,096 194 13ms 20ms 64ms 142ms 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-23/00/2026-09-23T00.parquet sha256sum 2026-09-23T00.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.