Hour audit: 2026-09-25T23
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-25T23 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T23:00:00.000048986+00:00 · last event 2026-09-25T23:59:59.999996470+00:00
VOLUME 126,045,735 rows · 1,343,551,729 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured i: 124,854,771 · h: 124,604,741 · k: 109,090,843 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 11,048,982 (8.77%) · h: 16,819,986 (13.34%) · k: 98,176,767 (77.89%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 1c6c6f46ed8802171b58b24fd3a883ff55a07b738253c29b65539a65caaa8946
the corpus checksum ledger names this file with the same digest
joined 126,046,103 to merged 126,045,735, minus 368 (minus 0.0003%)
boundary drops 368 · 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-26T01:23:29Z 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 11,878,829 133,110,007 0-45 230d9f3aba841e696d10701a1fb072ec012d43c45df8f35156d196a375030e01 book 1,519,197 77,400,496 46-51 63d5207e69cd6f30dd979fa0f06353e54343eda96e345879804d4ce2b403e7f2 last_trade_price 52,680 2,978,582 52-52 dbbfd9867a1a2903313fd55908886c424f36e95c4deaca6e5b6f015b72f64311 market_resolved 1,596 201,968 53-53 0e87c54e4c6e0b642b1aff4467b5da74a5abc6e2a4ad5222911030a2559449f5 new_market 1,827 169,456 54-54 35ae71c0ef45e08b2933e208f95af82e1489ef70483373022d50b7a09e27771a price_change 112,588,086 1,128,132,688 55-484 b2c67c3b342ea0da3b911136d61c73896b7587491cfa8ed6e03984da51620d9c tick_size_change 3,520 128,139 485-485 4bdf70a8d9a8fd8936149d16e178239e10174d31f74c7c5f154eea28f13d129c EVENT MIX count share price_change 112,588,086 89.32% best_bid_ask 11,878,829 9.42% book 1,519,197 1.21% last_trade_price 52,680 0.04% tick_size_change 3,520 <0.01% new_market 1,827 <0.01% market_resolved 1,596 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,878,867 11,878,829 38 54,576 PARTIAL book 1,519,213 1,519,197 16 216,782 PARTIAL last_trade_price 52,680 52,680 0 3,158 PARTIAL market_resolved 1,596 1,596 0 1,237 PARTIAL new_market 1,827 1,827 0 1,095 PARTIAL price_change 112,588,400 112,588,086 314 92,194 PARTIAL tick_size_change 3,520 3,520 0 880 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,877,212 1,547,732 18ms 43ms 227ms 37.8s 0 transport_latency_assumed best_bid_ask i 11,876,129 949,190 21ms 28ms 105ms 4.2s 0 transport_latency_assumed best_bid_ask k 10,356,261 9,381,907 13ms 20ms 118ms 9.9s 0 transport_latency_assumed book h 125,498 19,963 25ms 7.5min 9.8d 100.5d 0 book_staleness book i 384,790 116,617 6.0min 4.1d 34.4d 119.1d 0 book_staleness book k 1,402,044 1,382,617 2.4h 4.1d 41.6d 119.0d 0 book_staleness last_trade_price h 52,401 7,214 20ms 76ms 632ms 35.2s 0 transport_latency_assumed last_trade_price i 52,462 6,912 22ms 51ms 429ms 2.7s 0 transport_latency_assumed last_trade_price k 45,069 38,554 14ms 39ms 283ms 4.2s 0 transport_latency_assumed market_resolved h 1,237 110 19ms 151ms 52.5s 52.6s 0 transport_latency_assumed market_resolved i 1,237 131 21ms 123ms 47.8s 47.9s 0 transport_latency_assumed market_resolved k 1,516 1,355 15ms 10.0min 19.9min 19.9min 0 transport_latency_assumed new_market h 1,095 503 132ms 20.9s 1.4min 2.1min 0 transport_latency_assumed new_market i 1,095 568 116ms 20.2s 1.4min 1.9min 0 transport_latency_assumed new_market k 1,291 756 228ms 5.9min 16.3min 16.4min 0 transport_latency_assumed price_change h 112,543,778 15,243,847 19ms 48ms 270ms 39.9s 0 transport_latency_assumed price_change i 112,535,538 9,975,338 21ms 30ms 143ms 4.4s 0 transport_latency_assumed price_change k 97,281,674 87,368,901 13ms 22ms 138ms 10.1s 0 transport_latency_assumed tick_size_change h 3,520 617 19ms 43ms 190ms 836ms 0 transport_latency_assumed tick_size_change i 3,520 226 21ms 35ms 157ms 349ms 0 transport_latency_assumed tick_size_change k 2,988 2,677 13ms 24ms 118ms 340ms 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/23/2026-09-25T23.parquet sha256sum 2026-09-25T23.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.