Repository navigation
Decide the exception policy for a MUST rule #2128
Description
Part of #2124.
The rule language defines what MUST means, then allows exceptions three different ways. An agent meeting a MUST it cannot meet does not know whether to stop, write a rationale, or ask. Output: one exception policy.
| Where | What it says |
|---|---|
core/docs.md:15 |
MUST: "Absolute requirement; no exception without stated rationale" |
core/docs.md:16 |
MUST NOT: "Absolute prohibition", with no exception clause |
core/review.md:146-147 |
a deviation from a MUST needs a designated approver's sign-off before it lands |
The three disagree on whether a MUST is absolute, waived by a rationale, or waived by an approver. MUST and MUST NOT disagree with each other too.
Done when
- One exception policy is decided: who may waive a MUST, and what the waiver records
-
core/docs.md, "Rule language", andcore/review.md, "Deviations", state it the same way
Activity
[-]Decide how an agent ranks a plain imperative against a tagged MUST[/-][+]Decide the exception policy for a MUST rule[/+]braboj commentedon Oct 23, 2026
Decided: a MUST or MUST NOT deviation lands only with a designated approver's sign-off and its reason recorded in the PR. An agent never waives one itself; it stops and asks.