Long-horizon verification

How operational receipts remain verifiable for the long horizon: redundant publication of verification material, customer-held copies, and an open verification recipe.

Some decisions matter for years: mortgage files, insurance policies, reinsurance portfolios, compliance reviews, logistics disputes, autonomous dispatch records. Long-horizon verification is the property that lets a reviewer check a customer-held operational receipt years after it was issued — without depending on GeoClear's application server being reachable, and without depending on any single distribution channel remaining available.

How long-horizon verification works

Three independent layers protect verifiability for the long horizon:

The bundle in the customer's file. Every Evidence Bundle is self-contained: the operational receipt, the canonical payload it commits to, the retained verification material needed to verify the receipt, and a self-contained in-browser verifier. As long as the customer retains the bundle, verification works — no internet, no GeoClear server, no external dependency.
Published verification material. Public verification material is distributed through redundant channels for independent durability beyond any single endpoint or organization. This protects the case where the customer needs to verify a receipt for which they don't have the bundle on hand.
A customer-side periodic snapshot. Belt-and-suspenders: pull a snapshot of the published verification material on a cadence that fits your retention policy, archive it next to your bundles, and you have a third independent copy.

What this surface does not promise

Storage durability is a property of redundant publication + customer-held copies, not a guarantee about the future of any specific service. The Vault preserves your operational receipts; the bundle preserves the verification recipe; published verification material backs up the recipe.

This surface does not enumerate the receipts that have been issued — that is the role of the customer-held receipt + GeoClear's append-only issuance store. This surface is solely about preserving the public verification recipe that lets any qualified reviewer validate any signed operational receipt.

Detailed implementation

Detailed publication topology, key-distribution model, rotation cadence, and emergency-rotation runbook are documented in the Security & Verification Whitepaper, available to qualified procurement and security reviewers under NDA.