Hour audit: 2026-10-09T18
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-09T18 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 142,544,633 rows · 1,646,867,797 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 142,473,446 · m: 142,322,742 · h: 142,297,390 · i: 142,207,344 · n: 141,834,930 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 70,796,634 (49.67%) · m: 68,939,498 (48.36%) · h: 1,133,373 (0.80%) · i: 1,385,999 (0.97%) · n: 289,129 (0.20%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 3db713d7262b03baea38e7de44097326535d552eb82b8a1b36618f6e0c204895
no line in the corpus checksum ledger names this file
joined 142,546,605 to merged 142,544,633, minus 1,972 (minus 0.0014%)
boundary drops 1,972 · 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-10T06:32:54Z as himno
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 6/8 pass, 1 finding, 1 not evaluated
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
FINDING the checksum ledger does not name this file
SKIPPED the hour's minutes have not been measured
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 13,002,610 165,349,147 0-49 2c5dabf8836c6f65e98d400951d35a2385ba4dae56322c66b9a589afdb22f37a book 218,754 23,764,526 50-50 d2e14b02ed6e813051f134d8c0733d3ffcc66331e527317a5a3825d9fce57333 last_trade_price 62,926 3,693,988 51-51 b76b9dd1c633dc3321c01439885a18dc840fe891487c186b24a358f6628d29c5 market_resolved 1,659 263,481 52-52 56276cd041dc41a2b99a54d8eb13c1e0c22775f0f9869c76eb8d5319e03ad492 new_market 5,146 487,662 53-53 eb17c497661a8ed106a1f46a1a2014f156df40b20a635f825cdd6617c0cfdb3a price_change 129,244,610 1,451,367,611 54-547 eddc9ed046f6955efe10e0aa963868e933eeda5832aa745db235422c258720b5 tick_size_change 8,928 319,638 548-548 831a604b52e8a165d2c145003f45b58e6ed8ed60e1aeb5b814c998d47a4455c6 EVENT MIX count share price_change 129,244,610 90.67% best_bid_ask 13,002,610 9.12% book 218,754 0.15% last_trade_price 62,926 0.04% tick_size_change 8,928 <0.01% new_market 5,146 <0.01% market_resolved 1,659 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,002,793 13,002,610 183 347 FULL book 218,778 218,754 24 37,994 FULL last_trade_price 62,927 62,926 1 2 FULL market_resolved 1,659 1,659 0 0 FULL new_market 5,146 5,146 0 0 FULL price_change 129,246,374 129,244,610 1,764 1,705 FULL tick_size_change 8,928 8,928 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,998,008 99,352 19ms 44ms 1.5s 1.6min 0 transport_latency_assumed best_bid_ask i 12,999,566 125,415 21ms 40ms 245ms 13.2s 0 transport_latency_assumed best_bid_ask m 13,001,351 6,372,461 6ms 18ms 223ms 19.0s 0 transport_latency_assumed best_bid_ask n 12,993,393 25,702 45ms 77ms 483ms 31.3s 0 transport_latency_assumed best_bid_ask o 13,000,897 6,379,680 6ms 20ms 256ms 48.1s 0 transport_latency_assumed book h 148,872 19,583 27ms 56.8s 6.2d 114.8d 0 book_staleness book i 134,987 7,173 26ms 963ms 3.0h 114.3d 0 book_staleness book m 139,637 72,767 8ms 299ms 12.7h 114.3d 0 book_staleness book n 139,037 11,795 53ms 5.0s 1.6d 114.4d 0 book_staleness book o 176,313 107,436 10ms 1.9h 30.4d 114.8d 0 book_staleness last_trade_price h 62,774 459 21ms 177ms 4.1s 59.1s 0 transport_latency_assumed last_trade_price i 62,645 353 26ms 328ms 2.3s 13.2s 0 transport_latency_assumed last_trade_price m 62,834 31,288 7ms 24ms 250ms 4.6s 0 transport_latency_assumed last_trade_price n 61,298 84 50ms 716ms 9.5s 24.9s 0 transport_latency_assumed last_trade_price o 62,888 30,742 7ms 23ms 289ms 6.4s 0 transport_latency_assumed market_resolved h 1,573 14 25ms 3.9s 50.6s 1.4min 0 transport_latency_assumed market_resolved i 1,573 218 30ms 16.6s 47.9s 54.9s 0 transport_latency_assumed market_resolved m 1,573 714 6ms 22.6s 54.2s 54.9s 0 transport_latency_assumed market_resolved n 1,573 4 51ms 846ms 49.9s 54.2s 0 transport_latency_assumed market_resolved o 1,573 709 6ms 174ms 47.6s 55.7s 0 transport_latency_assumed new_market h 3,111 735 200ms 35.4s 1.8min 2.3min 0 transport_latency_assumed new_market i 3,111 838 133ms 39.0s 2.0min 2.5min 0 transport_latency_assumed new_market m 3,111 2,195 45ms 39.0s 1.9min 2.4min 0 transport_latency_assumed new_market n 3,111 494 238ms 39.3s 1.9min 2.5min 0 transport_latency_assumed new_market o 3,111 884 116ms 37.7s 1.8min 2.4min 0 transport_latency_assumed price_change h 129,074,124 1,013,187 19ms 55ms 1.9s 1.9min 0 transport_latency_assumed price_change i 128,996,534 1,251,954 22ms 51ms 689ms 13.2s 0 transport_latency_assumed price_change m 129,105,308 62,455,641 6ms 20ms 241ms 19.0s 0 transport_latency_assumed price_change n 128,627,590 251,038 46ms 110ms 1.9s 33.8s 0 transport_latency_assumed price_change o 129,219,736 64,272,790 6ms 21ms 283ms 49.2s 0 transport_latency_assumed tick_size_change h 8,928 43 19ms 33ms 683ms 8.0s 0 transport_latency_assumed tick_size_change i 8,928 48 22ms 40ms 161ms 397ms 0 transport_latency_assumed tick_size_change m 8,928 4,432 6ms 14ms 110ms 691ms 0 transport_latency_assumed tick_size_change n 8,928 12 45ms 62ms 299ms 1.0s 0 transport_latency_assumed tick_size_change o 8,928 4,393 6ms 15ms 99ms 1.7s 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-09/18/2026-10-09T18.parquet sha256sum 2026-10-09T18.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.