Hour audit: 2026-09-15T08
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-15T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T08:00:00.000425365+00:00 · last event 2026-09-15T08:59:59.999795170+00:00
VOLUME 114,474,867 rows · 1,212,099,647 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,679,001 · e: 113,650,403 · g: 113,614,800 · f: 113,585,468 · c: 105,841,709 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,415,560 (11.72%) · e: 485,792 (0.42%) · g: 142,749 (0.12%) · f: 255,419 (0.22%) · c: 100,175,347 (87.51%) (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 114,474,867 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 566ef5cd13115e0d676126a7c48eb9edb80ec7ebb68762433cc061a425ea9ed6
the corpus checksum ledger names this file with the same digest
joined 114,478,243 to merged 114,474,867, minus 3,376 (minus 0.0029%)
boundary drops 3,376 · 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-15T09:59: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,687,965 131,464,798 0-44 e1a535a9d8180472c2f36562525dbd8933cc56757894d93266607cf5dcbdc792 book 825,309 65,081,672 45-48 c22ce4d30cd8e9ce05e6ded6624bf5e4699a8144cbeb814b92d7a1561007db70 last_trade_price 52,756 3,023,185 49-49 27d5cbc24ec6ac383c4abdf8e64a1b2b8c0f075864a8c589ab92c22ee68c9e15 market_resolved 1,093 150,676 50-50 a3113c30ddd8e3d3d9af17a4d83b40dca99ecc8361812b411adfe76d48ba903d new_market 936 98,927 51-51 dd42b0546795841f2a1becff5475493032ed53a3d5db7361aa33c577935f471b price_change 101,904,304 1,010,883,658 52-440 0c311ecf768b88c0214359b6f1782315333ae545fef9304f884c6856ddbebbf5 tick_size_change 2,504 92,869 441-441 7c8ab1770e4c56c93c82916a83913a8f8fae30f578ea5737a17c97bfec274ea6 EVENT MIX count share price_change 101,904,304 89.02% best_bid_ask 11,687,965 10.21% book 825,309 0.72% last_trade_price 52,756 0.05% tick_size_change 2,504 <0.01% market_resolved 1,093 <0.01% new_market 936 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,688,275 11,687,965 310 769 FULL book 825,435 825,309 126 169,390 FULL last_trade_price 52,756 52,756 0 125 FULL market_resolved 1,093 1,093 0 45 FULL new_market 936 936 0 0 FULL price_change 101,907,244 101,904,304 2,940 480 FULL tick_size_change 2,504 2,504 0 47 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,826,211 10,296,186 5ms 12ms 106ms 7.4s 0 transport_latency_assumed best_bid_ask e 11,685,786 39,864 44ms 51ms 208ms 10.9s 0 transport_latency_assumed best_bid_ask f 11,686,040 18,487 49ms 58ms 221ms 10.0s 0 transport_latency_assumed best_bid_ask g 11,682,530 6,201 82ms 121ms 408ms 22.5s 0 transport_latency_assumed best_bid_ask h 11,686,527 1,327,227 17ms 25ms 133ms 7.5s 0 transport_latency_assumed book c 795,198 777,106 6.0min 2.2d 34.6d 108.4d 0 book_staleness book e 113,222 3,214 46ms 220ms 23.7min 89.9d 0 book_staleness book f 116,496 4,710 52ms 508ms 6.3h 89.9d 0 book_staleness book g 147,968 26,267 99ms 29.2min 9.8d 108.4d 0 book_staleness book h 112,147 14,012 21ms 83ms 4.1min 89.9d 0 book_staleness last_trade_price c 49,001 46,066 11ms 49ms 234ms 4.9s 0 transport_latency_assumed last_trade_price e 52,604 361 52ms 173ms 4.5s 10.9s 0 transport_latency_assumed last_trade_price f 52,601 231 58ms 207ms 4.1s 10.0s 0 transport_latency_assumed last_trade_price g 52,243 87 95ms 343ms 5.1s 22.3s 0 transport_latency_assumed last_trade_price h 52,548 6,011 24ms 86ms 372ms 4.9s 0 transport_latency_assumed market_resolved c 936 895 5ms 4.4min 5.4min 5.4min 0 transport_latency_assumed market_resolved e 935 4 46ms 152ms 28.7s 57.0s 0 transport_latency_assumed market_resolved f 935 3 51ms 145ms 450ms 52.9s 0 transport_latency_assumed market_resolved g 935 not meas. 87ms 268ms 624ms 48.5s 0 transport_latency_assumed market_resolved h 935 191 21ms 66ms 28.5s 57.0s 0 transport_latency_assumed new_market c 636 447 46ms 14.6s 1.0min 4.2min 0 transport_latency_assumed new_market e 636 97 147ms 475ms 35.5s 1.1min 0 transport_latency_assumed new_market f 636 110 178ms 23.5s 39.8s 1.1min 0 transport_latency_assumed new_market g 636 92 264ms 27.9s 41.2s 1.2min 0 transport_latency_assumed new_market h 636 190 72ms 20.7s 36.3s 38.7s 0 transport_latency_assumed price_change c 94,167,407 89,052,547 5ms 14ms 212ms 10.6s 0 transport_latency_assumed price_change e 101,794,716 442,244 44ms 61ms 551ms 11.8s 0 transport_latency_assumed price_change f 101,726,256 231,878 49ms 68ms 542ms 10.0s 0 transport_latency_assumed price_change g 101,727,988 110,102 83ms 147ms 829ms 22.5s 0 transport_latency_assumed price_change h 101,823,704 12,067,533 17ms 31ms 301ms 8.0s 0 transport_latency_assumed tick_size_change c 2,320 2,100 5ms 22ms 259ms 299ms 0 transport_latency_assumed tick_size_change e 2,504 8 44ms 49ms 124ms 5.9s 0 transport_latency_assumed tick_size_change f 2,504 not meas. 49ms 54ms 128ms 5.6s 0 transport_latency_assumed tick_size_change g 2,500 not meas. 80ms 111ms 485ms 4.7s 0 transport_latency_assumed tick_size_change h 2,504 396 17ms 24ms 68ms 216ms 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/08/2026-09-15T08.parquet sha256sum 2026-09-15T08.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.