GeoClear | Decision Receipt Profile

Operational receipts for AI and rules-based decisions. GeoClear records the inputs, policy context, and verdict returned at decision time so downstream systems can verify before acting and auditors can review later.

Truth boundary: GeoClear™ records the inputs and verdict returned at decision time. It does not certify that the model or policy was correct.

Who this is for

Credit-scoring teams, well-evidenced adverse-action notices, auditable decline/approve trails.
Underwriting platforms, retained evidence of the inputs and verdict returned at decision time.
AI agent builders, agent-to-agent verifiable hand-off (one agent passes an operational receipt to the next).
Any AI workflow whose decisions are reviewed later, chargeback, regulator inquiry, internal QC, post-incident review.

One platform, multiple profiles

GeoClear is real-time operational receipt infrastructure for machine-driven systems. Where the Location Receipt Profile records physical-presence claims and the Flood & Census Receipt Profile records regulatory determinations, Decision Receipt Profile records the verdict and the inputs that produced it, the agent’s output bound to the inputs the model received at decision time. The same receipt substrate powers all three profiles.

What the receipt records

decision_id: The calling system’s correlation token
input_payload_hash: Recorded inputs (tamper-evident)
verdict: Boolean / scored / classified
verdict_summary: Short reason string
verification_path: e.g. mcp://geoclear/verify_address + tool version
agent_id: The calling agent’s identity (when supplied)
consent_context_hash: Hash of the consent context that authorized the call (when applicable)
issued_at: The receipt’s timestamp

The receipt is bound to these fields at decision time. A downstream agent (or auditor) can verify later that the receipt the upstream agent is presenting was issued by GeoClear, for the inputs claimed, at the timestamp claimed. No round trip to GeoClear; no trust in the upstream agent’s logs.

Sample bundle

NC-0001, 562 Abington Road, NC Customer-held evidence bundle · offline-verifiable

Open sample gallery → Verify it now

Integration

Solutions: AI Agents & MCP
MCP tool catalog: verify_address + future per-decision tools (credit, risk)
Agent-to-agent flow: /resources/sample-bundles/agent-to-agent
Verifier: browser verifier · developer docs for the public verifier package
Underlying platform: Receipt Engine · Operational Receipts

What this proves, and what it doesn’t

What this proves

GeoClear issued this receipt 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 receipt later without contacting GeoClear servers.

What this does not prove

That the agent’s decision based on the verdict was correct or fair.
That the model was unbiased.
That the agent had authorization to act on the verdict.
That the downstream consumer interpreted it correctly.

GeoClear records the verdict + inputs, the human review of the decision’s quality is unchanged. The receipt makes the audit trail verifiable; it doesn’t make the underlying decision right.

Sister receipt profiles: Location Receipt Profile · Flood & Census Receipt Profile. Underneath them all: Receipt Engine + Operational Receipts.