If you are reviewing a mortgage file, an insurance claim, or an autonomous-system decision years after it happened, you are going to ask one question:
What did the system actually rely on at decision time?
A screenshot of a dashboard is not enough. A line in a log file is not enough, logs expire, get rotated, get lost in vendor migrations. What you need is an artifact that is self-contained, tamper-evident, and verifiable on its own merits, without having to call the original API again.
That artifact is the GeoClear Evidence Bundle.
What's in the bundle
An Evidence Bundle is a customer-held evidence package containing the operational evidence record, retained evidence, verification material, and supporting references needed for later review. It travels with your decision record and verifies independently, without contacting GeoClear servers.
How to verify a bundle in five minutes
- Open the browser verifier.
- Drag the bundle in.
- The verifier checks the record against the bundled verification material.
- Green checkmarks = verified. Red = mutated since issuance.
Verification runs locally in your browser using retained verification material. GeoClear's servers do not participate in the verification result. If GeoClear is unreachable, taken offline, or no longer exists, the bundle still verifies on its own terms, which is the point.
What this verifies, and what it doesn't
This is the part most procurement reviewers want to see in plain English.
What this verifies
- GeoClear issued this record at the timestamp inside it.
- The recorded payload has not been mutated since issuance.
- The verification material traces to a stable, customer-verifiable trust anchor.
- The customer can re-verify the record later without contacting GeoClear servers.
What this does not verify
- That every upstream dataset was perfect.
- Full legal or regulatory compliance.
- That a downstream business decision was risk-free.
- That the physical world itself was verified (we record what was checked, not whether the world matched).
That distinction is deliberate. It is the right boundary for auditability without overclaiming what cryptography can verify.
Real-world examples
Two examples of the question a bundle answers later:
Agentic-commerce chargeback
A merchant disputes a chargeback on a $5,000 transaction. The bundle includes the transaction record, consent context, and compliance snapshot from the original verdict, the issuing bank’s investigator can verify the consent context independently using the customer-held verification material.
Agent-to-agent verification
An autonomous agent calls a result-returning tool and passes the operational evidence record to a downstream agent (or human reviewer). The bundle is what the downstream consumer verifies independently, tamper-evident evidence of what the upstream agent saw, regardless of whether the upstream agent’s logs are still intact. See the sample bundle gallery →
What you should retain
For high-stakes results, retain the full Evidence Bundle alongside the rest of your file. The bundle is self-contained and verifies independently, for as long as your audit horizon requires.
For procurement / SOC 2 / ISO contexts, the verification material is durable: it does not depend on GeoClear’s continued operation for re-verification.
Try it
, Shailesh, founder at GeoClear
More: All resources · Evidence Bundle verification, offline verifier · Compliance: records that outlive the application