Hour audit: 2026-09-26T04
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-26T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T04:00:00.000002298+00:00 · last event 2026-09-26T04:59:59.999943677+00:00
VOLUME 103,618,856 rows · 1,039,841,412 bytes (991.67 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 103,489,083 · k: 103,461,039 · i: 103,390,886 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,644,210 (5.45%) · k: 94,473,355 (91.17%) · i: 3,501,291 (3.38%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 e8e12cd8e91d150efcec5c1dddb27433be0db82311c98ee05c8253435f287015
the corpus checksum ledger names this file with the same digest
joined 103,621,983 to merged 103,618,856, minus 3,127 (minus 0.0030%)
boundary drops 3,127 · 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-26T05:51:43Z 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 10,948,249 119,700,804 0-41 2d999154e870a1d98b290b1955ad0a2ebbc7fc71874bd4b8002409223c88652d book 286,285 27,948,038 42-43 66d3cb074e42103d1446e8d2db1d9f532651b760a69be379b1fc99334864c399 last_trade_price 38,183 2,232,795 44-44 977c2d2c3a733cd3245a046f85dd8ccad04d33ce595ee8de2c764e5028d79e5e market_resolved 2,287 360,882 45-45 28cc2e0a0bcabb8f9599bcf137e4010b5c2a42cb3f2f32f13c8bc54bec51f80e new_market 3,280 358,642 46-46 16cf7d7a291fe1931b12aab4562c18449476560e3c3531149666eb1a582eb592 price_change 92,334,336 887,832,785 47-399 f82fea235ffa89619d9323e2fb62c94b6a14499fefdf463e31bef6026cb545e8 tick_size_change 6,236 227,194 400-400 41eea3129934f475f4eacb8da6f58f869f4419090b392984e392dca295b21bed EVENT MIX count share price_change 92,334,336 89.11% best_bid_ask 10,948,249 10.57% book 286,285 0.28% last_trade_price 38,183 0.04% tick_size_change 6,236 <0.01% new_market 3,280 <0.01% market_resolved 2,287 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,948,737 10,948,249 488 51,732 PARTIAL book 286,362 286,285 77 97,868 PARTIAL last_trade_price 38,183 38,183 0 3,012 PARTIAL market_resolved 2,287 2,287 0 2,177 PARTIAL new_market 3,280 3,280 0 2,433 PARTIAL price_change 92,336,898 92,334,336 2,562 95,803 PARTIAL tick_size_change 6,236 6,236 0 1,559 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,945,120 540,963 18ms 31ms 807ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,947,140 339,269 21ms 26ms 166ms 3.6s 0 transport_latency_assumed best_bid_ask k 10,946,578 10,068,017 12ms 18ms 297ms 13.8s 0 transport_latency_assumed book h 208,883 128,107 53.3s 3.4d 34.6d 119.3d 0 book_staleness book i 82,573 9,158 23ms 146ms 1.0h 119.2d 0 book_staleness book k 172,203 149,020 7.0s 3.2d 34.6d 119.3d 0 book_staleness last_trade_price h 37,912 2,295 19ms 63ms 1.6s 35.8s 0 transport_latency_assumed last_trade_price i 38,075 1,732 23ms 46ms 333ms 1.3s 0 transport_latency_assumed last_trade_price k 37,971 34,156 13ms 29ms 416ms 7.1s 0 transport_latency_assumed market_resolved h 2,176 83 18ms 33.3s 54.0s 57.2s 0 transport_latency_assumed market_resolved i 2,177 469 22ms 33.4s 54.0s 57.1s 0 transport_latency_assumed market_resolved k 2,177 1,735 13ms 27.5s 52.1s 54.5s 0 transport_latency_assumed new_market h 2,424 981 223ms 36.1s 1.4min 1.8min 0 transport_latency_assumed new_market i 2,433 1,224 174ms 36.4s 1.4min 1.8min 0 transport_latency_assumed new_market k 2,424 1,075 212ms 32.0s 1.4min 1.8min 0 transport_latency_assumed price_change h 92,286,332 4,971,450 18ms 36ms 849ms 1.0min 0 transport_latency_assumed price_change i 92,312,252 3,149,240 21ms 29ms 206ms 8.2s 0 transport_latency_assumed price_change k 92,293,450 84,213,646 12ms 21ms 304ms 14.1s 0 transport_latency_assumed tick_size_change h 6,236 331 18ms 32ms 173ms 12.4s 0 transport_latency_assumed tick_size_change i 6,236 199 21ms 67ms 179ms 197ms 0 transport_latency_assumed tick_size_change k 6,236 5,706 12ms 19ms 110ms 294ms 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-26/04/2026-09-26T04.parquet sha256sum 2026-09-26T04.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.