ripwire-layers

# Layers with ripwire > Nearest neighbours: > • You want the file→file dependency graph itself (not a health read) → `--deps` is step 2 below, or > go straight to it if you already know you want godfiles/cycles. > • Reviewing YOUR OWN diff for coupling risk, not a repo-wide sweep → **ripwire-change-check**. > • Unfamiliar subsystem, general risk sweep (not architecture-specific) → **ripwire-fresh-eyes**. Trigger: you want a factual picture of architectural health before a large refactor, or you're reviewing whether the codebase is trending toward or away from clean layering. `<dir>` = repo root. Every metric below has a NUMBER → THRESHOLD → ACTION — don't stop at reporting it. 1. **Layering rules** (if a rules file exists) — `ripwire <dir> --arch=rules.txt` Output: `<arch>` with violations listed by layer pair and file. Exit 2 = NEW violations found (CI gate). If no rules file exists yet, this step is the prompt to write one (grammar: `layer NAME = substr…`, `deny FROM -> TO`, `allow FROM -> TO`; `#` comments). **Action**: every violation is a concrete edge to either fix (remove the dependency) or explicitly `allow` (document why it's intentional) — don't leave it silently baselined forever. **Adopting rules on a codebase with existing debt** — the baseline workflow: - `ripwire <dir> --arch=rules.txt --baseline` — accept every CURRENT violation as known debt: writes a `.ripwire_arch_baseline` sidecar in the CWD (commit it), exits 0. - From ...