Hour audit: 2026-09-26T05
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-26T05 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T05:00:00.000444455+00:00 · last event 2026-09-26T05:59:59.999927362+00:00
VOLUME 102,475,258 rows · 1,015,985,954 bytes (968.92 MiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured i: 102,426,388 · k: 102,419,259 · h: 102,419,090 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 4,561,691 (4.45%) · k: 94,701,859 (92.41%) · h: 3,211,708 (3.13%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 ac62df3462af058a1c06cc9a9a82fea40c846158d1fe2a4ee97d83546c9b232c
the corpus checksum ledger names this file with the same digest
joined 102,475,554 to merged 102,475,258, minus 296 (minus 0.0003%)
boundary drops 296 · 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-26T06:57:39Z 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,297,522 121,719,647 0-43 a76f0c5e8e0954f500b9b8848413475684da5604c3de534753a1d50c1e96229c book 115,158 11,649,961 44-44 481ca6c72070d28c15197fbeda1b76236d2f0b56d5defbe9df7181eef572a267 last_trade_price 37,083 2,186,509 45-45 795308e81b1bf764c3367f3df99131e64f3894f5dcdf1f9e1d1ed0c14aae92bc market_resolved 1,512 238,470 46-46 d953e3d6af75357fc6ed61cd46e4660feb0718dfa9d6fd96099883bbaecb6079 new_market 811 90,844 47-47 427cac04c6ed129e11eeb46aaa3da1468cfdc6ca47342099f4aed815d5e07b1f price_change 91,019,488 878,799,061 48-395 25bee570eea1f1ce270ac1754829302fe06aa7d2f508b32b8b93b7065cb6cd6d tick_size_change 3,684 132,660 396-396 ab4a251c7e7895c8c3e6ded5b9fa4a128660c72321ef7fd9a8de47ca145f16da EVENT MIX count share price_change 91,019,488 88.82% best_bid_ask 11,297,522 11.02% book 115,158 0.11% last_trade_price 37,083 0.04% tick_size_change 3,684 <0.01% market_resolved 1,512 <0.01% new_market 811 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,297,556 11,297,522 34 47,666 PARTIAL book 115,164 115,158 6 22,865 PARTIAL last_trade_price 37,083 37,083 0 2,965 PARTIAL market_resolved 1,512 1,512 0 1,491 PARTIAL new_market 811 811 0 608 PARTIAL price_change 91,019,744 91,019,488 256 102,774 PARTIAL tick_size_change 3,684 3,684 0 921 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,296,912 310,000 18ms 24ms 93ms 44.4s 0 transport_latency_assumed best_bid_ask i 11,296,733 459,606 17ms 21ms 67ms 4.0s 0 transport_latency_assumed best_bid_ask k 11,296,912 10,527,916 12ms 16ms 62ms 7.5s 0 transport_latency_assumed book h 80,474 9,070 21ms 126ms 4.2d 100.8d 0 book_staleness book i 99,723 32,842 21ms 5.9h 18.8d 119.3d 0 book_staleness book k 85,620 73,246 15ms 50.3s 7.6d 119.3d 0 book_staleness last_trade_price h 37,011 1,715 19ms 42ms 295ms 33.1s 0 transport_latency_assumed last_trade_price i 37,039 2,095 19ms 34ms 211ms 3.7s 0 transport_latency_assumed last_trade_price k 36,962 33,273 13ms 23ms 235ms 1.6s 0 transport_latency_assumed market_resolved h 1,491 104 18ms 13.1s 50.6s 52.5s 0 transport_latency_assumed market_resolved i 1,491 175 19ms 14.3s 49.9s 53.8s 0 transport_latency_assumed market_resolved k 1,491 1,233 13ms 14.2s 44.8s 56.3s 0 transport_latency_assumed new_market h 608 209 104ms 13.9s 49.8s 1.5min 0 transport_latency_assumed new_market i 608 285 94ms 18.1s 57.5s 1.7min 0 transport_latency_assumed new_market k 608 317 133ms 22.6s 55.1s 1.7min 0 transport_latency_assumed price_change h 90,998,910 2,890,458 18ms 27ms 149ms 44.9s 0 transport_latency_assumed price_change i 90,987,110 4,066,586 17ms 22ms 122ms 4.2s 0 transport_latency_assumed price_change k 90,993,982 84,062,444 13ms 17ms 89ms 7.5s 0 transport_latency_assumed tick_size_change h 3,684 152 18ms 30ms 66ms 594ms 0 transport_latency_assumed tick_size_change i 3,684 102 19ms 47ms 86ms 167ms 0 transport_latency_assumed tick_size_change k 3,684 3,430 13ms 16ms 53ms 272ms 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/05/2026-09-26T05.parquet sha256sum 2026-09-26T05.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.