Hour audit: 2026-10-10T06
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-10T06 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 125,799,336 rows · 1,472,819,467 bytes (1.37 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 124,749,046 · o: 124,532,721 · m: 124,519,425 · h: 124,479,331 · n: 119,496,086 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 672,315 (0.53%) · o: 60,801,767 (48.33%) · m: 62,909,105 (50.01%) · h: 762,930 (0.61%) · n: 653,219 (0.52%) (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 125,799,336 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 26a42121f9d095a57d9083c755668c1a03069d6e909274960569962a013ae041
no line in the corpus checksum ledger names this file
joined 125,806,651 to merged 125,799,336, minus 7,315 (minus 0.0058%)
boundary drops 7,315 · 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-10T13:00:24Z 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 12,816,055 157,997,691 0-48 71ec09c830bf44a2d9fc1cab9f4886fbf1e3c6dd2cc503f7a47d2d175ad3be2b book 1,588,759 108,240,606 49-55 91e389b5687d93e136eafeb852cf684bb860a69ee7cda012022be01d3f96eaf8 last_trade_price 39,178 2,391,297 56-56 394be1e0ed6bb6a4fc7690b8b2917c27fdec50474dcd561370548aede7e4c6c7 market_resolved 1,073 151,540 57-57 d1bcf24283607f0f2fda18f6a9d336a33759f533d45f9ec5734977e68907c68e new_market 529 54,823 58-58 54180c7d10423394bdee3d33884c93f444e003d113008b9e784d19ba27778d2e price_change 111,349,198 1,202,383,048 59-483 4040facdb97e236ee32184d833d553b88e4e4c357c02d4a2ef1c103baa51fcdd tick_size_change 4,544 167,614 484-484 8a6c95920c5ff3c7575063ca611c9db653e7d90d0af7414b4e76154f3ec18537 EVENT MIX count share price_change 111,349,198 88.51% best_bid_ask 12,816,055 10.19% book 1,588,759 1.26% last_trade_price 39,178 0.03% tick_size_change 4,544 <0.01% market_resolved 1,073 <0.01% new_market 529 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,816,202 12,816,055 147 1,556 FULL book 1,594,507 1,588,759 5,748 240,680 FULL last_trade_price 39,178 39,178 0 125 FULL market_resolved 1,073 1,073 0 6 FULL new_market 529 529 0 0 FULL price_change 111,350,618 111,349,198 1,420 328 FULL tick_size_change 4,544 4,544 0 70 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,812,784 42,042 17ms 24ms 200ms 1.6min 0 transport_latency_assumed best_bid_ask i 12,811,629 25,263 21ms 39ms 69ms 3.9s 0 transport_latency_assumed best_bid_ask m 12,814,658 6,442,023 4ms 9ms 55ms 14.0s 0 transport_latency_assumed best_bid_ask n 12,249,639 3,625 43ms 49ms 127ms 4.1s 0 transport_latency_assumed best_bid_ask o 12,814,448 6,303,102 4ms 9ms 51ms 4.1s 0 transport_latency_assumed book h 374,266 190,383 3.6min 2.0d 48.7d 133.4d 0 book_staleness book i 677,214 341,436 5.6min 2.1d 48.7d 133.3d 0 book_staleness book m 384,995 226,912 3.6min 2.0d 48.7d 133.4d 0 book_staleness book n 912,823 602,058 5.1min 2.1d 48.7d 133.3d 0 book_staleness book o 391,149 227,970 3.6min 2.0d 48.7d 133.4d 0 book_staleness last_trade_price h 39,110 246 19ms 47ms 526ms 56.7s 0 transport_latency_assumed last_trade_price i 38,889 220 22ms 41ms 378ms 1.3s 0 transport_latency_assumed last_trade_price m 39,111 19,053 5ms 13ms 143ms 1.7s 0 transport_latency_assumed last_trade_price n 37,204 49 45ms 101ms 559ms 2.9s 0 transport_latency_assumed last_trade_price o 39,058 19,610 5ms 13ms 138ms 1.3s 0 transport_latency_assumed market_resolved h 947 31 20ms 93ms 54.0s 56.7s 0 transport_latency_assumed market_resolved i 946 70 23ms 17.5s 47.5s 1.8min 0 transport_latency_assumed market_resolved m 947 467 5ms 17.6s 47.4s 48.9s 0 transport_latency_assumed market_resolved n 950 88 49ms 55.6s 4.7min 6.9min 0 transport_latency_assumed market_resolved o 942 417 5ms 29.0s 54.7s 58.3s 0 transport_latency_assumed new_market h 358 118 63ms 664ms 35.6s 1.6min 0 transport_latency_assumed new_market i 358 74 67ms 12.0s 35.4s 1.3min 0 transport_latency_assumed new_market m 358 114 53ms 13.0s 46.6s 1.4min 0 transport_latency_assumed new_market n 372 45 159ms 10.8s 2.0min 6.7min 0 transport_latency_assumed new_market o 358 178 53ms 11.5s 36.6s 1.7min 0 transport_latency_assumed price_change h 111,247,322 530,102 18ms 26ms 252ms 1.6min 0 transport_latency_assumed price_change i 111,215,470 305,252 21ms 40ms 139ms 4.0s 0 transport_latency_assumed price_change m 111,274,812 56,218,250 4ms 10ms 97ms 14.2s 0 transport_latency_assumed price_change n 106,290,830 47,354 43ms 52ms 250ms 4.7s 0 transport_latency_assumed price_change o 111,282,222 54,248,240 4ms 10ms 88ms 5.2s 0 transport_latency_assumed tick_size_change h 4,544 8 18ms 27ms 78ms 818ms 0 transport_latency_assumed tick_size_change i 4,540 not meas. 21ms 40ms 52ms 88ms 0 transport_latency_assumed tick_size_change m 4,544 2,286 4ms 8ms 27ms 815ms 0 transport_latency_assumed tick_size_change n 4,268 not meas. 43ms 47ms 76ms 415ms 0 transport_latency_assumed tick_size_change o 4,544 2,250 4ms 8ms 21ms 87ms 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-10/06/2026-10-10T06.parquet sha256sum 2026-10-10T06.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.