Tech Debt

Overview

Two complementary stances on technical debt, picked apart by the router in this file:

• Mode A — Prevent: while you're making a change, rework it toward the intended end state. Delete the dead compatibility path instead of preserving it.
• Mode B — Triage: while you're assessing existing code, categorize, score, and prioritize the debt into a remediation plan.

They run at different points in a debt's lifecycle: prevent when writing, triage when planning. Triage output feeds back into prevent, one item at a time.

When to use

Use Mode A when:

• You are implementing, finishing, or reviewing a feature / fix / refactor and the user wants the change clean.
• You're about to keep a fallback, alias, mode flag, or wrapper "just in case" — check it has a caller first.
• The user says "do this properly", "no bandaids", "zero tech debt", or "don't leave a mess".