Hour audit: 2026-09-15T21
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-15T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T21:00:00.000274219+00:00 · last event 2026-09-15T21:59:59.999904192+00:00
VOLUME 110,582,167 rows · 1,158,844,557 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 109,920,630 · e: 109,866,229 · f: 109,857,318 · g: 109,781,335 · c: 105,696,873 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,763,927 (7.02%) · e: 601,044 (0.54%) · f: 287,270 (0.26%) · g: 74,262 (0.07%) · c: 101,855,664 (92.11%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,582,167 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cab3f2c013ba93108df1bd891391ca8f467c5c3eba8db32c5f183a14a7c1bda9
the corpus checksum ledger names this file with the same digest
joined 110,585,910 to merged 110,582,167, minus 3,743 (minus 0.0034%)
boundary drops 3,743 · 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-15T22:58:38Z 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,414,124 141,051,982 0-47 0b6a72d79e87060eee3de4364b3e2d28478d36c172e622a416a870f760188191 book 839,838 65,929,741 48-51 64b963218722c31aa7b09c27bf2f61ad6ca314ca588e4ca411c9950bda756031 last_trade_price 48,705 2,823,962 52-52 a6f5b99ab5a2da810ffa7f0c403ce805aa80a4f056a46f534ec5cf7366ac1478 market_resolved 944 141,084 53-53 44b7300d16eb2ea7ed06d3a36877f12177bd1d673aeb0fc30e37124d423e25d4 new_market 906 94,705 54-54 afd95eb06e4f3fa0f0a58c900cbf85bf610139e1c628e53fdbf13af5cdc7414f price_change 97,274,742 947,433,912 55-426 170f681591e78ea3e78263a764cba0208c3ba9dc0c6a7d2f3e6fcd22a079befd tick_size_change 2,908 106,986 427-427 e4a6a4dd74dcac811326abafb463616dce86faf58132ff789f2f07eb600a54cb EVENT MIX count share price_change 97,274,742 87.97% best_bid_ask 12,414,124 11.23% book 839,838 0.76% last_trade_price 48,705 0.04% tick_size_change 2,908 <0.01% market_resolved 944 <0.01% new_market 906 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,414,367 12,414,124 243 479 FULL book 841,274 839,838 1,436 175,471 FULL last_trade_price 48,705 48,705 0 61 FULL market_resolved 944 944 0 32 FULL new_market 906 906 0 0 FULL price_change 97,276,806 97,274,742 2,064 90 FULL tick_size_change 2,908 2,908 0 39 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,916,868 11,513,707 5ms 9ms 73ms 7.3s 0 transport_latency_assumed best_bid_ask e 12,410,638 48,638 40ms 47ms 150ms 6.6s 0 transport_latency_assumed best_bid_ask f 12,411,846 22,296 44ms 51ms 160ms 7.1s 0 transport_latency_assumed best_bid_ask g 12,409,385 908 80ms 96ms 302ms 21.6s 0 transport_latency_assumed best_bid_ask h 12,411,923 828,575 18ms 24ms 91ms 8.4s 0 transport_latency_assumed book c 551,101 507,730 2.7min 20.4h 35.1d 109.0d 0 book_staleness book e 264,311 109,309 30.2s 1.1h 24.4d 109.0d 0 book_staleness book f 195,017 60,213 957ms 29.1min 24.3d 109.0d 0 book_staleness book g 198,471 60,657 2.4s 29.3min 24.3d 109.0d 0 book_staleness book h 247,486 101,929 21.3s 38.2min 24.3d 109.0d 0 book_staleness last_trade_price c 46,419 44,471 11ms 47ms 229ms 5.0s 0 transport_latency_assumed last_trade_price e 48,380 340 50ms 207ms 1.8s 6.6s 0 transport_latency_assumed last_trade_price f 48,579 183 56ms 262ms 3.9s 7.1s 0 transport_latency_assumed last_trade_price g 48,331 30 99ms 466ms 6.9s 21.8s 0 transport_latency_assumed last_trade_price h 48,471 3,681 24ms 92ms 460ms 7.4s 0 transport_latency_assumed market_resolved c 836 815 5ms 15ms 4.9min 5.0min 0 transport_latency_assumed market_resolved e 864 8 44ms 299ms 59.3s 59.3s 0 transport_latency_assumed market_resolved f 864 1 50ms 354ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 860 not meas. 90ms 390ms 1.1s 5.7s 0 transport_latency_assumed market_resolved h 864 120 20ms 116ms 58.2s 58.2s 0 transport_latency_assumed new_market c 607 418 61ms 41.5s 1.7min 39.1min 0 transport_latency_assumed new_market e 606 45 155ms 34.8s 1.5min 4.7min 0 transport_latency_assumed new_market f 606 101 160ms 37.0s 1.5min 4.7min 0 transport_latency_assumed new_market g 606 83 242ms 37.6s 1.5min 1.6min 0 transport_latency_assumed new_market h 606 259 75ms 33.4s 1.6min 2.0min 0 transport_latency_assumed price_change c 93,178,290 89,785,908 5ms 10ms 87ms 7.3s 0 transport_latency_assumed price_change e 97,138,522 442,696 40ms 52ms 341ms 6.6s 0 transport_latency_assumed price_change f 97,197,498 204,476 44ms 58ms 356ms 7.1s 0 transport_latency_assumed price_change g 97,120,774 12,584 80ms 106ms 737ms 21.6s 0 transport_latency_assumed price_change h 97,208,372 6,829,078 18ms 28ms 142ms 8.7s 0 transport_latency_assumed tick_size_change c 2,752 2,615 5ms 11ms 150ms 356ms 0 transport_latency_assumed tick_size_change e 2,908 8 41ms 49ms 116ms 177ms 0 transport_latency_assumed tick_size_change f 2,908 not meas. 44ms 60ms 126ms 751ms 0 transport_latency_assumed tick_size_change g 2,908 not meas. 80ms 95ms 238ms 554ms 0 transport_latency_assumed tick_size_change h 2,908 285 18ms 26ms 45ms 125ms 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-15/21/2026-09-15T21.parquet sha256sum 2026-09-15T21.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.