Hour audit: 2026-09-25T15
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, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-25T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T15:00:00.000065761+00:00 · last event 2026-09-25T15:59:59.999979076+00:00
VOLUME 131,830,869 rows · 1,385,771,574 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 130,850,022 · k: 120,584,386 · i: 120,221,191 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,339,541 (15.43%) · k: 105,996,480 (80.40%) · i: 5,494,848 (4.17%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 b87bb5170f8c43d1855862217b5a82677d66bb6b72d20a6426c849724bbd93a5
the corpus checksum ledger names this file with the same digest
joined 131,832,969 to merged 131,830,869, minus 2,100 (minus 0.0016%)
boundary drops 2,100 · 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-25T22:33:19Z as hik
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,516,838 137,781,590 0-47 d69772d73eb02edc5d6394893961e6d3de9920c0f8b5767a8e620f7aa1ebed46 book 1,074,256 72,629,168 48-52 5adcd2410a98ff8ca52faff215bd231bc4c06066992628db59d0ad75638c568f last_trade_price 66,070 3,695,096 53-53 06f78122ae857f75cbf2a927e50d72e5e60561b3406b9a281b3d1f9de4c44fe9 market_resolved 837 108,253 54-54 eb0a13a4f24c9d7f90ffb1430c4e0e6a1d29246f8893bcbe124d922cbb33396e new_market 482 52,708 55-55 5ba7c7c4c94d29c3c59c21e6bf48cc58b1616bd7711bd35b28f813e844a1c1dc price_change 118,170,082 1,169,924,499 56-506 38fcf971b6c056b4c73bc3c57eb8d52e1f4812e143deae1bf0cd796f6a0427de tick_size_change 2,304 84,460 507-507 abf5f2b2bc1f69d3f4358dd8ba6c625e085209ee8b1fb5e50ba464efd0049ab8 EVENT MIX count share price_change 118,170,082 89.64% best_bid_ask 12,516,838 9.49% book 1,074,256 0.81% last_trade_price 66,070 0.05% tick_size_change 2,304 <0.01% market_resolved 837 <0.01% new_market 482 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,516,872 12,516,838 34 51,202 PARTIAL book 1,075,416 1,074,256 1,160 209,206 PARTIAL last_trade_price 66,070 66,070 0 3,698 PARTIAL market_resolved 837 837 0 650 PARTIAL new_market 482 482 0 336 PARTIAL price_change 118,170,988 118,170,082 906 87,574 PARTIAL tick_size_change 2,304 2,304 0 576 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,516,186 1,855,085 19ms 45ms 121ms 8.7s 0 transport_latency_assumed best_bid_ask i 11,420,356 447,070 22ms 35ms 122ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,465,744 10,214,683 13ms 25ms 109ms 1.5s 0 transport_latency_assumed book h 145,350 33,542 26ms 288ms 3.8d 118.7d 0 book_staleness book i 960,005 445,675 1.1h 3.8d 41.0d 118.7d 0 book_staleness book k 968,599 595,039 1.1h 3.8d 41.0d 118.7d 0 book_staleness last_trade_price h 65,936 11,302 21ms 70ms 321ms 4.8s 0 transport_latency_assumed last_trade_price i 60,240 2,509 25ms 123ms 769ms 3.2s 0 transport_latency_assumed last_trade_price k 60,463 52,259 14ms 43ms 217ms 1.5s 0 transport_latency_assumed market_resolved h 650 129 21ms 95ms 46.5s 51.6s 0 transport_latency_assumed market_resolved i 723 128 27ms 6.9min 11.2min 11.2min 0 transport_latency_assumed market_resolved k 752 580 18ms 7.8min 12.0min 12.0min 0 transport_latency_assumed new_market h 336 137 64ms 9.7s 55.1s 1.6min 0 transport_latency_assumed new_market i 364 139 80ms 1.3min 7.7min 7.7min 0 transport_latency_assumed new_market k 369 206 68ms 3.8min 8.5min 8.5min 0 transport_latency_assumed price_change h 118,119,260 18,438,914 20ms 51ms 159ms 8.7s 0 transport_latency_assumed price_change i 107,777,471 4,599,273 23ms 45ms 261ms 4.1s 0 transport_latency_assumed price_change k 108,086,475 95,131,895 13ms 29ms 131ms 2.2s 0 transport_latency_assumed tick_size_change h 2,304 432 20ms 40ms 78ms 117ms 0 transport_latency_assumed tick_size_change i 2,032 54 22ms 31ms 86ms 102ms 0 transport_latency_assumed tick_size_change k 1,984 1,818 13ms 20ms 38ms 212ms 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/15/2026-09-25T15.parquet sha256sum 2026-09-25T15.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.