What the Receipt Engine does
The Receipt Engine is the horizontal layer underneath every product GeoClear ships. For eligible GeoClear verdict responses:
- Records the relevant operational inputs, binds them to policy context, and issues an operational receipt through the GeoClear trust boundary.
- Persists the receipt append-only on the GeoClear side; emits the receipt header on the response so the customer also holds it.
- Cross-references a public Key Transparency surface so any verifier can audit which key signed at which time.
- Cross-references the unified trust manifest so every channel a verifier needs is discoverable from one URL.
The issuance substrate is decision-domain-agnostic: the same trust boundary issues operational receipts for an address verification, a flood determination, a credit decision, or an autonomous-routing verdict. The Receipt Engine doesn’t care what the decision is, it cares that the decision is bound to a tamper-evident operational receipt the customer can verify later.
Reference Implementations
Each Tier 2 product is a proof the Receipt Engine works for a specific decision domain. The Receipt Engine itself is decision-domain-agnostic.
The framing rule: GeoClear is an operational-receipt platform for machine decisions. We’ve built the Tier 2 products as the blueprints for how we issue tamper-evident operational receipts in specific decision domains. If we can issue an operational receipt for a flood verdict, we can apply the same receipt architecture to other machine decisions.
Technical anchors
The Receipt Engine’s technical surfaces, for developer + procurement audiences who need the depth:
- Receipt VaultWhat the customer keeps; the portable evidence file layout.
- Key Transparency ArchivePublic verification material across four channels.
- location-trust.jsonUnified trust-substrate manifest for verifier scripts.
- Security architectureTrust-boundary diagram + receipt issuance + honesty disclosure.
- MCP protocol referenceHow autonomous agents call the Receipt Engine.
- Compliance briefAudit-heavy workflow surface.
What this Receipt Engine proves, and what it doesn’t
What this proves
- GeoClear signed this verdict at the receipt’s timestamp.
- The retained operational evidence matches the issued receipt.
- The retained verification material verifies the receipt.
- The receipt was not modified after signing.
What this does not prove
- That every upstream dataset was perfect.
- Full legal or regulatory compliance.
- That a downstream business decision was risk-free.
- That the physical world matched the recorded values.
This is the right boundary. The Receipt Engine makes the verification path verifiable on the customer’s terms without overclaiming what cryptography can prove about the world.
Try it
The Receipt Engine issues operational receipts for eligible GeoClear verdict responses across every public API surface, and produces receipts customers can retain. Three ways to see it:
Companion: Operational Receipts, the portable operational evidence the Receipt Engine produces. Together, the two Tier 1 products are the platform.