Hour audit: 2026-09-16T21
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-16T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T21:00:00.000080920+00:00 · last event 2026-09-16T21:59:59.999666522+00:00
VOLUME 108,416,161 rows · 1,142,512,475 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 107,504,364 · e: 107,455,707 · f: 107,410,517 · g: 107,379,444 · c: 103,540,223 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,991,924 (7.37%) · e: 530,084 (0.49%) · f: 301,228 (0.28%) · g: 188,430 (0.17%) · c: 99,404,495 (91.69%) (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,416,161 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 636c22483d3dbe5d1ecaf3b8724241beda6f3d755c547381b5b894493edb60f3
the corpus checksum ledger names this file with the same digest
joined 108,429,307 to merged 108,416,161, minus 13,146 (minus 0.0121%)
boundary drops 13,146 · 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-16T22:58:47Z 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,137,600 137,441,922 0-46 522572387eccea1a249c009fe7d3c85fb53a1e84ddb894ecaa1e35132e12b67a book 1,274,256 81,667,933 47-51 79f44812d072c7fbd66cdcabc2897f467543a6a092ab05782c42a743f2fc9767 last_trade_price 50,117 2,945,928 52-52 5211fdc48df3cd0cc4a01e461a978f0be2788234d419013a2bf7c70a464e5960 market_resolved 1,707 266,729 53-53 bae0ce92b5deffb5527f7e636dd94de9bac6959dc40c5dec80bac68b9517b87c new_market 1,091 115,051 54-54 c977dd783ce83f9d7393ed60f646c46c1f33ac7eec69d277637e1bd1d4eedd13 price_change 94,946,962 918,677,854 55-417 930c96306b128312de8b048cb60d43efc15d49d6cf5ba30ddcf79deb3e059b20 tick_size_change 4,428 161,500 418-418 aeabcb27ec92d41f7218a5169f81133cd4071909aae685a3b18ebca314450c8b EVENT MIX count share price_change 94,946,962 87.58% best_bid_ask 12,137,600 11.20% book 1,274,256 1.18% last_trade_price 50,117 0.05% tick_size_change 4,428 <0.01% market_resolved 1,707 <0.01% new_market 1,091 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,137,932 12,137,600 332 451 FULL book 1,285,040 1,274,256 10,784 132,005 FULL last_trade_price 50,117 50,117 0 67 FULL market_resolved 1,707 1,707 0 11 FULL new_market 1,091 1,091 0 0 FULL price_change 94,948,992 94,946,962 2,030 103 FULL tick_size_change 4,428 4,428 0 28 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,656,648 11,231,477 5ms 9ms 79ms 3.1s 0 transport_latency_assumed best_bid_ask e 12,133,050 32,658 39ms 46ms 175ms 6.8s 0 transport_latency_assumed best_bid_ask f 12,133,211 11,857 46ms 55ms 196ms 7.7s 0 transport_latency_assumed best_bid_ask g 12,133,194 1,177 81ms 99ms 346ms 17.9s 0 transport_latency_assumed best_bid_ask h 12,133,717 860,431 18ms 24ms 100ms 10.4s 0 transport_latency_assumed book c 696,529 510,827 3.8min 1.3d 36.1d 110.0d 0 book_staleness book e 438,549 211,001 2.0min 14.5h 35.1d 110.0d 0 book_staleness book f 393,847 175,992 1.6min 7.7h 32.5d 110.0d 0 book_staleness book g 396,329 171,364 1.6min 9.2h 35.1d 110.0d 0 book_staleness book h 440,816 205,072 2.0min 14.9h 35.1d 110.0d 0 book_staleness last_trade_price c 48,310 46,224 10ms 46ms 226ms 4.8s 0 transport_latency_assumed last_trade_price e 49,921 199 51ms 316ms 2.9s 6.8s 0 transport_latency_assumed last_trade_price f 49,940 139 58ms 291ms 2.9s 7.9s 0 transport_latency_assumed last_trade_price g 50,046 29 96ms 602ms 8.8s 18.0s 0 transport_latency_assumed last_trade_price h 49,986 3,526 24ms 92ms 530ms 10.4s 0 transport_latency_assumed market_resolved c 1,664 1,618 5ms 10ms 4.6min 6.0min 0 transport_latency_assumed market_resolved e 1,664 4 41ms 162ms 456ms 2.2min 0 transport_latency_assumed market_resolved f 1,664 not meas. 48ms 187ms 431ms 691ms 0 transport_latency_assumed market_resolved g 1,664 1 85ms 249ms 609ms 2.1min 0 transport_latency_assumed market_resolved h 1,664 84 20ms 60ms 199ms 1.0min 0 transport_latency_assumed new_market c 747 457 65ms 14.1s 1.5min 8.3min 0 transport_latency_assumed new_market e 747 150 136ms 14.9s 1.3min 1.7min 0 transport_latency_assumed new_market f 747 110 175ms 18.8s 1.4min 2.5min 0 transport_latency_assumed new_market g 747 45 254ms 14.2s 1.3min 2.0min 0 transport_latency_assumed new_market h 747 329 76ms 14.2s 1.3min 1.7min 0 transport_latency_assumed price_change c 91,132,009 87,609,811 5ms 11ms 97ms 3.4s 0 transport_latency_assumed price_change e 94,827,348 286,072 39ms 54ms 404ms 6.8s 0 transport_latency_assumed price_change f 94,826,680 113,130 46ms 64ms 402ms 7.8s 0 transport_latency_assumed price_change g 94,793,036 15,814 82ms 109ms 773ms 18.0s 0 transport_latency_assumed price_change h 94,873,006 6,922,135 18ms 27ms 167ms 10.4s 0 transport_latency_assumed tick_size_change c 4,316 4,081 5ms 10ms 48ms 136ms 0 transport_latency_assumed tick_size_change e 4,428 not meas. 39ms 44ms 123ms 432ms 0 transport_latency_assumed tick_size_change f 4,428 not meas. 45ms 52ms 136ms 576ms 0 transport_latency_assumed tick_size_change g 4,428 not meas. 80ms 96ms 250ms 483ms 0 transport_latency_assumed tick_size_change h 4,428 347 18ms 21ms 59ms 581ms 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-16/21/2026-09-16T21.parquet sha256sum 2026-09-16T21.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.