The full preconditions of each rules/review-severity.md carve-out, moved out of the always-loaded rule (#642). They bind as rule content: the rule keeps each carve-out's trigger line and requires reading its section here before relying on it. Each section carries only the moved detail; the trigger, applies-when and reset lines stay in the rule.

Judge-Weighed Finding Carve-Out

A weighing asks whether fixing a finding is worth its cost, never whether the finding is real
The ruling file follows the format the skills/release/dismiss-ruled-review.sh header names
The operator is the judge
The agent nominates a finding only when it sits on lines the previous fix push added, or with a cited reachability claim marking it marginal
The agent asks the operator one decision question per gate, carrying every nomination and its claim
The question never blocks the round
The agent keeps fixing until the answer arrives
No answer means fix
The agent records the answer verbatim as the ruling file
Preconditions (all required):
1. The ruling rules the finding defer or decline
2. The ruling file carries AUTHORITY: operator and quotes the operator's answer verbatim
3. The ruling names the finding at its HEAD:, and the finding's file is unchanged from that commit to the head
4. The finding is under no floor
5. The finding is entered in the task's follow-up issue citing the ruling, a decline labelled won't-fix
6. Every other release gate holds
Floors:
- a failing test, lint, diagnostic or required check
- a security or data-loss defect reachable by normal inputs
- a no-secrets or ci-safety finding
- a carve-out's unmet precondition
- an unmet acceptance criterion the operator stated
The judge rules fix on every floor
skills/release/dismiss-ruled-review.sh refuses the rule-id floors and a failing check
A ruling never skips, disables or removes a test
A gating policy review the ruling covers is dismissed per rules/ci-safety.md Judge-Ruled-Review Dismissal Carve-Out