Hour audit: 2026-09-17T02
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-17T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T02:00:00.000062043+00:00 · last event 2026-09-17T02:59:59.999984836+00:00
VOLUME 124,878,110 rows · 1,316,079,229 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 123,602,093 · h: 123,439,651 · f: 118,950,915 · c: 118,873,967 · g: 114,916,841 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 811,847 (0.65%) · h: 10,430,788 (8.35%) · f: 531,071 (0.43%) · c: 112,411,404 (90.02%) · g: 693,000 (0.55%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a815e97218d637aa1bbba15dc043864cfa180d984d8624a4b6b332009dc6cfb5
the corpus checksum ledger names this file with the same digest
joined 124,890,173 to merged 124,878,110, minus 12,063 (minus 0.0097%)
boundary drops 12,063 · 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-17T04:01:35Z 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 15,039,648 164,556,295 0-57 83a8796a779b0999d0fcc72d1d6f9fea0525660319a41e530e5a93e4045a8b0d book 1,595,497 91,484,567 58-64 5ff81eb1dac342b52498166e9e3ec2feb60d52c782ea79ccf747ff4a821b6f81 last_trade_price 45,722 2,609,437 65-65 b3fa0f6de74d8434a4fb3562b3b9562c47189bb5ab5e2b1e06ba501d01cb191e market_resolved 2,334 338,748 66-66 334b85670293ccd6bb397620ddca62df4f7b403fed5a029216b75df7272993b3 new_market 1,193 123,965 67-67 ee91ac55d769c3183e2f4116013c363ee3581a3a3ca871158944e55bafed0066 price_change 108,185,500 1,055,248,077 68-480 8173a93e3ecb910b14274525458e39e2490cffb6740af2acf1066af125e072c3 tick_size_change 8,216 297,188 481-481 8207791083a48be31fb2e4d6c02571a43f4dce67438b2c7c73975ca125b95e3e EVENT MIX count share price_change 108,185,500 86.63% best_bid_ask 15,039,648 12.04% book 1,595,497 1.28% last_trade_price 45,722 0.04% tick_size_change 8,216 <0.01% market_resolved 2,334 <0.01% new_market 1,193 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,039,860 15,039,648 212 2,146 FULL book 1,603,970 1,595,497 8,473 133,728 FULL last_trade_price 45,722 45,722 0 179 FULL market_resolved 2,334 2,334 0 106 FULL new_market 1,193 1,193 0 0 FULL price_change 108,188,878 108,185,500 3,378 933 FULL tick_size_change 8,216 8,216 0 151 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 14,440,718 13,771,542 5ms 10ms 94ms 2.6s 0 transport_latency_assumed best_bid_ask e 15,034,405 57,412 39ms 47ms 151ms 4.5s 0 transport_latency_assumed best_bid_ask f 14,439,754 21,628 45ms 56ms 178ms 3.6s 0 transport_latency_assumed best_bid_ask g 13,933,255 2,915 80ms 98ms 287ms 11.9s 0 transport_latency_assumed best_bid_ask h 15,035,531 1,186,151 17ms 25ms 110ms 39.8s 0 transport_latency_assumed book c 591,682 361,016 2.0min 1.4d 36.3d 110.2d 0 book_staleness book e 401,333 201,977 1.8min 9.4h 35.3d 110.2d 0 book_staleness book f 629,016 278,253 1.8min 1.2d 36.3d 110.2d 0 book_staleness book g 939,711 647,122 3.7min 2.4d 36.3d 110.2d 0 book_staleness book h 239,377 107,129 25.7s 52.5min 25.5d 110.2d 0 book_staleness last_trade_price c 43,171 40,046 10ms 48ms 255ms 4.2s 0 transport_latency_assumed last_trade_price e 45,535 482 47ms 105ms 609ms 4.5s 0 transport_latency_assumed last_trade_price f 44,113 227 53ms 117ms 516ms 4.2s 0 transport_latency_assumed last_trade_price g 42,462 41 89ms 194ms 2.4s 12.0s 0 transport_latency_assumed last_trade_price h 45,351 4,926 23ms 64ms 286ms 8.2s 0 transport_latency_assumed market_resolved c 2,128 2,088 5ms 17ms 4.7min 5.3min 0 transport_latency_assumed market_resolved e 2,116 2 111ms 140ms 316ms 657ms 0 transport_latency_assumed market_resolved f 2,036 5 117ms 164ms 359ms 4.7min 0 transport_latency_assumed market_resolved g 2,073 116 203ms 332ms 4.8min 5.8min 0 transport_latency_assumed market_resolved h 2,117 123 35ms 58ms 114ms 4.4s 0 transport_latency_assumed new_market c 806 500 93ms 32.3s 4.4min 9.3min 0 transport_latency_assumed new_market e 790 159 163ms 24.0s 1.1min 5.8min 0 transport_latency_assumed new_market f 790 118 150ms 30.6s 1.0min 16.2min 0 transport_latency_assumed new_market g 798 110 247ms 25.5s 4.7min 10.8min 0 transport_latency_assumed new_market h 790 306 126ms 30.5s 1.1min 24.1min 0 transport_latency_assumed price_change c 103,787,334 98,228,490 5ms 13ms 141ms 3.0s 0 transport_latency_assumed price_change e 108,109,698 551,754 39ms 52ms 254ms 4.5s 0 transport_latency_assumed price_change f 103,827,414 230,814 46ms 61ms 254ms 3.6s 0 transport_latency_assumed price_change g 99,990,742 42,686 80ms 103ms 417ms 12.0s 0 transport_latency_assumed price_change h 108,108,269 9,131,756 17ms 29ms 183ms 40.1s 0 transport_latency_assumed tick_size_change c 8,128 7,722 5ms 10ms 244ms 488ms 0 transport_latency_assumed tick_size_change e 8,216 61 41ms 58ms 408ms 783ms 0 transport_latency_assumed tick_size_change f 7,792 26 46ms 55ms 378ms 549ms 0 transport_latency_assumed tick_size_change g 7,800 10 79ms 97ms 423ms 999ms 0 transport_latency_assumed tick_size_change h 8,216 397 17ms 24ms 444ms 4.9s 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-17/02/2026-09-17T02.parquet sha256sum 2026-09-17T02.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.