anti-entropy-governance

1# Anti-Entropy
2 
3## Overview
4 
5Use this skill when the task is not merely "change code" but "remove old paths
6safely without growing entropy".
7 
8This skill chooses between:
9 
10- `delete-first` for internal code retirement
11- `compat-exception` for proven external dependency boundaries
12- `confirmation-first` for irreversible state or an external contract whose
13  distributed consumers cannot be observed
14 
15It does not replace `brainstorming`, `writing-plans`,
16`systematic-debugging`, or `verification-before-completion`. It is a narrow
17governance owner for retirement, fallback collapse, duplicate-owner cleanup,
18and deletion safety.
19 
20## When to Use
21 
22Use when any of these are true:
23 
24- old logic, duplicate owners, or stale fallbacks should be retired
25- a candidate fix is "delete old path" vs "add another fallback"
26- internal keyword / phrase / trigger logic is being replaced by structured logic
27- a new canonical owner exists and the old owner may still carry real behavior
28- a cleanup, migration, or deprecation task touches schema, persistence,
29  source-of-truth, or external compatibility boundaries
30- the task risks confusing code retirement with live data deletion
31 
32Do not use for:
33 
34- pure additive feature work with no retirement decision
35- tiny wording edits
36- simple status or read-only Q&A
37- normal bug fixes that do not involve owner collapse, fallback cleanup, or
38  deletion choice
39 
40## Auto-Compose Boundary
41 
42This skill should be composed by other owners. It should not become a new
43…