RESOURCES
Bounds, approvals by named roles, pinned versions, and the run record.
Articles in Governance
- Governance
The run record and what it holds
Every run on Czar leaves a record: what went in, what each step did, whether policy allowed it, and who approved. It stays on the appliance and an auditor can read it.
· 4 min read
- Governance
What the admin decides
The admin sets the outer limits for every agent at the site: which models exist, who may publish, which systems are tools. A new capability is an administrative decision first.
· 4 min read
- Governance
One live version at a time
A stable address points at exactly one published version. There is never a question of which agent is running, and going back is a matter of pointing the address elsewhere.
· 4 min read
- Governance
Approvals by named roles
When an agent waits, a reviewer approves or stops, and the decision carries that person's name. Approval on Czar is a role with a record, not a button anyone can press.
· 4 min read
- Governance
Bounds written into the version
An agent's limits are not settings that can drift. They are part of the published version: which models, which material, which tools, where it waits, what it may never do.
· 4 min read