Authority rules are diffable
0dai init scaffolds agent-authority.yaml so review boundaries live beside code instead of inside a private chat thread.
for platform and SRE
0dai gives platform owners a repo-owned control plane for agent changes: authority rules in ai/, receipts for review, audit trails for merge decisions, and clear boundaries for what needs Enterprise review.
operating controls
0dai init scaffolds agent-authority.yaml so review boundaries live beside code instead of inside a private chat thread.
Agent work can leave a task receipt, proof link, issue reference, and quality artifact before it reaches the merge queue.
Team rollout copy is grounded in RBAC, audit logs, and admin controls; SSO/SAML and custom security terms stay Enterprise.
live vs enterprise
Platform teams can start with Team for governed shared workflows. Larger rollouts, SSO/SAML, audit export, dedicated success, and custom security terms stay in the Enterprise path.
Session roaming starts as ai/sessions/active.json. Cross-machine sync and shared graph history remain planned unless the status page says otherwise.
SSO/SAML and custom terms are not self-serve Team claims. They belong to Enterprise and contact-sales review.
The operating model is governed-merge coverage: every serious change should carry authority, review, and audit evidence.
audit proof
These are the same public product boundaries used by pricing and status copy: current Team governance, current receipt proof, and Enterprise-only security commitments separated from roadmap work.
Govern the first repo before you scale the rollout.
Start with Team controls; route Enterprise security needs through contact sales.