Curia’s autonomy engine gives you a single dial to control how independently your AI team operates. A score from 0 to 100 determines whether Curia acts on its own, asks before acting, drafts without sending, or sticks to pure advice. The score applies across all agents, channels, and skills — one setting, consistent behavior everywhere. You can read it or change it at any time with a plain-English instruction.Documentation Index
Fetch the complete documentation index at: https://docs.meetcuria.com/llms.txt
Use this file to discover all available pages before exploring further.
The five autonomy bands
The score maps to one of five named bands. Each band has a precise behavioral description that is injected into the Coordinator’s system prompt on every task, so Curia self-governs in real time — no restart required.| Band | Score range | Behavior |
|---|---|---|
| Full | 90–100 | Acts independently. No confirmation needed for standard operations. Flags only genuinely novel, irreversible, or high-stakes actions where the cost of pausing is justified. |
| Spot-check | 80–89 | Proceeds on routine tasks. Notes consequential actions — sending email, creating commitments — in its response so you maintain visibility without being asked. |
| Approval Required | 70–79 | Presents a plan and asks for explicit confirmation before any consequential action. Routine reporting, summarization, and information retrieval proceed without approval. |
| Draft Only | 60–69 | Prepares drafts, plans, and analysis but does not send, publish, schedule, or act without an explicit go-ahead. Surfaces work for your review; execution requires a direct instruction. |
| Restricted | < 60 | Advisory only. Presents options and analysis. Takes no independent action whatsoever. Every step with an external effect requires an explicit instruction from you. |
Curia defaults to 75 (Approval Required) on first deployment. This is a conservative starting point — Curia confirms before taking consequential actions until you decide to extend more independence.
Checking your current score
You can ask Curia about its autonomy score from any channel using plain language: Example response:Changing your score
Score changes take effect immediately on the next task — no restart required. The Coordinator loads the current score from Postgres at the start of every task, so a change you make mid-session applies on the very next action.How to calibrate your score
A practical approach for new deployments:Start at 75 (the default)
Approval Required means Curia asks before sending anything or making commitments. This gives you full visibility into what it would do without any risk of surprises.
Watch it work for a week
Pay attention to which confirmations feel unnecessary. If Curia is asking about things you always say yes to, your score is too low for your comfort level.
Move to 80–85 when you're comfortable
Spot-check lets Curia proceed on routine tasks while still noting consequential actions in its responses. You stay informed without being interrupted.
Autonomy engine mechanics
How action_risk levels, execution gates, and automatic score adjustment work under the hood.
Security overview
Understand the broader governance and audit framework Curia operates within.