← Products
Tier 1 · The Platform · The Engine

GeoClear™ Record Engine.

Policy-bound Authorization and Denial operational evidence records issued at execution time. Customer-side enforcement, customer-held evidence, offline verification.

How the signing works → Connect over MCP Verify a record
verification layer flow Six-stage diagram: an actor proposes an action; the evidence path is checked against policy and approvals; an evidence packet is issued; the evidence travels with the action; the receiving system verifies before accepting; the customer retains the evidence for later audit and review. Action proposed an agent, human, workflow, tool, or system proposes an action 01 Evidence path checked policy, approval, and evidence requirements are evaluated 02 Evidence issued an operational evidence packet is issued 03 Evidence travels the record accompanies the action request 04 Receiving system verifies accepts, holds, rejects, or escalates 05 Customer keeps evidence retained for audit and later review 06 verification layer flow Six-stage diagram: an actor proposes an action; the evidence path is checked against policy and approvals; an evidence packet is issued; the evidence travels with the action; the receiving system verifies before accepting; the customer retains the evidence for later audit and review. Action proposed an agent, human, workflow, tool, or system proposes an action 01 Evidence path checked policy, approval, and evidence requirements are evaluated 02 Evidence issued an operational evidence packet is issued 03 Evidence travels the record accompanies the action request 04 Receiving system verifies accepts, holds, rejects, or escalates 05 Customer keeps evidence retained for audit and later review 06
Action → policy + evidence check → operational evidence record → target verifies → customer audit.

What the Record Engine does

The Record Engine is the horizontal layer underneath every product GeoClear ships. For eligible GeoClear verdict responses:

The issuance substrate is decision-domain-agnostic: the same trust boundary issues operational evidence records for an address verification, a flood determination, a credit decision, or an autonomous-routing verdict. The Record Engine doesn’t care what the decision is, it cares that the decision is bound to a tamper-evident operational evidence record the customer can verify later.

Reference Implementations

Each Tier 2 product is evidence the Record Engine works for a specific decision domain. The Record Engine itself is decision-domain-agnostic.

Tier 2 · Record Profile Location Record Profile Real-time presence evidence for physical-world systems (drone, logistics, IoT). Tier 2 · Record Profile Flood & Census Record Profile Wedge for mortgage. NFIP-aligned flood determination. Tier 2 · Record Profile Decision Record Profile Operational decision records for credit, underwriting, and AI-driven Yes/No.

The framing rule: GeoClear is an operational-evidence-record platform for machine decisions. We’ve built the Tier 2 products as the blueprints for how we issue tamper-evident operational evidence records in specific decision domains. If we can issue an operational evidence record for a flood verdict, we can apply the same record architecture to other machine decisions.

Technical anchors

The Record Engine’s technical surfaces, for developer + procurement audiences who need the depth:

What this Record Engine verifies, and what it doesn’t

What this verifies

  • GeoClear issued this verdict at the record’s timestamp.
  • The retained operational evidence matches the issued record.
  • The retained verification material verifies the record.
  • The record was not modified after issuance.

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 matched the recorded values.

This is the right boundary. The Record Engine makes the verification path verifiable on the customer’s terms without overclaiming what cryptography can verify about the world.

Try it

The Record Engine issues operational evidence records for eligible GeoClear verdict responses across every public API surface, and produces records customers can retain. Three ways to see it:

Verify a live record → Download a sample bundle Try the API console

Companion: Operational Evidence Records, the portable operational evidence the Record Engine produces. Together, the two Tier 1 products are the platform.

GeoClear issues operational evidence records for AI actions, tool calls, and workflow decisions. The evidence bundle is tamper-evident, and verifiers detect modification. GeoClear does not provide legal certification and does not verify the real-world truth of upstream data sources.