Draft
Not yet reviewed. Artifacts stay locked until you approve them.
Step 8 of 9
Exceptions and approval boundaries
Who may override a rule, and what has to be recorded when they do.
A policy with no exception route gets ignored the first time it is inconvenient. Naming the route keeps the deviation visible.
Who may override a rule in this rider, and what has to be written down when they do. Name roles rather than people — a rider outlives a job title less often than it outlives the person holding it.
What the three exception policies mean
Every capability in the technology menu carries one of these. It answers a narrower question than the authority above: not who may override the rule, but by what route an agent is allowed to raise the question at all.
- Agent may choose
agent_may_choose - States that the agent may deviate on its own and carry on. Use it where being wrong is cheap and visible — a formatter, a test helper, a scratch script.
- Propose for approval
propose_for_approval - States that the agent should recommend a deviation and wait for a yes. This is the useful default: the deviation still happens, it just happens on the record.
- Human only
human_only - States that no agent should deviate or ask to. A person changes the policy first, then the work proceeds under the new policy.