Hour audit: 2026-09-05T14
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-05T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T14:00:00.041861430+00:00 · last event 2026-09-05T14:59:59.999989801+00:00
VOLUME 129,750,015 rows · 1,419,072,328 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 126,246,926 · e: 126,234,234 · f: 125,788,735 · g: 125,267,843 · c: 83,167,844 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 21,207 (0.02%) · e: 309,635 (0.24%) · f: 750,521 (0.58%) · g: 125,227,328 (96.51%) · c: 3,441,324 (2.65%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 129,750,015 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c9270f191d4e88781274f834fb4912753209110d919378b2214d534f0f443714
the corpus checksum ledger names this file with the same digest
joined 129,799,741 to merged 129,750,015, minus 49,726 (minus 0.0383%)
boundary drops 49,726 · 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-05T20:23:58Z 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,697,932 147,094,236 0-48 b5dbf24bdf40decc786cb85bf712a53ac5ce3a112b0ac7cea95fe5cfc58adf39 book 3,613,155 116,615,514 49-62 d1133047d53ea406201cae90089aa4bbaea57b7401ff99bb84b8ecea0f9ce1ea last_trade_price 69,219 4,051,159 63-63 1d171fe4e0ee122c2336b0d7749d9583f9e3c876a659862984fb15e8898a1181 market_resolved 4,146 282,686 64-64 5c92ff96e896a1559ae3319e08ede8f928df4fa7d88aa5919302a1919d7b3686 new_market 5,531 442,548 65-65 fc87f15433b81cb40b3ed34b3bee861b96d090d9c9066000fbc4989d1e0557c4 price_change 113,348,008 1,148,678,884 66-498 94d838c9853f9a39fb71989a7dbbad41c99a04387716285afd4941f1ba9d983e tick_size_change 12,024 432,721 499-499 78666945e1c8993546122ab45e5efd39a84c3ec3de728dac5664a8dcd969c3fd EVENT MIX count share price_change 113,348,008 87.36% best_bid_ask 12,697,932 9.79% book 3,613,155 2.78% last_trade_price 69,219 0.05% tick_size_change 12,024 <0.01% new_market 5,531 <0.01% market_resolved 4,146 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,701,098 12,697,932 3,166 13,379 FULL book 3,613,655 3,613,155 500 186,683 FULL last_trade_price 69,390 69,219 171 1,173 FULL market_resolved 4,146 4,146 0 52 FULL new_market 5,600 5,531 69 89 FULL price_change 113,393,828 113,348,008 45,820 9,539 FULL tick_size_change 12,024 12,024 0 1,024 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,088,474 506 5ms 12ms 195ms 9.2s 0 transport_latency_assumed best_bid_ask e 12,695,074 14,448 39ms 50ms 314ms 16.3s 0 transport_latency_assumed best_bid_ask f 12,674,350 38,303 47ms 81ms 569ms 26.0s 0 transport_latency_assumed best_bid_ask g 12,645,579 12,643,263 84ms 183ms 2.6s 48.0s 0 transport_latency_assumed best_bid_ask h 12,697,187 1,412 18ms 33ms 529ms 1.1min 0 transport_latency_assumed book c 3,537,660 3,431,631 3.4min 15.0h 34.1d 98.7d 0 book_staleness book e 146,853 2,867 42ms 169ms 4.2s 28.2d 0 book_staleness book f 152,170 8,060 49ms 1.3s 43.2min 10.0d 0 book_staleness book g 165,906 165,514 89ms 32.0s 12.2h 80.2d 0 book_staleness book h 150,874 5,083 22ms 168ms 35.6min 98.7d 0 book_staleness last_trade_price c 40,804 1 11ms 50ms 381ms 5.0s 0 transport_latency_assumed last_trade_price e 68,996 725 46ms 128ms 1.1s 16.2s 0 transport_latency_assumed last_trade_price f 67,724 1,545 53ms 211ms 8.3s 25.4s 0 transport_latency_assumed last_trade_price g 67,046 66,877 93ms 341ms 15.0s 40.0s 0 transport_latency_assumed last_trade_price h 69,196 71 24ms 79ms 1.6s 57.0s 0 transport_latency_assumed market_resolved c 3,688 2,555 7.5min 17.0min 20.5min 21.0min 0 transport_latency_assumed market_resolved e 1,591 not meas. 41ms 187ms 51.7s 57.5s 0 transport_latency_assumed market_resolved f 1,590 not meas. 47ms 129ms 55.7s 1.0min 0 transport_latency_assumed market_resolved g 1,591 1,591 85ms 281ms 46.5s 52.9s 0 transport_latency_assumed market_resolved h 1,591 not meas. 18ms 78ms 44.7s 50.6s 0 transport_latency_assumed new_market c 4,620 1,419 391ms 7.9min 17.1min 17.3min 0 transport_latency_assumed new_market e 2,633 537 211ms 1.3min 4.9min 5.5min 0 transport_latency_assumed new_market f 2,633 753 225ms 1.4min 4.8min 5.2min 0 transport_latency_assumed new_market g 2,633 2,633 365ms 1.5min 4.9min 15.4min 0 transport_latency_assumed new_market h 2,633 189 180ms 1.4min 4.9min 5.4min 0 transport_latency_assumed price_change c 71,484,622 5,212 5ms 13ms 214ms 10.2s 0 transport_latency_assumed price_change e 113,307,063 291,058 40ms 60ms 363ms 16.7s 0 transport_latency_assumed price_change f 112,878,244 701,792 47ms 99ms 1.2s 26.0s 0 transport_latency_assumed price_change g 112,373,132 112,335,494 84ms 214ms 6.5s 48.1s 0 transport_latency_assumed price_change h 113,313,421 14,452 18ms 36ms 592ms 1.1min 0 transport_latency_assumed tick_size_change c 7,976 not meas. 5ms 16ms 158ms 377ms 0 transport_latency_assumed tick_size_change e 12,024 not meas. 40ms 112ms 419ms 800ms 0 transport_latency_assumed tick_size_change f 12,024 68 48ms 185ms 501ms 6.3s 0 transport_latency_assumed tick_size_change g 11,956 11,956 87ms 420ms 1.8s 13.5s 0 transport_latency_assumed tick_size_change h 12,024 not meas. 18ms 51ms 908ms 15.0s 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-05/14/2026-09-05T14.parquet sha256sum 2026-09-05T14.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.