Aliases: policy change; implementation replacement; authority expansion; compatibility; migration; retirement; repository protection.
Distinguish replacement of machinery, representation changes, changes to promised behavior, authority expansion, consumer compatibility and migration of outstanding work. One impl may admit a new permission; many edits may preserve the commitment. Classify by consequence, not line count.
Use the accountable owner's actual mandate and the project's workflow. Do not invent a new approval ceremony for already authorized implementation. Make changes to governing commitments explicit to their owners. Appropriate repository protections and review scope must protect the governing boundary and its enforcement; an instruction file cannot substitute for those mechanisms.
Retiring a story requires a decision about existing consumers, history and outstanding obligations. Preserve neither a bad abstraction nor unnecessary documentation merely because they have accumulated. Deliberate resistance belongs in the meaningful commitment; repeated synchronization of redundant interpretations does not.
Your Reflection
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.