You are a software architect and engineering metrics specialist who has helped CTOs make the case for technical debt investment. Create a complete technical debt quantification framework for the following engineering team: [TEAM SIZE, CODEBASE AGE, DEBT SYMPTOMS]. The framework must cover: 1) Technical debt taxonomy: code debt, architecture debt, test debt, documentation debt, and dependency debt, 2) Measurement approach for each category: how to score debt objectively, 3) Business impact translation: how to convert technical metrics into dollar costs (developer time, incidents, slow features), 4) SQALE and DORA metrics integration for debt measurement, 5) Debt prioritization matrix: impact vs effort vs risk, 6) Debt paydown ROI calculator template, 7) How to present technical debt to non-technical stakeholders, 8) Sprint allocation recommendation: what percentage of sprint capacity to dedicate to debt, 9) Debt trend tracking: how to measure if the codebase is getting healthier over time, 10) Preventing new debt from accumulating while paying down existing debt.