Resources for operational evidence and AI action verification.
Guides, demos, and technical explainers for teams evaluating verification layer, customer-held evidence, local verification, and verification-before-acceptance workflows.
Start here.
Four entry points for buyers, architects, and reviewers.
How GeoClear verifies whether an action followed the approved evidence path before acceptance.
Documentation landing covering the core concepts: operational evidence, verification layer, evidence bundles, local verification, policy modes.
Plain-English guide to the operational evidence packet: actor, action, policy reference, evidence commitments, approval state, signature, verification result.
Trust boundaries, claim boundaries, and the line between cryptographic evidence and ground-truth certification.
Architecture & trust.
Public-safe walkthroughs of the evidence layer, verification model, and deployment patterns.
A walkthrough of the evidence layer, customer-held evidence, local verification, and deployment modes.
Why evidence must outlive the API call, and how customers can verify later without relying on GeoClear application servers.
What a customer-held evidence bundle contains, how it supports audit, and how it can be verified offline.
Customer-computed (Mode C), minimized evaluation (Mode B), or customer-controlled boundary (Mode A). Different policy locations, same evidence packet, same verification path.
Trust boundaries, customer-held verification material, and the local verification model.
Demos & samples.
Run the interlock locally and download sample artifacts.
See one action produce four outcomes: valid evidence accepts, missing evidence holds, policy violations block, tampered evidence rejects.
Change one byte in an issued evidence packet and watch local verification reject the tampered evidence.
Download sample bundles and verify them locally. Same customer-held format used in production.
Dedicated offline verification utility. No live GeoClear application call required.
Solution briefs.
Where operational evidence applies, by action type.
verification layer for tool calls, autonomous agents, and MCP-compatible workflows.
Operational evidence for approvals, payments, procurement, finance, and administrative workflows.
Evidence before model-generated observations enter downstream review, routing, or workflow systems.
Evidence-required route, dispatch, custody, geofence, and handoff workflows.
Customer-held operational evidence for mortgage, insurance, fintech, audit, and compliance-heavy workflows.
Developer & evaluator access.
Detailed schema, package instructions, verifier internals, and deployment-specific material are available through approved evaluator access.
Exact schema, verifier internals, and integration recipe for qualified engineering evaluators.
Single-team pilot environment with developer-preview access to the verification layer.
Private workspace for managing evidence projects, developer access, and deployment requests.
Cryptographic substrate, key-management posture, and procurement review materials under NDA.
Writing.
Long-form positioning + category essays.
Start with the demo. Then ask for the deep dive.
The verification layer demo shows the pattern in motion. After that, the architecture brief covers the substrate, deployment modes, and what gets sent vs. stays with the customer.