Skip to content
Controlled coverage evidence · verified 16 Sep 2026
114/194 accepted · 80 fail-closed

114 sovereign countries passed the current four-module Risk Gate review census.

A controlled workflow evaluated all 194 enabled sovereign countries; 80 remained fail-closed. Missing or unverified inputs are not converted into approval, and every accepted result keeps execution_authorized=false.

Review Risk GateEvidence & limits

This evidence did not activate x402, real-money payments, Base mainnet or autonomous execution. Claim boundary: this is a dated controlled-workflow coverage result for the current Risk Gate methodology. It is not an all-country product guarantee, transaction authorization, production SLA, independent security audit or mainnet-launch claim, and it does not imply that every product is deliverable for every accepted country or request shape.

PRIVATE PILOT
Coming Soon for general access

Put a risk check between context and action.

Risk Gate verifies a signed country or corridor Risk Object, evaluates the current external-risk context and returns a bounded pre-decision recommendation before the customer's own system acts.

Controlled pilot only. Geomacro returns decision context; it does not sign, authorize or submit customer transactions.

Possible Risk Gate outputs

01

CONTINUE

02

REDUCE_LIMIT

03

REQUIRE_APPROVAL

04

PAUSE

execution_authorized = false

The customer keeps identity, permissions, policy enforcement and final execution.

How it works

Four bounded steps. No hidden execution authority.

01

Verify

Validate object signature, integrity and freshness.

02

Evaluate

Read current risk, change, confidence and relevant drivers.

03

Apply policy

Evaluate the caller-supplied policy profile against the bounded context.

04

Return

Return one controlled recommendation with an auditable decision record.

Private Pilot scope

Country and directional-corridor context only.

Current Private Pilot scope is country and directional corridor risk. Geomacro supports directional corridors composed from endpoints plus eligible bilateral evidence.

Full physical-route and counterparty modelling are not claimed. Event-specific Risk Objects remain a broader product direction rather than part of the current pilot contract.

Trust model

A gate should fail safely when context is weak.

Verifiable object

Signed, versioned Risk Objects preserve integrity, freshness and methodology context.

Fail-closed

Missing, stale, malformed or commercially ineligible required context cannot silently become approval.

Auditable response

The recommendation is designed to be correlated with the exact risk context used by the caller.

Machine boundary

Built to sit inside a customer-controlled workflow.

Geomacro evaluates external-risk context. The customer still owns the identity, permissions, compliance, funds and final action.

subject + action context
↓
verified Risk Object
↓
risk + delta + confidence + drivers
↓
CONTINUE / REDUCE_LIMIT / REQUIRE_APPROVAL / PAUSE
↓
customer-controlled action

Design partners

Have a workflow that should stop, slow down or require review when external risk changes?

Bring the action, subject, required freshness and policy boundary. We will map it to the current pilot scope before any integration commitment.

Discuss a pilot