architecture-compass

# Architecture Compass ## Required Skills Read, apply: 1. `framework:knowledge-priming` -- Load codebase context: language, framework, structure, conventions (always) 2. `framework:architecture` -- Architectural audit lens and recommended direction guardrails (always) 3. `framework:domain-driven-design` -- Strategic DDD only: bounded contexts, domain seams (conditional: only when domain complexity warrants it) 4. `framework:collaborative-judgment` -- Surface judgment calls during co-design rounds (always) ## Workflow ### Step 1: Load Existing Context **Check for an existing insights document first.** If `.lattice/insights/architecture.md` already exists: - Read it. Check the Session Status table using these three states: - `pending` — row exists, no content written yet - `in-progress` — content exists in the section but no agreed date recorded - `✅ agreed` — content exists and date is recorded - Resume from the earliest `pending` or `in-progress` phase. For `in-progress` phases: present the existing content for re-confirmation rather than regenerating it. - **In-progress without content:** If Current Architecture is `in-progress` but the document has no Current Architecture content (the previous session's scan context was lost), re-run Step 2 scan before presenting. - **Staleness check:** If the most recent `✅ agreed` date in the Session Status table is older than 30 days, run a lightweight re-scan (Steps 2.1 and 2.6 only — tree + imports). If material structural ...