Hour audit: 2026-09-14T21
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-14T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T21:00:00.000065808+00:00 · last event 2026-09-14T21:59:59.999548184+00:00
VOLUME 108,226,450 rows · 1,146,841,549 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 107,322,990 · h: 107,123,470 · f: 107,116,048 · e: 107,102,762 · c: 99,210,917 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 249,298 (0.23%) · h: 12,120,038 (11.20%) · f: 364,976 (0.34%) · e: 656,674 (0.61%) · c: 94,835,464 (87.63%) (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 108,226,450 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 df3dfb50bc932abda0f1f7bcd168d13f12ce49faa37d92d278adabf70f907948
the corpus checksum ledger names this file with the same digest
joined 108,230,085 to merged 108,226,450, minus 3,635 (minus 0.0034%)
boundary drops 3,635 · 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-14T22:58:21Z 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,277,521 127,073,477 0-43 d2e7a570f06fc4f71c03cdea0d861706cf5fa6f675f5ef74d69c9ec4b4a9fda7 book 1,232,293 80,507,832 44-48 293ebe6d07c5a6756ee4d2cc24681de1c0dec882ac4a4f731d6e3398c4b1fb8c last_trade_price 50,316 2,924,313 49-49 f7d109516ecc462eaa3a7bd2e2dcffbf592fdebaff80ca8719103a0db8d2b36c market_resolved 1,682 270,305 50-50 d13c2f73929720b6a4d755ca6639c1c87bf9731f22dcab3bb7fa81dd2a6787e8 new_market 1,894 197,677 51-51 448e7937219f33ef75f960661cfb5ffaf97f8ce8cb61ceec7d1def7d6f76812c price_change 95,659,812 934,528,186 52-416 6844c9e9af421a5ce74adb6227222a55bde50592f8cfe6c1b791c5752a7da986 tick_size_change 2,932 107,157 417-417 906a59580765c770441705a95852ff21289c9874b503076223d5d907b5c6b564 EVENT MIX count share price_change 95,659,812 88.39% best_bid_ask 11,277,521 10.42% book 1,232,293 1.14% last_trade_price 50,316 0.05% tick_size_change 2,932 <0.01% new_market 1,894 <0.01% market_resolved 1,682 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,277,898 11,277,521 377 1,544 FULL book 1,232,731 1,232,293 438 168,312 FULL last_trade_price 50,316 50,316 0 204 FULL market_resolved 1,682 1,682 0 125 FULL new_market 1,904 1,894 10 9 FULL price_change 95,662,622 95,659,812 2,810 926 FULL tick_size_change 2,932 2,932 0 54 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,359,002 9,927,564 5ms 11ms 121ms 5.8s 0 transport_latency_assumed best_bid_ask e 11,274,307 60,754 44ms 60ms 231ms 10.6s 0 transport_latency_assumed best_bid_ask f 11,273,698 30,018 48ms 61ms 244ms 10.3s 0 transport_latency_assumed best_bid_ask g 11,266,649 1,944 79ms 109ms 494ms 19.0s 0 transport_latency_assumed best_bid_ask h 11,274,440 1,257,241 18ms 25ms 162ms 51.5s 0 transport_latency_assumed book c 916,254 831,673 8.9min 2.3d 36.4d 108.0d 0 book_staleness book e 189,321 41,465 274ms 6.8h 23.3d 108.0d 0 book_staleness book f 201,819 46,593 665ms 9.2h 23.3d 108.0d 0 book_staleness book g 510,632 225,852 3.7min 1.5d 34.1d 108.0d 0 book_staleness book h 249,207 86,710 18.3s 19.1h 23.3d 108.0d 0 book_staleness last_trade_price c 44,977 42,873 10ms 49ms 232ms 4.8s 0 transport_latency_assumed last_trade_price e 50,217 500 60ms 255ms 2.0s 10.6s 0 transport_latency_assumed last_trade_price f 50,028 216 62ms 253ms 1.8s 10.3s 0 transport_latency_assumed last_trade_price g 49,909 32 101ms 684ms 8.1s 19.1s 0 transport_latency_assumed last_trade_price h 50,083 6,695 24ms 87ms 386ms 7.0s 0 transport_latency_assumed market_resolved c 1,472 1,424 5ms 15ms 3.9min 5.3min 0 transport_latency_assumed market_resolved e 1,592 12 56ms 217ms 56.9s 1.0min 0 transport_latency_assumed market_resolved f 1,592 13 52ms 211ms 485ms 914ms 0 transport_latency_assumed market_resolved g 1,591 3 92ms 358ms 787ms 1.6s 0 transport_latency_assumed market_resolved h 1,592 230 22ms 86ms 56.0s 59.4s 0 transport_latency_assumed new_market c 1,297 819 81ms 14.6s 1.8min 7.9min 0 transport_latency_assumed new_market e 1,278 199 193ms 15.7s 1.0min 1.5min 0 transport_latency_assumed new_market f 1,285 204 218ms 18.7s 1.2min 5.5min 0 transport_latency_assumed new_market g 1,279 115 313ms 16.4s 34.2s 1.5min 0 transport_latency_assumed new_market h 1,280 557 121ms 16.7s 45.5s 4.0min 0 transport_latency_assumed price_change c 87,885,199 84,028,429 5ms 12ms 138ms 5.8s 0 transport_latency_assumed price_change e 95,583,115 553,742 45ms 72ms 464ms 10.6s 0 transport_latency_assumed price_change f 95,584,694 287,932 48ms 73ms 464ms 10.3s 0 transport_latency_assumed price_change g 95,489,998 21,352 80ms 145ms 1.3s 19.2s 0 transport_latency_assumed price_change h 95,543,936 10,768,357 18ms 31ms 215ms 52.5s 0 transport_latency_assumed tick_size_change c 2,716 2,682 5ms 8ms 31ms 79ms 0 transport_latency_assumed tick_size_change e 2,932 2 43ms 56ms 107ms 2.5s 0 transport_latency_assumed tick_size_change f 2,932 not meas. 48ms 52ms 121ms 435ms 0 transport_latency_assumed tick_size_change g 2,932 not meas. 79ms 92ms 198ms 4.0s 0 transport_latency_assumed tick_size_change h 2,932 248 18ms 22ms 70ms 1.6s 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-14/21/2026-09-14T21.parquet sha256sum 2026-09-14T21.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.