Hour audit: 2026-10-02T11
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-10-02T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T11:00:00.000061794+00:00 · last event 2026-10-02T11:59:59.999937509+00:00
VOLUME 108,554,895 rows · 1,125,211,132 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 108,491,371 · i: 108,491,214 · m: 108,484,758 · k: 108,477,436 · g: 108,365,116 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,066,737 (0.98%) · i: 306,015 (0.28%) · m: 102,442,903 (94.37%) · k: 4,715,158 (4.34%) · g: 24,082 (0.02%) (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,554,895 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b1295cda26ea76eb413f0929747b66cbc91f7f0abb6e6e317177e6afdfc4f8a5
the corpus checksum ledger names this file with the same digest
joined 108,556,757 to merged 108,554,895, minus 1,862 (minus 0.0017%)
boundary drops 1,862 · 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-10-02T13:45:17Z as ghikm
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 9,499,458 110,622,234 0-36 fc04d7469dfbdd881f1f95cb93c3210c82b0cfbd8451ebbd860c101df1511eb7 book 152,564 16,842,479 37-37 bdecc25c4561039c37d74a12dafa6898410d7162673aef74a185dd9354f5097c last_trade_price 50,004 2,873,682 38-38 2d1fd54c80d6779dace49b68491a85fbd6a5efbcd8dc45ee1a889202052c2fb7 market_resolved 575 95,547 39-39 364ed60f9967204f2081d08aefb173aeb174d915c7058db576b593b80ed9075e new_market 1,116 113,207 40-40 d2abb01a59290e322522ad9269dd921312adc7650fddec53b3775ce40f2ef811 price_change 98,848,378 993,319,504 41-418 44683606b73cf9d57898ef5fb9608012ae987209931ee0b90edd2019022bade4 tick_size_change 2,800 103,572 419-419 8b47271f8871e80617d00253360c5a8db152a2d2a4cd805a996f312058ea680d EVENT MIX count share price_change 98,848,378 91.06% best_bid_ask 9,499,458 8.75% book 152,564 0.14% last_trade_price 50,004 0.05% tick_size_change 2,800 <0.01% new_market 1,116 <0.01% market_resolved 575 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,499,668 9,499,458 210 96 FULL book 152,564 152,564 0 23,321 FULL last_trade_price 50,004 50,004 0 1 FULL market_resolved 575 575 0 0 FULL new_market 1,116 1,116 0 0 FULL price_change 98,850,030 98,848,378 1,652 107 FULL tick_size_change 2,800 2,800 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,497,141 559 77ms 102ms 506ms 17.3s 0 transport_latency_assumed best_bid_ask h 9,498,456 75,365 18ms 32ms 220ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,498,754 24,044 22ms 42ms 163ms 30.3s 0 transport_latency_assumed best_bid_ask k 9,498,782 393,811 13ms 22ms 161ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,499,246 9,005,679 5ms 10ms 82ms 5.4s 0 transport_latency_assumed book g 116,133 15,693 91ms 3.1min 6.1d 125.6d 0 book_staleness book h 120,667 20,602 27ms 22.1min 13.1d 117.8d 0 book_staleness book i 102,878 2,369 25ms 98ms 16.2min 107.1d 0 book_staleness book k 109,192 13,375 16ms 162ms 13.0h 107.1d 0 book_staleness book m 108,822 100,525 7ms 66ms 23.7h 40.9d 0 book_staleness last_trade_price g 49,675 21 87ms 1.2s 7.3s 17.0s 0 transport_latency_assumed last_trade_price h 49,985 600 20ms 43ms 496ms 47.9s 0 transport_latency_assumed last_trade_price i 49,987 221 25ms 69ms 627ms 29.9s 0 transport_latency_assumed last_trade_price k 49,993 2,656 14ms 28ms 326ms 1.0min 0 transport_latency_assumed last_trade_price m 49,995 46,506 6ms 12ms 135ms 2.9s 0 transport_latency_assumed market_resolved g 570 not meas. 79ms 230ms 52.7s 56.7s 0 transport_latency_assumed market_resolved h 570 3 19ms 49ms 44.4s 47.6s 0 transport_latency_assumed market_resolved i 570 2 24ms 65ms 37.1s 40.9s 0 transport_latency_assumed market_resolved k 570 25 13ms 37ms 46.8s 54.6s 0 transport_latency_assumed market_resolved m 570 545 6ms 12ms 31.8s 35.5s 0 transport_latency_assumed new_market g 727 89 487ms 21.9s 31.2s 1.7min 0 transport_latency_assumed new_market h 727 256 238ms 19.7s 47.3s 1.8min 0 transport_latency_assumed new_market i 727 114 289ms 20.7s 28.3s 1.8min 0 transport_latency_assumed new_market k 727 186 372ms 19.9s 28.9s 1.7min 0 transport_latency_assumed new_market m 727 471 65ms 19.9s 26.5s 1.9min 0 transport_latency_assumed price_change g 98,698,070 7,720 78ms 157ms 3.4s 17.4s 0 transport_latency_assumed price_change h 98,818,166 969,886 19ms 33ms 362ms 1.1min 0 transport_latency_assumed price_change i 98,835,498 279,258 22ms 43ms 333ms 30.3s 0 transport_latency_assumed price_change k 98,815,372 4,304,988 13ms 25ms 237ms 1.0min 0 transport_latency_assumed price_change m 98,822,598 93,286,526 5ms 10ms 110ms 5.4s 0 transport_latency_assumed tick_size_change g 2,800 not meas. 77ms 94ms 193ms 5.0s 0 transport_latency_assumed tick_size_change h 2,800 25 19ms 32ms 56ms 122ms 0 transport_latency_assumed tick_size_change i 2,800 7 22ms 41ms 58ms 1.3s 0 transport_latency_assumed tick_size_change k 2,800 117 13ms 21ms 118ms 127ms 0 transport_latency_assumed tick_size_change m 2,800 2,651 5ms 9ms 39ms 231ms 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-10-02/11/2026-10-02T11.parquet sha256sum 2026-10-02T11.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.