Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list

2026-10-16 20:51:00 +02:00
parent 222fbe95f4
commit 3c49b389d1
2 changed files with 8 additions and 3 deletions
@@ -35,7 +35,10 @@ reported and left.
   items as listed? The likely-safe and unknown items are separate questions, item by item when few.
 4. **Delete only the approved list**, each with the command that refuses an unsafe case (a worktree removal
   that refuses a dirty one, a branch deletion that refuses an unmerged one). A refusal is reported, never
-   forced.
+   forced. The operator approves a deletion on a channel that proves who answered, as an ask bound to that
+   exact list and carried out on the warrant (ADR 0387, design 58 milestone 7, issue 884). Until that is built,
+   an agent session's permission check refuses these deletions, and the approved list is handed to the
+   operator to run.
 5. **Report**: what was cleaned, what was kept and why, what was unknown, what the operator kept, and the
   missing tools, each opened as an issue (`issue-tracker.open`) or added to an existing one.