loom-architecture-deepeninglisted

# loom-architecture-deepening Architecture deepening is a refactoring-shaping playbook. It looks for places where a better module interface can hide more behavior, improve locality, and make tests and future agent work easier. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-codebase-atlas`, `loom-domain-language-and-decisions`, `loom-code-simplification`, `loom-api-and-interface-design`, `loom-specs`, `loom-plans`, `loom-tickets`, `loom-evidence`, and `loom-audit`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. It proposes and shapes refactors. Execution still belongs in tickets and evidence. ## Use This Playbook When Use this playbook when: - understanding one concept requires bouncing through many small modules - a module's interface is nearly as complex as its implementation - tests reach past interfaces into implementation details - pure helpers were extracted for testability but bugs live in orchestration - callers repeat the same policy, ordering, validation, or error handling - an interface change could concentrate behavior and improve leverage - the operator asks for architecture improvement rather than local cleanup Skip it for simple readability cleanup that `loom-code-simplification` can handle. ## Route Use this route: ```text atlas -> candidates -> select -> design seams -> plan tickets -> execute via implementation -> verify