Resources · Evidence Bundles

Sample customer-held evidence bundles.

GeoClear evidence bundles show what a customer can retain after an action is verified: operational evidence, verification material, evidence commitments, and audit instructions.

Open verification demo → Verify Evidence Locally Request Architecture Brief

What an evidence bundle is.

The bundle is what the customer keeps after the verification layer does its job.

Action proposed → Evidence verified → Outcome recorded → Customer keeps bundle

An evidence bundle is the customer-held package that supports later review. It can contain the operational evidence record, an evidence summary, verification material, a manifest, and instructions for local or offline verification.

What a sample bundle contains.

Public-safe row list. Specific bundle internals and production trust material live behind the gated Security Architecture Brief.

Bundle item	Plain meaning
Operational evidence record	The tamper-evident artifact
Evidence packet summary	What action was proposed and what evidence path applied
Policy result summary	Whether the policy result was accept, hold, reject, block, or escalate
Evidence commitments	References or hashes, not raw source data
Verification material	Material needed for local verification
Manifest	Inventory of bundle contents
Verification instructions	How a reviewer checks the bundle later

Public samples are sanitized and do not contain customer data, raw mission data, or production trust material.

Sample bundles by outcome.

Five sample scenarios mapped to the four outcome types.

Sample 1 · Accept

Agentic Tool Call

A tool action carries valid operational evidence and is accepted by the receiving system.

Outcome: Valid evidence → Accept

Use for: MCP, agent runtime, tool-call governance.

Sample 2 · Hold

Back-Office Approval

An agent-prepared approval action is held until required human approval evidence is present.

Outcome: Missing approval → Hold

Use for: back-office, finance, procurement, administrative workflows.

Sample 3 · Accept / Hold

Visual Evidence

A model-generated observation is routed only when required evidence and review status are present.

Outcome: Evidence path verified → Accept / Hold

Use for: visual-evidence workflow review, analyst routing, audit.

Sample 4 · Block

Policy Violation Block

An out-of-policy action is blocked before dispatch, and the evidence record shows why it did not proceed.

Outcome: Policy violation → Block

Use for: high-impact actions, autonomous workflows, compliance review.

Sample 5 · Reject

Tampered Evidence Rejection

An evidence packet was modified after issuance. Local verification detects the modification and rejects it.

Outcome: Tampered evidence → Reject

Use for: independent verification, dispute review, audit.

Sample bundle access.

Status

Public sample downloads are being refreshed to align with the current operational-evidence format. Until then, use the verification layer demo and the offline verifier to see the verification flow.

Request Sample Bundle Access →

What sample bundles verify. What they do not verify.

Claim boundary applied to public samples.

What sample bundles verify

The evidence artifact was issued by the configured trust boundary.
The retained evidence matches the issued artifact.
Verification detects later modification.
The action followed the recorded evidence path.

What sample bundles do not verify

They do not verify the AI was right.
They do not verify the real-world truth of upstream data.
They do not provide legal certification by themselves.
Public samples are examples, not customer production records.

Last updated: 2026-05-31