From 9c9a5aece979bffae063306d8c4dbe26d7a9e58c Mon Sep 17 00:00:00 2001 From: Sinity Date: Sun, 23 Aug 2026 15:00:18 +0200 Subject: [PATCH] docs(agent): record deferred-scope closure discipline Problem: deferred acceptance scope was previously closed without a\nstructured successor link, leaving repair work discoverable only through\nbacklog archaeology.\n\nWhat changed: document the close-time successor requirement and preserve\njudgment-based enforcement rather than pattern-matching close-reason prose.\n\nRef polylogue-aagkt. --- .agent/CONVENTIONS.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.agent/CONVENTIONS.md b/.agent/CONVENTIONS.md index a74adc6dce..35e5d95ebe 100644 --- a/.agent/CONVENTIONS.md +++ b/.agent/CONVENTIONS.md @@ -68,6 +68,14 @@ substep is a checkpoint, not a publishing trigger; split only at a genuine boundary (risk, reviewability, dependency, ownership, deployment, or failure isolation). +## Deferred Scope at Closure + +When closing a Bead while any acceptance criterion, root cause, or repair scope +remains deferred, create the successor Bead first and link it with a structured +`related` or dependency edge in the same batch. The close reason must name that +successor. Review this as a judgment call at close time; do not add a lint or +gate that pattern-matches close-reason prose. + ## Scratch, Demos, Git Boundary `.agent/scratch/` is gitignored thinking space (README + research notes);