Hour audit: 2026-09-28T17
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-28T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T17:00:00.000063660+00:00 · last event 2026-09-28T17:59:59.999893458+00:00
VOLUME 113,221,522 rows · 1,292,914,581 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 111,969,365 · k: 110,571,938 · h: 109,747,537 · g: 107,343,743 · c: 101,661,259 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,887,820 (1.67%) · k: 18,485,336 (16.33%) · h: 5,716,283 (5.05%) · g: 133,495 (0.12%) · c: 86,998,588 (76.84%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 113,221,522 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 be1d3ec6311d6271850be17c140887e84c862ae6b5522e9b653ed982a241a0a7
the corpus checksum ledger names this file with the same digest
joined 113,226,225 to merged 113,221,522, minus 4,703 (minus 0.0042%)
boundary drops 4,703 · 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-28T20:09:09Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 10,822,724 129,545,161 0-41 ec291686f9939de5e1fe002582351170cddfb8411fcdf11f201a9c4153140f69 book 1,534,707 84,346,462 42-47 87040badd8240e815533215c3a1d75d91a16f3e75309693f342c1c4cc5bba8e9 last_trade_price 63,228 3,642,766 48-48 f19348a8ec65b44684553350c01308dad9ed6aacdac713e05890558f44057c02 market_resolved 585 75,178 49-49 afe1718354faae8c4c9b6df91160b91c1aea2a25e55f112fffceacdf81172a04 new_market 5,048 528,466 50-50 ec046b27a4120fc7e73f52513f3dd095b653ebcbac4acf297c2cab642565a229 price_change 100,791,898 1,073,365,339 51-435 b6f83722b5e249bef4502ae15d8910a13fe464afc8d1d1c493fc57998786ea6e tick_size_change 3,332 121,313 436-436 25a610f2494f8d723bf3bc844a20e5b4642992629f109dd3dd2c96b930205094 EVENT MIX count share price_change 100,791,898 89.02% best_bid_ask 10,822,724 9.56% book 1,534,707 1.36% last_trade_price 63,228 0.06% new_market 5,048 <0.01% tick_size_change 3,332 <0.01% market_resolved 585 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,822,965 10,822,724 241 2,980 FULL book 1,534,709 1,534,707 2 159,685 FULL last_trade_price 63,228 63,228 0 342 FULL market_resolved 585 585 0 23 FULL new_market 5,048 5,048 0 0 FULL price_change 100,796,358 100,791,898 4,460 3,574 FULL tick_size_change 3,332 3,332 0 333 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,769,997 8,414,153 6ms 28ms 259ms 10.7s 0 transport_latency_assumed best_bid_ask g 10,529,642 2,693 81ms 199ms 1.6s 39.9s 0 transport_latency_assumed best_bid_ask h 10,581,262 515,014 19ms 37ms 469ms 55.5s 0 transport_latency_assumed best_bid_ask i 10,817,763 170,876 26ms 45ms 268ms 9.2s 0 transport_latency_assumed best_bid_ask k 10,633,278 1,719,988 14ms 32ms 238ms 54.3s 0 transport_latency_assumed book c 1,178,090 1,136,483 1.5h 1.6d 44.2d 121.8d 0 book_staleness book g 447,674 100,035 15.8min 1.6d 37.2d 121.8d 0 book_staleness book h 439,436 92,536 7.4min 1.6d 37.2d 121.8d 0 book_staleness book i 471,194 97,387 10.2min 1.6d 37.2d 121.8d 0 book_staleness book k 457,330 108,266 9.6min 1.6d 37.2d 121.8d 0 book_staleness last_trade_price c 57,095 48,495 7ms 43ms 343ms 2.7s 0 transport_latency_assumed last_trade_price g 54,589 49 135ms 3.9s 18.8s 39.5s 0 transport_latency_assumed last_trade_price h 62,207 3,261 20ms 99ms 733ms 30.0s 0 transport_latency_assumed last_trade_price i 62,743 780 30ms 301ms 2.5s 7.6s 0 transport_latency_assumed last_trade_price k 62,510 10,643 15ms 63ms 372ms 3.2s 0 transport_latency_assumed market_resolved c 497 450 8ms 9.1min 10.9min 11.5min 0 transport_latency_assumed market_resolved g 447 4 90ms 348ms 47.1s 2.4min 0 transport_latency_assumed market_resolved h 448 34 20ms 80ms 20.0s 1.6min 0 transport_latency_assumed market_resolved i 455 27 29ms 133ms 47.4s 55.0s 0 transport_latency_assumed market_resolved k 454 70 16ms 57ms 17.5s 1.6min 0 transport_latency_assumed new_market c 3,869 1,873 99ms 4.2min 5.8min 34.9d 0 transport_latency_assumed new_market g 3,456 360 302ms 35.1s 2.5min 34.9d 0 transport_latency_assumed new_market h 3,456 983 123ms 29.9s 2.7min 34.9d 0 transport_latency_assumed new_market i 3,456 1,018 107ms 25.6s 2.5min 34.9d 0 transport_latency_assumed new_market k 3,456 814 139ms 26.4s 2.4min 34.9d 0 transport_latency_assumed price_change c 90,649,619 77,395,349 6ms 33ms 281ms 11.3s 0 transport_latency_assumed price_change g 96,304,683 30,354 84ms 393ms 10.7s 40.1s 0 transport_latency_assumed price_change h 98,657,480 5,104,152 19ms 50ms 569ms 55.9s 0 transport_latency_assumed price_change i 100,610,422 1,617,700 27ms 68ms 688ms 9.6s 0 transport_latency_assumed price_change k 99,411,618 16,644,343 14ms 40ms 275ms 54.7s 0 transport_latency_assumed tick_size_change c 2,092 1,785 6ms 26ms 159ms 378ms 0 transport_latency_assumed tick_size_change g 3,252 not meas. 80ms 123ms 412ms 1.4s 0 transport_latency_assumed tick_size_change h 3,248 303 18ms 27ms 124ms 1.1s 0 transport_latency_assumed tick_size_change i 3,332 32 25ms 32ms 111ms 270ms 0 transport_latency_assumed tick_size_change k 3,292 1,212 14ms 23ms 118ms 284ms 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-28/17/2026-09-28T17.parquet sha256sum 2026-09-28T17.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.