fourteen-dimension-auditlisted

# 14-Dimension Codebase Audit ## Goal Turn a narrative audit into a numeric, comparable scorecard. Every run produces the same 14 dimensions; runs separated by time become deltas. Projects become comparable. ## When to use - **Baseline** — before starting a modernization program - **Target setting** — when defining the roadmap (what's the B-grade target?) - **Progress check** — monthly during a program (track deltas) - **Release gate** — at each major version (was this release a regression in any dimension?) Do NOT invoke mid-sprint (noise > signal) or on <2 weeks of changes (too few commits to move a dimension). ## Inputs - `repo_path` — absolute path to repo root - `rubric_file` (optional) — JSON or YAML rubric overriding default thresholds; falls back to built-in per-dimension rubric from `docs/runtime/audit-scoring-framework.md` - `weight_override` (optional) — JSON mapping dimension name → weight (default: equal weights for all 14) ## Outputs - `reports/current/audit-scorecard.md` — per-dimension 0-100 scores + narrative - `reports/current/audit-scorecard.yaml` — machine-readable scores for delta comparison - Target column (per dimension) + gap analysis + A-F grade - Recommended priority order for closing gaps ## The 14 dimensions 1. Architecture — layering, coupling, Strangler-Fig-migratability 2. Testing — coverage %, test types (unit/integration/E2E), flake rate 3. Secret management — key handling, rotation, pre-commit gitleaks 4. Observability — structured