docs
Contents
Concepts

Autonomy levels

How much runs without you. Merge and publish always stay with a person.

LevelWhat happensAvailability
Review everythingEach change waits for a person to approve its exact versionAvailable
Run low-riskLow-risk changes are approved by policy; the rest wait for a personIn progress
Run allAll classified changes are approved by policyIn progress

A policy approval is recorded as the policy, never as a person, and is bound to the proposal's hash. CMS schema changes and proposals from an external agent always need a person, at every level.

Next: Plans and credits