Hour audit: 2026-10-04T09
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-04T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T09:00:00.000073280+00:00 · last event 2026-10-04T09:59:59.999955645+00:00
VOLUME 94,264,560 rows · 1,031,697,719 bytes (983.90 MiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 94,218,737 · i: 94,209,746 · m: 94,202,264 · h: 94,156,715 · n: 94,124,109 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 47,197,209 (50.07%) · i: 303,459 (0.32%) · m: 46,299,043 (49.12%) · h: 409,948 (0.43%) · n: 54,901 (0.06%) (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 94,264,560 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 73f696472407c6867c950f300238547b4a3d68635e83fa477b43b84f1c2d0e8f
the corpus checksum ledger names this file with the same digest
joined 94,265,334 to merged 94,264,560, minus 774 (minus 0.0008%)
boundary drops 774 · 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-04T10:58:18Z 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 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 8,039,689 100,298,651 0-30 26dcb5b9143a79d9b267f2f22f43d1000f4ba2dae7545aeb70c583af4a834488 book 122,242 12,600,207 31-31 f6e2bf041f7126a9f906732512f76a621f42c3d2f6bbed06096236a93d8c1449 last_trade_price 51,395 2,979,898 32-32 73c1224fa61077914c8c251816b604155d5a1c3540b7f96da7b9f8273b7ec6c6 market_resolved 618 102,471 33-33 6abd0bc7a31ba02bb1c81f6d733fc932d26509bdc8e6ce908d1efdedce864604 new_market 3,468 301,023 34-34 67e3551e1827108a1882475952f7af174fe76a3402e4c9697957411a85d2ebab price_change 86,044,428 914,235,360 35-363 3bba28537da3b3fc92f57b12e7516f60ea340f2c6b6da0947c42a62f1a00d9ec tick_size_change 2,720 101,595 364-364 dcc13ca2baef09e43cc067ef4bf600fad5e76826b984979ac7eda195b983fc2e EVENT MIX count share price_change 86,044,428 91.28% best_bid_ask 8,039,689 8.53% book 122,242 0.13% last_trade_price 51,395 0.05% new_market 3,468 <0.01% tick_size_change 2,720 <0.01% market_resolved 618 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,039,797 8,039,689 108 389 FULL book 122,242 122,242 0 6,594 FULL last_trade_price 51,395 51,395 0 0 FULL market_resolved 618 618 0 0 FULL new_market 3,468 3,468 0 0 FULL price_change 86,045,094 86,044,428 666 752 FULL tick_size_change 2,720 2,720 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 8,036,737 30,867 18ms 26ms 610ms 2.2min 0 transport_latency_assumed best_bid_ask i 8,037,367 24,143 21ms 27ms 222ms 56.7s 0 transport_latency_assumed best_bid_ask m 8,038,177 3,984,652 4ms 10ms 147ms 17.2s 0 transport_latency_assumed best_bid_ask n 8,036,338 4,072 45ms 58ms 377ms 23.6s 0 transport_latency_assumed best_bid_ask o 8,038,059 3,995,955 4ms 10ms 120ms 18.3s 0 transport_latency_assumed book h 110,944 6,028 22ms 187ms 3.1h 108.9d 0 book_staleness book i 109,036 3,112 24ms 134ms 29.4min 127.5d 0 book_staleness book m 107,760 54,388 6ms 26ms 22.1s 108.9d 0 book_staleness book n 111,152 6,176 50ms 748ms 6.2h 108.9d 0 book_staleness book o 107,528 52,538 6ms 26ms 6.0s 62.9d 0 book_staleness last_trade_price h 51,271 258 20ms 43ms 677ms 1.8min 0 transport_latency_assumed last_trade_price i 51,348 118 23ms 61ms 709ms 6.9s 0 transport_latency_assumed last_trade_price m 51,374 25,646 6ms 14ms 202ms 3.3s 0 transport_latency_assumed last_trade_price n 51,154 28 49ms 178ms 5.0s 22.1s 0 transport_latency_assumed last_trade_price o 51,369 25,345 6ms 14ms 210ms 4.9s 0 transport_latency_assumed market_resolved h 618 not meas. 21ms 31.0s 46.7s 46.8s 0 transport_latency_assumed market_resolved i 618 1 24ms 27.3s 44.4s 44.5s 0 transport_latency_assumed market_resolved m 618 276 5ms 15.1s 31.6s 31.7s 0 transport_latency_assumed market_resolved n 618 not meas. 48ms 24.0s 40.3s 40.3s 0 transport_latency_assumed market_resolved o 618 341 6ms 13.8s 30.0s 30.0s 0 transport_latency_assumed new_market h 1,935 457 222ms 32.5s 42.8s 1.6min 0 transport_latency_assumed new_market i 1,935 290 185ms 33.8s 43.7s 1.7min 0 transport_latency_assumed new_market m 1,935 1,047 113ms 32.7s 42.3s 1.5min 0 transport_latency_assumed new_market n 1,935 588 268ms 33.8s 46.0s 1.4min 0 transport_latency_assumed new_market o 1,935 1,086 98ms 34.2s 40.5s 1.7min 0 transport_latency_assumed price_change h 85,952,490 372,316 18ms 29ms 637ms 2.2min 0 transport_latency_assumed price_change i 86,006,722 275,776 22ms 31ms 331ms 56.8s 0 transport_latency_assumed price_change m 85,999,680 42,231,720 5ms 11ms 159ms 31.6s 0 transport_latency_assumed price_change n 85,920,192 44,030 45ms 72ms 922ms 24.8s 0 transport_latency_assumed price_change o 86,016,508 43,120,586 5ms 10ms 133ms 20.9s 0 transport_latency_assumed tick_size_change h 2,720 22 19ms 40ms 1.1s 2.1min 0 transport_latency_assumed tick_size_change i 2,720 19 22ms 49ms 510ms 1.6s 0 transport_latency_assumed tick_size_change m 2,720 1,314 5ms 20ms 374ms 973ms 0 transport_latency_assumed tick_size_change n 2,720 7 45ms 94ms 507ms 4.9s 0 transport_latency_assumed tick_size_change o 2,720 1,358 5ms 19ms 254ms 446ms 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-04/09/2026-10-04T09.parquet sha256sum 2026-10-04T09.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.