Hour audit: 2026-10-06T15
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T15:00:00.000088556+00:00 · last event 2026-10-06T15:59:59.999911714+00:00
VOLUME 125,599,188 rows · 1,502,195,987 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 124,610,861 · h: 124,609,263 · i: 124,580,808 · m: 124,544,546 · n: 124,213,586 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 61,136,502 (48.68%) · h: 1,472,181 (1.17%) · i: 1,259,523 (1.00%) · m: 61,458,398 (48.93%) · n: 272,584 (0.22%) (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 125,599,188 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 471fc29c56be19d0fbcbe6821755fe5a0f4bfdda8f96b567d4f1984186bcfd5d
no line in the corpus checksum ledger names this file
joined 125,600,461 to merged 125,599,188, minus 1,273 (minus 0.0010%)
boundary drops 1,273 · 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-06T17:06: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 7/8 pass, 1 finding
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
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,763,950 139,676,479 0-41 08877342287dd81d2e2e3839fe401000eebf0fba4c11d591463da9acbddde297 book 1,569,293 103,943,846 42-47 f7275e38297d709e2f78dbe684995be8b5890bf94d3750b329d1e5800301abad last_trade_price 67,744 3,873,372 48-48 b3360fa7f4b48f805cb1eef21c3437efc27bf2e171e04f4308bbe42dbdd5b41e market_resolved 1,517 228,244 49-49 2b1dbbc151024d6cd958bd402f6c56382f52fbeba83c6c197dff35c3b7c6f34b new_market 472 52,339 50-50 9ffb8a9f13bbeaa6ca52217ba1ace4e4c2b7dd30e4aeb33195a0d783e137abac price_change 113,192,968 1,252,871,805 51-482 29e4627fa5f720ab93b99ade8c4bcf520107d32416f2df86118a5df80d56c8a7 tick_size_change 3,244 119,822 483-483 345a3674050c37e37525f8ae7ae1ca391647309587a14650fb78b1802987ac38 EVENT MIX count share price_change 113,192,968 90.12% best_bid_ask 10,763,950 8.57% book 1,569,293 1.25% last_trade_price 67,744 0.05% tick_size_change 3,244 <0.01% market_resolved 1,517 <0.01% new_market 472 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,764,064 10,763,950 114 75 FULL book 1,569,321 1,569,293 28 9,234 FULL last_trade_price 67,745 67,744 1 2 FULL market_resolved 1,517 1,517 0 2 FULL new_market 472 472 0 0 FULL price_change 113,194,098 113,192,968 1,130 64 FULL tick_size_change 3,244 3,244 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,758,770 101,399 19ms 33ms 160ms 6.6s 0 transport_latency_assumed best_bid_ask i 10,752,626 55,980 22ms 36ms 216ms 6.4s 0 transport_latency_assumed best_bid_ask m 10,756,964 5,331,814 6ms 18ms 100ms 3.2s 0 transport_latency_assumed best_bid_ask n 10,754,636 3,234 45ms 66ms 309ms 26.0s 0 transport_latency_assumed best_bid_ask o 10,758,679 5,271,523 6ms 18ms 100ms 3.2s 0 transport_latency_assumed book h 676,749 204,033 5.2min 1.3d 45.1d 129.7d 0 book_staleness book i 901,328 589,054 12.7min 1.3d 45.1d 129.7d 0 book_staleness book m 695,421 275,791 4.8min 1.3d 45.1d 129.7d 0 book_staleness book n 679,033 218,275 7.1min 1.3d 45.1d 129.7d 0 book_staleness book o 703,988 282,140 5.0min 1.3d 45.1d 129.7d 0 book_staleness last_trade_price h 67,595 760 22ms 130ms 865ms 5.6s 0 transport_latency_assumed last_trade_price i 66,996 347 27ms 384ms 3.1s 5.9s 0 transport_latency_assumed last_trade_price m 67,362 33,524 7ms 32ms 197ms 1.5s 0 transport_latency_assumed last_trade_price n 65,931 55 54ms 1.6s 11.4s 26.0s 0 transport_latency_assumed last_trade_price o 67,491 33,058 7ms 27ms 214ms 1.6s 0 transport_latency_assumed market_resolved h 1,412 20 21ms 19.9s 54.3s 1.1min 0 transport_latency_assumed market_resolved i 1,411 189 24ms 15.5s 52.7s 1.1min 0 transport_latency_assumed market_resolved m 1,412 643 7ms 16.6s 52.2s 56.0s 0 transport_latency_assumed market_resolved n 1,411 36 47ms 182ms 47.7s 57.4s 0 transport_latency_assumed market_resolved o 1,412 629 7ms 64ms 49.0s 2.5min 0 transport_latency_assumed new_market h 325 67 59ms 11.8s 1.0min 6.2d 0 transport_latency_assumed new_market i 325 46 46ms 10.3s 1.3min 6.2d 0 transport_latency_assumed new_market m 325 173 31ms 9.2s 21.0s 6.2d 0 transport_latency_assumed new_market n 325 32 82ms 11.3s 4.7d 6.2d 0 transport_latency_assumed new_market o 325 154 37ms 10.1s 54.7s 6.2d 0 transport_latency_assumed price_change h 113,101,172 1,165,854 20ms 42ms 378ms 6.8s 0 transport_latency_assumed price_change i 112,854,878 613,888 22ms 51ms 1.1s 7.3s 0 transport_latency_assumed price_change m 113,019,818 55,814,764 6ms 21ms 132ms 3.3s 0 transport_latency_assumed price_change n 112,709,006 50,952 46ms 103ms 3.6s 26.0s 0 transport_latency_assumed price_change o 113,075,722 55,547,510 6ms 20ms 130ms 3.4s 0 transport_latency_assumed tick_size_change h 3,240 48 19ms 33ms 93ms 282ms 0 transport_latency_assumed tick_size_change i 3,244 19 22ms 40ms 92ms 328ms 0 transport_latency_assumed tick_size_change m 3,244 1,689 6ms 20ms 92ms 238ms 0 transport_latency_assumed tick_size_change n 3,244 not meas. 45ms 61ms 164ms 364ms 0 transport_latency_assumed tick_size_change o 3,244 1,488 6ms 19ms 79ms 247ms 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-06/15/2026-10-06T15.parquet sha256sum 2026-10-06T15.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.