Explicit authority
Every AI request runs at an authority level: observe, propose or execute. The effective level is the lowest of what was asked, what the job allows and what policy permits.
AI governance
In SuNodes, an AI being able to do something, being allowed to do it, and actually doing it are three separate things, each decided outside the AI. Here's how that works, and how it shows up when you build and run an agent.
Three separate questions
Capability. What a tool technically does: read your website's analytics, draft a reply, publish a change. Each is described with its effect: read, propose or execute.
Permission. Whether this agent, for this job, is granted that capability. Grants are derived by policy from the job you approved, never written by the AI.
Execution. Whether this specific action runs. Policy checks it again at that moment; anything sensitive waits for your approval of exactly that action.
Example: an agent can be capable of sending email, permitted only to prepare drafts, and so never execute a send at all.
How a decision is made
The rules
These rules are built into how every AI Agent in SuNodes works.
Every AI request runs at an authority level: observe, propose or execute. The effective level is the lowest of what was asked, what the job allows and what policy permits.
Before an agent exists, you see in plain words what it can read, what it can do and what needs approval. The review is pinned: if the agent's job changes, it has to be reviewed again.
An approval is tied to one action with its exact inputs, expires, and can be used once. An agent can never approve its own work.
No agent may delete a website, change domain ownership or settings, or buy services and spend money, whatever it's told.
An agent's first run is a test that reads for real but only checks its actions; it runs on its own only after passing.
Each agent has a monthly credit limit that pauses it when reached, and any agent can be paused at any time.
Not everything asks first
Approving every small step would make agents useless, so low-risk work runs once it's permitted. What counts as sensitive is fixed by policy, not chosen by the agent.
Traceable and revocable
Each agent run shows its steps and what it did; decisions are recorded in your activity log. AI records keep fingerprints and short previews of inputs rather than full prompts.
Turn off a permission, pause an agent, remove its mailbox access or disconnect a service to take that access away. Mail access is checked again at every step an agent takes.
Use SuNodes's managed AI, or your own provider key. Your key is never swapped for ours behind your back, and ours never falls back to another provider silently.
Where this comes from
SuNodes is a product of Tavri, Inc., whose work focuses on governed AI execution. The governance described on this page is what's built into SuNodes; Tavri's wider research and technology aren't all part of SuNodes, and this page only describes what is.
Hire an agent for one job, review exactly what it may do, and approve what matters.