Hour audit: 2026-09-25T16
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-25T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T16:00:00.000016185+00:00 · last event 2026-09-25T16:59:59.999932893+00:00
VOLUME 122,784,773 rows · 1,303,688,104 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 122,323,093 · i: 122,310,973 · k: 117,601,771 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,961,195 (10.56%) · i: 5,660,499 (4.61%) · k: 104,163,079 (84.83%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 3983288de44e5022f68cb394a47eb460bb92825a102dfe537a51036a6da86176
the corpus checksum ledger names this file with the same digest
joined 122,785,001 to merged 122,784,773, minus 228 (minus 0.0002%)
boundary drops 228 · 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:55:35Z 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,703,736 120,206,732 0-40 793fa5ebe9841ee3d291964e2ee6ee8efe5aff5e1b9e9152bedd13685046d8d9 book 569,234 58,037,468 41-43 9319874e10c9b140bf85b72d5165f2e9ac894b34ab95e61181733d92f51fd4d6 last_trade_price 62,873 3,602,082 44-44 136742cbc39143b71558635fa4bf6c9617cfd7df168c1e387521018970eb9641 market_resolved 1,212 181,453 45-45 db29a0fc39ce87f8812b5cb428cca112ea9e77ee9646c2481e85c7b93cfdaa90 new_market 1,100 125,535 46-46 f97cf2317786a233e4e7499ca0fa270ad7de9ca6db98aab4bcb9bd481f3f3bf3 price_change 111,443,690 1,120,031,872 47-472 c0bf5923412f9452558a64c5e6c7df01eb66cf88d43d0a33dd936011af9dc4f9 tick_size_change 2,928 107,851 473-473 49e58a924800cd03055b8ae79b50bc9bd3657b6e6d7831633c8c3a2d9d61da07 EVENT MIX count share price_change 111,443,690 90.76% best_bid_ask 10,703,736 8.72% book 569,234 0.46% last_trade_price 62,873 0.05% tick_size_change 2,928 <0.01% market_resolved 1,212 <0.01% new_market 1,100 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,703,748 10,703,736 12 50,690 PARTIAL book 569,242 569,234 8 208,981 PARTIAL last_trade_price 62,874 62,873 1 4,092 PARTIAL market_resolved 1,213 1,212 1 1,128 PARTIAL new_market 1,100 1,100 0 826 PARTIAL price_change 111,443,896 111,443,690 206 87,731 PARTIAL tick_size_change 2,928 2,928 0 732 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,703,049 1,064,330 19ms 35ms 161ms 44.8s 0 transport_latency_assumed best_bid_ask i 10,702,378 469,167 21ms 31ms 131ms 4.1s 0 transport_latency_assumed best_bid_ask k 10,266,972 9,170,239 13ms 23ms 136ms 6.9s 0 transport_latency_assumed book h 129,210 16,857 24ms 85ms 8.3min 100.2d 0 book_staleness book i 144,514 18,874 26ms 48.5s 7.0d 118.8d 0 book_staleness book k 556,499 533,503 19.5min 3.8d 34.1d 118.8d 0 book_staleness last_trade_price h 62,785 7,434 21ms 66ms 385ms 11.2s 0 transport_latency_assumed last_trade_price i 62,611 2,608 25ms 145ms 999ms 2.9s 0 transport_latency_assumed last_trade_price k 60,536 52,831 14ms 40ms 210ms 2.4s 0 transport_latency_assumed market_resolved h 1,127 194 36ms 20.6s 54.9s 58.0s 0 transport_latency_assumed market_resolved i 1,128 50 25ms 111ms 49.8s 57.4s 0 transport_latency_assumed market_resolved k 1,118 968 16ms 60ms 48.3s 2.4min 0 transport_latency_assumed new_market h 826 299 134ms 20.9s 33.7s 1.9min 0 transport_latency_assumed new_market i 826 299 113ms 18.3s 33.1s 1.4min 0 transport_latency_assumed new_market k 826 502 77ms 10.4s 29.2s 1.3min 0 transport_latency_assumed price_change h 111,423,168 11,871,768 19ms 41ms 215ms 46.1s 0 transport_latency_assumed price_change i 111,396,588 5,169,348 21ms 40ms 271ms 4.1s 0 transport_latency_assumed price_change k 106,713,052 94,402,574 13ms 26ms 150ms 7.2s 0 transport_latency_assumed tick_size_change h 2,928 313 19ms 33ms 96ms 13.9s 0 transport_latency_assumed tick_size_change i 2,928 153 21ms 29ms 85ms 241ms 0 transport_latency_assumed tick_size_change k 2,768 2,462 13ms 22ms 139ms 232ms 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/16/2026-09-25T16.parquet sha256sum 2026-09-25T16.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.