Independent Verification Layer

Proof that an agent did what you approved.

Companies need evidence that an AI agent completed the right task—not just a message saying it succeeded. Proviso captures explicit conditions, routes tool calls through a signed gateway, and independently verifies the resulting state.

  1. 01 Approved proviso
  2. 02 Auditable gateway
  3. 03 Independent check
  4. 04 Signed verdict

The Approach

Don’t rely on the agent’s own account.

If a verifier trusts the agent’s transcript, the agent can fabricate both the action and the outcome. Proviso separates execution from verification across two complementary checks.

01 · Auditable Execution

Controlled Tool-Call Gateway

Agent tool calls pass through a Rust gateway that holds provider credentials—the agent never sees them. Every request and response is canonicalized (RFC 8785 JCS), signed with Ed25519, and checkpointed to an append-only witness before dispatch.

  • Refuses calls that violate signed conditions before execution
  • Idempotency keys prevent silent duplicate actions on retry
  • Optional AWS Nitro Enclave attestation binds keys to measured builds
02 · Independent Outcome Check

Separate State Verifier

After execution, the verifier independently queries the external system—booking API, blockchain state, or payment processor—using its own read credentials to confirm the resulting state exists and matches every approved condition.

  • Model-independent: keep whichever LLM or agent framework you use
  • Deterministic evaluation of explicit, reviewable conditions
  • Offline verification CLI checks signatures and witness chains directly
user ── approves ──► conditions (explicit, reviewable, signed)
                          │
agent ── tool call ──► gateway ──► provider API
                          │  records request + response (signed, attested)
                          ▼
                     verifier ──► independent read of provider state
                          │
                          ▼
              verdict: verified | failed | unresolved
              (conditions, evidence, sources, observation times)
Provider credentials and signing keys stay outside the agent and outside the operator console.

Honest Evidence

Three explicit verdicts. Never a guess.

Every verification record states what was checked, the evidence source, and when it was observed. A payment confirmation does not prove delivery—uncertainty is surfaced explicitly.

verified

All Conditions Matched

Every approved condition was deterministically evaluated against independently observed provider state, with a valid signed gateway receipt and witness checkpoint.

failed

Mismatch or Policy Violation

The observed state contradicted the approved conditions—wrong amount, non-refundable rate, duplicate execution, or an unauthorized tool call blocked at the gateway.

unresolved

Missing or Conflicting Evidence

Timeouts, incomplete provider confirmation, or restart recovery after dispatch produce unresolved with a recheck path—never a false success claim.

What’s Built

Modular infrastructure, verified end to end.

Proviso is developed in the open as a Rust core paired with a Cloudflare edge control plane, MCP integrations, and AWS Nitro Enclave deployment components.

Rust Gateway, Witness & Verifier

Signed top-level tool-call receipts, SQLite journal, encrypted local and remote witness checkpointing with fork rejection, and a standalone offline verifier.

Rust · Ed25519 · ChaCha20-Poly1305 · RFC 8785 JCS

Cloudflare Console, CLI & MCP

Operator console backed by Durable Objects, noninteractive CLI, stdio and Streamable HTTP OAuth MCP server, scoped organization tokens, and a read-only durable evidence assistant.

Cloudflare Workers · Durable Objects · MCP SDK

AWS Nitro Enclaves & KMS

Isolated gateway execution with no interactive shell or persistent storage. KMS releases provider credentials and TLS private keys only to enclaves matching approved PCR measurements.

AWS Nitro · KMS Attestation · Mutual TLS

Modal Sandbox Bridge

Supported Modal SDK bridge and experimental gRPC adapter for trusted sandbox execution, caller-only key signing, and public-key grant issuance.

Modal · Caller-Only Signing · Model-Agnostic

Development status: 120 automated tests pass across the Rust gateway, Cloudflare console/MCP, enclave, and Modal bridge suites. Live AWS Nitro/KMS hardware attestation and live Modal execution are currently in pilot validation.

Quickstart

Run the offline verification demo.

Generate a signed tool-call bundle with the fixture provider and verify it independently—no cloud credentials or external resources required.

Terminal · Rust stable
git clone https://github.com/iqlusioninc/agent-verification.git
cd agent-verification
cargo run -- demo --output demo-output
cargo run -- verify --bundle demo-output/bundle.json --trust demo-output/trust.json --allow-unattested