Hour audit: 2026-09-17T16
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-17T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T16:00:00.000018196+00:00 · last event 2026-09-17T16:59:59.999860586+00:00
VOLUME 112,012,042 rows · 1,163,271,812 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 111,922,554 · f: 111,859,168 · h: 111,809,928 · e: 111,790,009 · g: 111,570,530 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 105,923,542 (94.56%) · f: 240,476 (0.21%) · h: 5,390,873 (4.81%) · e: 407,469 (0.36%) · g: 49,682 (0.04%) (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 112,012,042 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b9f2df95a214ff384aea58557fef25f1a3c37c764465f9f8f6207c370a94c424
the corpus checksum ledger names this file with the same digest
joined 112,016,263 to merged 112,012,042, minus 4,221 (minus 0.0038%)
boundary drops 4,221 · 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-17T18:02:39Z 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 11,218,765 130,081,033 0-42 35a0dce780d70be883f32ea2e2fe47266837e85b4a2dfc0041f318edd40529f2 book 205,553 21,976,191 43-43 cb45732f2dd48f0785817b8539af7b13cb4727016de53fa06d3929a0f20d6ff0 last_trade_price 63,493 3,690,068 44-44 c771f22e716b6f3f33cf9a4c82e16c96149718a3dc05ec2d25929ebc43b528ad market_resolved 1,239 202,783 45-45 5298a2cd82b660cd22a4090ced61869a2079c7c63b7107d4df98259bc3aa5509 new_market 1,098 113,310 46-46 a8e84f1343632c912b60c53803675b2daf5c08029851af69a426664f4152f326 price_change 100,517,646 1,005,778,404 47-430 72578563347bb685f711ebed7d771ea39338774b09ecf682ec72011322b0048d tick_size_change 4,248 155,619 431-431 47e8884c22e8a0f577781cb162883086b8f2fc5f094fefc039edbc743b2e2314 EVENT MIX count share price_change 100,517,646 89.74% best_bid_ask 11,218,765 10.02% book 205,553 0.18% last_trade_price 63,493 0.06% tick_size_change 4,248 <0.01% market_resolved 1,239 <0.01% new_market 1,098 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,219,040 11,218,765 275 138 FULL book 205,743 205,553 190 26,687 FULL last_trade_price 63,493 63,493 0 0 FULL market_resolved 1,239 1,239 0 0 FULL new_market 1,098 1,098 0 0 FULL price_change 100,521,402 100,517,646 3,756 82 FULL tick_size_change 4,248 4,248 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,217,837 10,677,779 6ms 13ms 84ms 7.4s 0 transport_latency_assumed best_bid_ask e 11,214,145 31,692 41ms 51ms 195ms 11.7s 0 transport_latency_assumed best_bid_ask f 11,215,928 16,217 45ms 59ms 209ms 7.7s 0 transport_latency_assumed best_bid_ask g 11,212,560 1,314 78ms 101ms 348ms 17.0s 0 transport_latency_assumed best_bid_ask h 11,216,039 491,763 18ms 30ms 123ms 36.6s 0 transport_latency_assumed book c 151,807 143,066 8ms 45.5s 8.3d 110.7d 0 book_staleness book e 141,882 12,216 44ms 2.9s 1.4d 110.7d 0 book_staleness book f 139,526 8,657 49ms 1.5s 34.4min 92.2d 0 book_staleness book g 147,337 16,827 92ms 27.9s 5.9d 92.2d 0 book_staleness book h 149,942 24,787 24ms 25.4s 4.2d 92.2d 0 book_staleness last_trade_price c 63,283 59,738 12ms 51ms 257ms 4.9s 0 transport_latency_assumed last_trade_price e 62,711 236 56ms 463ms 5.9s 11.6s 0 transport_latency_assumed last_trade_price f 63,075 185 61ms 399ms 4.1s 7.7s 0 transport_latency_assumed last_trade_price g 62,210 78 100ms 1.0s 7.6s 16.8s 0 transport_latency_assumed last_trade_price h 63,168 3,256 25ms 93ms 540ms 26.0s 0 transport_latency_assumed market_resolved c 1,228 1,187 6ms 13ms 289ms 1.0min 0 transport_latency_assumed market_resolved e 1,228 not meas. 43ms 190ms 656ms 1.0min 0 transport_latency_assumed market_resolved f 1,228 1 48ms 194ms 505ms 59.6s 0 transport_latency_assumed market_resolved g 1,228 2 88ms 282ms 816ms 2.9s 0 transport_latency_assumed market_resolved h 1,228 49 20ms 64ms 260ms 59.0s 0 transport_latency_assumed new_market c 719 463 63ms 17.4s 1.4min 1.7min 0 transport_latency_assumed new_market e 719 143 155ms 22.0s 1.5min 1.8min 0 transport_latency_assumed new_market f 719 116 168ms 17.9s 1.4min 3.0min 0 transport_latency_assumed new_market g 719 79 268ms 16.8s 1.4min 1.9min 0 transport_latency_assumed new_market h 719 297 75ms 17.8s 1.2min 1.7min 0 transport_latency_assumed price_change c 100,483,432 95,037,152 6ms 17ms 122ms 7.4s 0 transport_latency_assumed price_change e 100,365,076 363,174 41ms 74ms 1.2s 11.8s 0 transport_latency_assumed price_change f 100,434,444 215,296 46ms 81ms 1.2s 7.7s 0 transport_latency_assumed price_change g 100,142,228 31,382 79ms 142ms 3.0s 17.0s 0 transport_latency_assumed price_change h 100,374,584 4,870,642 19ms 37ms 219ms 42.7s 0 transport_latency_assumed tick_size_change c 4,248 4,157 6ms 9ms 46ms 346ms 0 transport_latency_assumed tick_size_change e 4,248 8 40ms 46ms 167ms 498ms 0 transport_latency_assumed tick_size_change f 4,248 4 45ms 52ms 193ms 470ms 0 transport_latency_assumed tick_size_change g 4,248 not meas. 78ms 94ms 214ms 576ms 0 transport_latency_assumed tick_size_change h 4,248 79 18ms 25ms 89ms 346ms 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/16/2026-09-17T16.parquet sha256sum 2026-09-17T16.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.