Repository navigation
[suite] [improvement] land the thread's delta from the last implement step instead of at close #72
Closed as not planned
Description
Consider applying the delta of the ADRs and glossary by the last implement skill task / step, instead of leaving it to close-thread.
Two things stand in the way and need settling. A thread can hold several implementations, so "last" has no definition today. And the implement skills' write boundary explicitly excludes docs/adr/, docs/glossary.md, and the thread's own adr/ and glossary.md. If the delta lands earlier, what closing still means also has to be decided, since the glossary defines it as the operation that lands the delta.
Activity
Jei-sKappa commentedon Sep 17, 2026
Not planned. Landing the thread delta from an implementation step would make an undefined “last implementation” responsible for project-level changes while the thread is still open. That is likely to cause bad behavior, including landing incomplete or later-superseded decisions. Keeping delta landing in close-thread preserves a single explicit lifecycle boundary.