Trust and Scope

What we govern, what we only see, and what is outside our reach.

A control is only as useful as its stated limits. These are ours.

OUTSIDE SCOPECommands a person types by handRuntimes not connected to Atbash
OBSERVABLE ONLY · DETECTED AND FLAGGEDAgent-generated shellGitPythonDirect browser activity
GOVERNED · VERDICT BEFORE EXECUTION
Send a messageModify a fileDelete a documentCall an external APIInitiate a paymentChange a settingPost publiclyTrigger an automation
Tool calls routed through an Atbash integration.
In plain words

What Atbash sees, keeps and never asks for

01 · WHAT IT SEES

The action at the hook

The agent's identity, who it acts for, the tool it is calling with its arguments, and the context the integration sends, all before the call runs.

02 · WHAT IT KEEPS

Records and certificates

Verdict Records and Agent Certificates, written to an append-only ledger, so no one can quietly edit or delete them later.

03 · NEVER ASKS FOR

Your secrets

No seed phrases, no private wallet keys, no secrets in a certificate. Key metadata only.

04 · FAILING SAFE

No verdict, no execution

In fail-closed mode, a call that gets no verdict does not run.

05 · YOUR CONTROLS

Your judge, your telemetry

Bring your own judge endpoint. Switch telemetry off with one config file.

06 · WHERE IT RUNS

Your choice of deployment

Atbash cloud, your cloud, a private subnet or on-premises.

Questions about scope? Ask us directly.