Hour audit: 2026-09-25T12
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
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: c. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T12 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T12:00:00.000225214+00:00 · last event 2026-09-25T12:59:59.999936788+00:00
VOLUME 127,200,201 rows · 1,395,925,268 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES ghik — 4 machines contributed rows
captured h: 126,298,549 · i: 126,283,082 · k: 121,472,632 · g: 106,095,470 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,281,446 (10.44%) · i: 7,383,212 (5.80%) · k: 106,020,861 (83.35%) · g: 514,682 (0.40%) (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 127,200,201 rows exactly, so those pairs supplied none
5 expected (cghik), 1 contributed nothing: c
INTEGRITY sha256 35b027f953c5555843303b1513267834e5a0a30eb8292ff244cbdfac00e9ce6d
the corpus checksum ledger names this file with the same digest
joined 127,202,346 to merged 127,200,201, minus 2,145 (minus 0.0017%)
boundary drops 2,145 · 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-09-25T18:24:13Z as ghik
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
FINDING a machine expected this hour contributed nothing
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 12,132,414 141,245,229 0-46 202133c9988735e9633b7a337b944b8d95ef4110bee0cdb039ad655aeed527b6 book 973,353 69,190,242 47-50 937ad53cb6f476e67c3060ef988b7a69af2273fb7ca3961f0f97b71058400e26 last_trade_price 60,963 3,492,995 51-51 3b25e477a68a7c176ef9ee9b3ccfbe8fab792e8c513be1a354fd8cc5a6ffab90 market_resolved 891 111,707 52-52 55f1d8e47f4b9a693f0c61ef0e62723a6f301b753924348dc77e0624071b3d9a new_market 2,304 217,223 53-53 584af915bc16a153647c8508a71b1490130ed9fc249b26862e353f26d33ce0e6 price_change 114,027,536 1,180,120,905 54-488 ae128fc2b63bad0bbffd0e2b13def319ae363818b1ca2170b7bca8bb1a43b658 tick_size_change 2,740 102,117 489-489 622ce3f4055b06de76fbb7160abb7c7886ddeda792b6251a14333b61f6c4a59a EVENT MIX count share price_change 114,027,536 89.64% best_bid_ask 12,132,414 9.54% book 973,353 0.77% last_trade_price 60,963 0.05% tick_size_change 2,740 <0.01% new_market 2,304 <0.01% market_resolved 891 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,132,630 12,132,414 216 50,036 PARTIAL book 973,369 973,353 16 210,007 PARTIAL last_trade_price 60,964 60,963 1 3,327 PARTIAL market_resolved 891 891 0 686 PARTIAL new_market 2,304 2,304 0 1,386 PARTIAL price_change 114,029,448 114,027,536 1,912 87,451 PARTIAL tick_size_change 2,740 2,740 0 685 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,204,170 1,746 80ms 121ms 645ms 30.4s 0 transport_latency_assumed best_bid_ask h 12,130,504 1,259,043 19ms 41ms 270ms 39.8s 0 transport_latency_assumed best_bid_ask i 12,129,960 639,629 21ms 33ms 135ms 4.1s 0 transport_latency_assumed best_bid_ask k 11,626,388 10,231,996 13ms 26ms 158ms 8.4s 0 transport_latency_assumed book g 837,847 488,664 1.1h 3.8d 40.7d 118.6d 0 book_staleness book h 127,844 13,477 25ms 175ms 1.9h 117.0d 0 book_staleness book i 132,202 22,666 24ms 200ms 2.9d 117.0d 0 book_staleness book k 541,168 448,546 21.5min 3.7d 33.9d 118.6d 0 book_staleness last_trade_price g 49,615 48 94ms 1.5s 13.7s 30.5s 0 transport_latency_assumed last_trade_price h 60,841 5,994 21ms 102ms 734ms 15.1s 0 transport_latency_assumed last_trade_price i 60,730 4,706 23ms 74ms 501ms 4.0s 0 transport_latency_assumed last_trade_price k 58,626 50,215 14ms 45ms 239ms 5.2s 0 transport_latency_assumed market_resolved g 704 205 95ms 8.0min 13.1min 14.1min 0 transport_latency_assumed market_resolved h 686 60 21ms 39.4s 47.6s 49.4s 0 transport_latency_assumed market_resolved i 686 133 22ms 34.3s 42.1s 43.3s 0 transport_latency_assumed market_resolved k 662 493 14ms 41.4s 5.1min 5.1min 0 transport_latency_assumed new_market g 1,439 353 583ms 6.5min 7.8min 9.6min 0 transport_latency_assumed new_market h 1,386 554 162ms 19.3s 40.7s 1.7min 0 transport_latency_assumed new_market i 1,386 556 127ms 16.5s 35.6s 1.3min 0 transport_latency_assumed new_market k 1,375 841 107ms 4.1min 4.9min 5.9min 0 transport_latency_assumed price_change g 94,999,411 23,666 81ms 194ms 5.2s 30.6s 0 transport_latency_assumed price_change h 113,974,548 12,002,068 19ms 48ms 349ms 40.8s 0 transport_latency_assumed price_change i 113,955,378 6,715,395 21ms 39ms 199ms 4.1s 0 transport_latency_assumed price_change k 109,241,801 95,286,407 13ms 29ms 168ms 8.6s 0 transport_latency_assumed tick_size_change g 2,284 not meas. 79ms 105ms 320ms 2.0s 0 transport_latency_assumed tick_size_change h 2,740 250 19ms 42ms 399ms 819ms 0 transport_latency_assumed tick_size_change i 2,740 127 21ms 35ms 312ms 407ms 0 transport_latency_assumed tick_size_change k 2,612 2,363 13ms 20ms 62ms 129ms 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-09-25/12/2026-09-25T12.parquet sha256sum 2026-09-25T12.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.