Hour audit: 2026-09-17T07
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-17T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T07:00:00.000260923+00:00 · last event 2026-09-17T07:59:59.999403010+00:00
VOLUME 101,817,430 rows · 1,037,057,737 bytes (989.02 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 101,365,127 · h: 101,308,295 · e: 101,302,288 · f: 101,298,739 · g: 101,283,732 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 98,015,318 (96.27%) · h: 3,030,487 (2.98%) · e: 408,654 (0.40%) · f: 241,704 (0.24%) · g: 121,267 (0.12%) (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 101,817,430 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9cb976e1663e9ce4659a294939efccfc5e4c4c01be390c1b83ec06ac2f63bf37
the corpus checksum ledger names this file with the same digest
joined 101,820,130 to merged 101,817,430, minus 2,700 (minus 0.0027%)
boundary drops 2,700 · 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-17T08:56:36Z 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,039,262 123,480,395 0-42 8fa0bbc4f22e6d59fb2d2a73892a3e17e9ee1b7aa8cdb0ff19d22fe485e8d7a8 book 637,079 55,082,243 43-45 9561a5a27723108815a49a12d635549fc88eb394339914f714a3729cf014fd5d last_trade_price 44,127 2,552,558 46-46 f0af4acecb61f50dcce4508a7be086848f4cff6ded1c39c6928f5ba83f316fa6 market_resolved 544 90,580 47-47 55ce6b7db55b8e66dd87375b3dc2764c34d1fd5e003a91fae44cdf8a6ad26249 new_market 825 89,002 48-48 663bfe21f6174d4cfab994c7dc0c2a32c1786d39b0dad6243e72468f47bb8bf7 price_change 90,093,329 854,517,132 49-392 0a87da09fd9ad9a8392b7d04a1c26dfb3d4e52bb127b43ffb6fb1bd8c9eb502b tick_size_change 2,264 83,720 393-393 d9327ec9fd29c29063377cb25acd95ba7aa2b86ebe4480ab244d10024b3e49b3 EVENT MIX count share price_change 90,093,329 88.49% best_bid_ask 11,039,262 10.84% book 637,079 0.63% last_trade_price 44,127 0.04% tick_size_change 2,264 <0.01% new_market 825 <0.01% market_resolved 544 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,039,484 11,039,262 222 121 FULL book 638,091 637,079 1,012 149,932 FULL last_trade_price 44,127 44,127 0 1 FULL market_resolved 544 544 0 0 FULL new_market 825 825 0 0 FULL price_change 90,094,795 90,093,329 1,466 56 FULL tick_size_change 2,264 2,264 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,038,140 10,716,017 5ms 8ms 64ms 3.9s 0 transport_latency_assumed best_bid_ask e 11,034,881 25,398 39ms 44ms 114ms 5.1s 0 transport_latency_assumed best_bid_ask f 11,035,898 9,789 46ms 51ms 128ms 2.5s 0 transport_latency_assumed best_bid_ask g 11,036,324 1,227 76ms 92ms 222ms 12.4s 0 transport_latency_assumed best_bid_ask h 11,036,291 286,831 18ms 22ms 91ms 7.6s 0 transport_latency_assumed book c 213,591 182,907 16.0s 35.4min 25.7d 110.4d 0 book_staleness book e 233,690 116,570 28.3s 44.0min 25.8d 110.4d 0 book_staleness book f 235,493 119,337 29.9s 41.8min 25.7d 110.4d 0 book_staleness book g 224,540 104,140 23.3s 38.1min 25.7d 110.4d 0 book_staleness book h 226,319 114,125 24.5s 40.3min 25.7d 110.4d 0 book_staleness last_trade_price c 44,006 41,980 10ms 43ms 210ms 4.9s 0 transport_latency_assumed last_trade_price e 43,801 258 46ms 101ms 738ms 5.1s 0 transport_latency_assumed last_trade_price f 43,814 116 53ms 108ms 364ms 4.9s 0 transport_latency_assumed last_trade_price g 43,926 5 90ms 201ms 1.6s 12.5s 0 transport_latency_assumed last_trade_price h 43,851 1,768 23ms 65ms 270ms 7.4s 0 transport_latency_assumed market_resolved c 544 535 5ms 8ms 44ms 195ms 0 transport_latency_assumed market_resolved e 544 1 112ms 196ms 469ms 813ms 0 transport_latency_assumed market_resolved f 544 not meas. 118ms 197ms 494ms 713ms 0 transport_latency_assumed market_resolved g 544 not meas. 204ms 330ms 800ms 1.6s 0 transport_latency_assumed market_resolved h 544 8 37ms 64ms 205ms 5.0s 0 transport_latency_assumed new_market c 576 346 72ms 14.9s 38.7s 1.3min 0 transport_latency_assumed new_market e 576 88 158ms 15.4s 29.4s 56.1s 0 transport_latency_assumed new_market f 576 98 143ms 12.8s 35.5s 1.1min 0 transport_latency_assumed new_market g 576 55 250ms 21.9s 39.5s 58.6s 0 transport_latency_assumed new_market h 576 238 108ms 12.9s 39.5s 1.1min 0 transport_latency_assumed price_change c 90,066,006 87,071,329 5ms 9ms 81ms 3.9s 0 transport_latency_assumed price_change e 89,986,532 266,331 39ms 45ms 175ms 5.1s 0 transport_latency_assumed price_change f 89,980,150 112,364 46ms 53ms 191ms 5.1s 0 transport_latency_assumed price_change g 89,975,558 15,840 77ms 95ms 338ms 12.5s 0 transport_latency_assumed price_change h 89,998,450 2,627,465 18ms 24ms 133ms 7.6s 0 transport_latency_assumed tick_size_change c 2,264 2,204 5ms 7ms 65ms 174ms 0 transport_latency_assumed tick_size_change e 2,264 8 39ms 64ms 191ms 351ms 0 transport_latency_assumed tick_size_change f 2,264 not meas. 46ms 51ms 184ms 238ms 0 transport_latency_assumed tick_size_change g 2,264 not meas. 76ms 94ms 256ms 390ms 0 transport_latency_assumed tick_size_change h 2,264 52 18ms 24ms 139ms 905ms 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/07/2026-09-17T07.parquet sha256sum 2026-09-17T07.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.