Hour audit: 2026-09-17T05
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-17T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T05:00:00.000203159+00:00 · last event 2026-09-17T05:59:59.999956506+00:00
VOLUME 108,904,775 rows · 1,106,524,640 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 108,412,175 · c: 108,404,934 · f: 108,364,970 · e: 107,580,230 · g: 104,739,565 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,079,171 (3.75%) · c: 103,752,476 (95.27%) · f: 225,660 (0.21%) · e: 438,989 (0.40%) · g: 408,479 (0.38%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 108,904,775 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4f3ff1c7680938e8db0a537a9c89e4ec27a1fc11b7482c0705cbc2cd92443068
the corpus checksum ledger names this file with the same digest
joined 108,907,766 to merged 108,904,775, minus 2,991 (minus 0.0027%)
boundary drops 2,991 · 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-17T06:58:15Z as cefgh
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,724,970 140,005,848 0-48 dd944c4fb6cdef3cad8a05cdefaacdcda9ae3de8193ee6a42e7e0df67346712a book 559,517 53,475,565 49-51 7e4d1c9447e191f0e7d3568f6765e11ec0e5e8624dae52288f303289b75851eb last_trade_price 39,669 2,264,015 52-52 257fb4375dce15c62070969a4d2584323e4410c14b1aa14a81247afe9b67417f market_resolved 1,056 174,531 53-53 8ca1517c794bc16c28cd360f855f044248e14c7af491c546750e35af0b50ddf7 new_market 955 103,948 54-54 d68cdf574c23f9b763da8e25470c021a4a262ddd72483b5f31ddbf45c85325e0 price_change 95,575,368 909,141,259 55-419 56c33b97c0c7cac7987b497e7729b9feee7c587ad6ecc4f9def48f97d6bdf3a7 tick_size_change 3,240 118,219 420-420 bba50291382ff8edf82e726b710d38a223523e9d9285424c7c6a43da9190932f EVENT MIX count share price_change 95,575,368 87.76% best_bid_ask 12,724,970 11.68% book 559,517 0.51% last_trade_price 39,669 0.04% tick_size_change 3,240 <0.01% market_resolved 1,056 <0.01% new_market 955 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,725,321 12,724,970 351 428 FULL book 559,727 559,517 210 172,849 FULL last_trade_price 39,669 39,669 0 50 FULL market_resolved 1,056 1,056 0 43 FULL new_market 955 955 0 0 FULL price_change 95,577,798 95,575,368 2,430 111 FULL tick_size_change 3,240 3,240 0 15 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,723,828 12,271,739 4ms 8ms 85ms 4.2s 0 transport_latency_assumed best_bid_ask e 12,687,243 33,273 41ms 46ms 129ms 8.5s 0 transport_latency_assumed best_bid_ask f 12,722,063 16,156 46ms 52ms 151ms 3.9s 0 transport_latency_assumed best_bid_ask g 12,221,687 2,142 78ms 95ms 236ms 9.7s 0 transport_latency_assumed best_bid_ask h 12,722,749 401,660 17ms 22ms 109ms 20.3s 0 transport_latency_assumed book c 118,449 98,340 7ms 14.1min 11.7d 110.3d 0 book_staleness book e 147,181 54,596 130ms 21.3min 11.7d 110.3d 0 book_staleness book f 109,000 16,742 49ms 9.7min 11.6d 110.3d 0 book_staleness book g 454,676 373,004 2.1min 1.1d 36.4d 110.3d 0 book_staleness book h 102,463 16,835 22ms 5.0min 9.8d 91.8d 0 book_staleness last_trade_price c 39,532 37,222 10ms 44ms 211ms 4.9s 0 transport_latency_assumed last_trade_price e 37,469 200 48ms 100ms 464ms 8.3s 0 transport_latency_assumed last_trade_price f 39,452 139 52ms 105ms 417ms 4.9s 0 transport_latency_assumed last_trade_price g 38,576 28 88ms 177ms 707ms 9.7s 0 transport_latency_assumed last_trade_price h 39,470 2,080 23ms 64ms 249ms 19.1s 0 transport_latency_assumed market_resolved c 1,056 1,032 5ms 9ms 114ms 575ms 0 transport_latency_assumed market_resolved e 1,056 4 112ms 168ms 376ms 951ms 0 transport_latency_assumed market_resolved f 1,056 2 117ms 163ms 420ms 708ms 0 transport_latency_assumed market_resolved g 1,013 not meas. 202ms 262ms 743ms 1.6s 0 transport_latency_assumed market_resolved h 1,056 18 37ms 64ms 155ms 468ms 0 transport_latency_assumed new_market c 681 496 57ms 14.8s 25.8s 4.1min 0 transport_latency_assumed new_market e 681 148 132ms 9.9s 38.1s 48.5s 0 transport_latency_assumed new_market f 681 55 160ms 16.2s 26.4s 58.2s 0 transport_latency_assumed new_market g 682 43 237ms 611ms 21.8s 42.5min 0 transport_latency_assumed new_market h 681 213 125ms 20.0s 28.7s 1.2min 0 transport_latency_assumed price_change c 95,518,148 91,340,472 5ms 10ms 165ms 5.0s 0 transport_latency_assumed price_change e 94,703,360 350,768 41ms 48ms 260ms 8.6s 0 transport_latency_assumed price_change f 95,489,478 192,566 46ms 56ms 294ms 5.2s 0 transport_latency_assumed price_change g 92,019,751 33,262 78ms 99ms 380ms 9.7s 0 transport_latency_assumed price_change h 95,542,516 3,658,300 18ms 26ms 199ms 20.9s 0 transport_latency_assumed tick_size_change c 3,240 3,175 5ms 7ms 28ms 1.4s 0 transport_latency_assumed tick_size_change e 3,240 not meas. 41ms 60ms 104ms 151ms 0 transport_latency_assumed tick_size_change f 3,240 not meas. 46ms 50ms 95ms 128ms 0 transport_latency_assumed tick_size_change g 3,180 not meas. 78ms 92ms 144ms 267ms 0 transport_latency_assumed tick_size_change h 3,240 65 17ms 22ms 67ms 3.3s 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-17/05/2026-09-17T05.parquet sha256sum 2026-09-17T05.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.