Simplify Codebase

Reduce the number of concepts and obligations a codebase must keep coherent. Line-count reduction is supporting evidence, not the objective. A successful run may conclude that the inspected surface is already justified.

Use the loaded CONTEXT terminology and RULE. If they have not been loaded, follow the project-knowledge protocol; continue and disclose the limitation when project knowledge is unavailable.

Select mode and scope

First choose the authority mode:

• Survey for simplification audit, investigation, or candidate-finding requests. Remain read-only and return ranked evidence.
• Change for explicit simplify, remove, consolidate, refactor, or repository-documentation edit requests. Prove each cut, implement it within the authorized scope, and validate the surviving contract.

Then choose the coverage scope:

• Focused when the user names a subsystem, symbol, state machine, dependency, or suspected duplication. Cover that boundary thoroughly before expanding outward.
• Broad when the request spans the repository or asks for multiple candidates. Partition the system and account for every in-scope domain.

Deleting a reachable capability, supported interface, stored representation, or compatibility path is a product decision. Describe the consequence and obtain direction unless the user has already chosen it.