Hour audit: 2026-09-25T20
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-25T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-25T20:00:00.000000688+00:00 · last event 2026-09-25T20:59:59.999717736+00:00
VOLUME 106,228,453 rows · 1,144,874,903 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured k: 106,017,901 · h: 106,008,379 · i: 105,847,199 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 93,132,781 (87.67%) · h: 8,142,746 (7.67%) · i: 4,952,926 (4.66%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 b8471a7dd7fa72b97b04fbf66a465a298a4245422a2a08bce2bbb68b8adc26e1
the corpus checksum ledger names this file with the same digest
joined 106,228,671 to merged 106,228,453, minus 218 (minus 0.0002%)
boundary drops 218 · 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-26T00:20:17Z 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,484,569 118,579,904 0-39 a080930b04a9884285d3500e5ff089bde49511965e89108945eb8eca5512a4d1 book 515,873 48,578,976 40-41 20cb2cbe2324823b952a2ee0c011ac2c2137b95d4378e2af50aa32c3a7592582 last_trade_price 56,422 3,259,623 42-42 1507c5fd6a4333559061928330355afb58ce1e0a82ad389bbd3ca3496ef78ca0 market_resolved 1,379 211,472 43-43 80b31fade96e856a3b2e33bd9ccd187bd687103e7d865479eafa4163b02be142 new_market 3,230 365,932 44-44 db3bdf9b5df934c76a4c98d395be67563e56247024dc491bfdf22bc72c9f15dd price_change 95,162,392 972,506,046 45-408 0db937613f2b483df22c76cf4e54811124b1bc40b97133579df6242221d99cca tick_size_change 4,588 166,030 409-409 88f03be8f53978355d6bb8d77cde73a3e21bad3008fc888e060ecfd407a0921e EVENT MIX count share price_change 95,162,392 89.58% best_bid_ask 10,484,569 9.87% book 515,873 0.49% last_trade_price 56,422 0.05% tick_size_change 4,588 <0.01% new_market 3,230 <0.01% market_resolved 1,379 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,484,593 10,484,569 24 54,832 PARTIAL book 515,877 515,873 4 172,069 PARTIAL last_trade_price 56,422 56,422 0 3,948 PARTIAL market_resolved 1,379 1,379 0 1,317 PARTIAL new_market 3,230 3,230 0 2,451 PARTIAL price_change 95,162,582 95,162,392 190 88,447 PARTIAL tick_size_change 4,588 4,588 0 1,147 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,481,747 755,752 18ms 43ms 430ms 56.7s 0 transport_latency_assumed best_bid_ask i 10,483,048 446,810 20ms 30ms 178ms 5.0s 0 transport_latency_assumed best_bid_ask k 10,482,045 9,282,007 12ms 24ms 246ms 55.2s 0 transport_latency_assumed book h 334,773 183,603 2.2min 3.2d 34.3d 118.9d 0 book_staleness book i 165,492 44,597 38ms 9.9h 20.3d 118.9d 0 book_staleness book k 358,147 287,673 3.4min 3.2d 34.3d 118.9d 0 book_staleness last_trade_price h 56,329 4,772 19ms 87ms 550ms 51.6s 0 transport_latency_assumed last_trade_price i 56,267 2,879 22ms 97ms 779ms 2.3s 0 transport_latency_assumed last_trade_price k 56,197 48,771 13ms 51ms 322ms 6.8s 0 transport_latency_assumed market_resolved h 1,317 94 18ms 651ms 48.9s 50.5s 0 transport_latency_assumed market_resolved i 1,317 104 20ms 88ms 52.8s 55.9s 0 transport_latency_assumed market_resolved k 1,317 1,181 13ms 353ms 47.0s 49.4s 0 transport_latency_assumed new_market h 2,451 1,144 138ms 25.6s 2.2min 3.5min 0 transport_latency_assumed new_market i 2,451 992 115ms 23.0s 2.2min 3.5min 0 transport_latency_assumed new_market k 2,451 1,094 119ms 21.8s 2.2min 3.5min 0 transport_latency_assumed price_change h 95,127,174 7,196,954 18ms 50ms 483ms 56.8s 0 transport_latency_assumed price_change i 95,134,036 4,457,174 20ms 39ms 291ms 5.0s 0 transport_latency_assumed price_change k 95,113,156 83,508,264 13ms 28ms 260ms 58.6s 0 transport_latency_assumed tick_size_change h 4,588 427 18ms 77ms 756ms 14.2s 0 transport_latency_assumed tick_size_change i 4,588 370 20ms 67ms 269ms 405ms 0 transport_latency_assumed tick_size_change k 4,588 3,791 13ms 56ms 362ms 1.7s 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/20/2026-09-25T20.parquet sha256sum 2026-09-25T20.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.