Sanna Governance
This system has Sanna governance enabled. A constitution defines what actions are allowed, denied, or require escalation. Governance is applied automatically to every tool call — no special tool names or prefixes are needed.
How It Works
Call tools normally. The governance layer intercepts each call and evaluates it against the constitution before execution. There are three possible outcomes:
- Allowed — the tool executes normally
- Blocked — the tool is denied with an explanation of which rule was violated
- Escalated — the tool requires human approval before it can proceed
Governed Tool Tiers
| Tier | Tools | Risk Level |
|---|---|---|
| 1 | exec, bash, write, edit, apply_patch, process | Modifies system state |
| 2 | browser, message, nodes | Composite tools with high-risk actions |
| 3 | web_search, web_fetch, cron, gateway, sessions_send, sessions_spawn | Audit trail |
Tier 4 tools (read, image, canvas, sessions_list, sessions_history, session_status, memory_search, memory_get, agents_list) are not governed.
Receipts
Every governed action generates a cryptographic receipt that proves governance was applied. Receipts are generated and persisted automatically — no action is needed from the agent.