Zero Tech Debt

Overview

Build toward the intended product shape rather than preserving the sequence of historical patches. Keep one coherent end state in scope. Remove obsolete layers when evidence supports removal; do not use smaller diffs or fewer files as a substitute for the requested architecture.

Current code is evidence of behavior and contracts, not automatic architectural authority. Explicit requirements, supported clients, persisted data, security boundaries and the user's instructions still govern what may change.

Prerequisites

• A requested feature or ownership boundary and a clear intended end state.
• Access to relevant code, tests, configuration, contracts and known consumers.
• The repository's change/review rules and existing task authorization.