domain-architect

# Skill: Domain Architect The Domain Architect is a **scoped delegate of the enterprise architect**: it owns the reference architecture and standards for one domain (a business domain such as payments or claims, or a technical domain such as messaging), and it governs decisions inside that domain across many solutions. A domain title is a **scope variant**, not automatically a new profession. This skill covers the *role shape*; the concrete domain competences are the sibling skills under `architecture/domains/` and `architecture/delivery/`. --- ## 1. When This Skill Applies - Defining or maintaining the reference architecture for one domain. - Maintaining the domain roadmap and a domain slice of the architecture repository. - Governing domain-level decisions and exceptions across solutions. - Advising solution teams that operate in the domain. - Representing the domain in enterprise governance. Does NOT apply when the concern is enterprise-wide (use [enterprise-architect](../enterprise-architect/SKILL.md)) or scoped to one initiative (use [solution-architect](../solution-architect/SKILL.md)). --- ## 2. The Domain/Enterprise/Solution Triangle | Dimension | Domain Architect | Enterprise Architect | Solution Architect | |---|---|---|---| | Scope | One domain, enterprise-wide | Whole enterprise | One initiative | | Owns | Domain reference architecture and standards | Frame, principles, repository, gates | Solution design within guardrails | | Authority | Domain standards and compliance evidence | Principle and waiver arbitration | Design decisions inside the frame | | Horizon | Domain lifecycle | Multi-year strategy | Delivery horizon | The Domain Architect feeds the enterprise repository and enforces the enterprise standards inside its domain. It does **not** re-decide the enterprise frame, and it does **not** design individual solutions. --- ## 3. Concrete Domain Skills The role is instantiated by the domain skill that matches the concern: | Domain | Skill | |---|---| | Data | [data-architect](../../domains/data-architect/SKILL.md) | | Application portfolio | [application-architect](../../domains/application-architect/SKILL.md) | | Technology / infrastructure | [technology-architect](../../domains/technology-architect/SKILL.md) | | Integration and messaging | [integration-architect](../../domains/integration-architect/SKILL.md) | | API strategy and governance | [api-architect](../../domains/api-architect/SKILL.md) | | AI/ML and MLOps | [ai-ml-architect](../../domains/ai-ml-architect/SKILL.md) | | Network | [network-architect](../../delivery/network-architect/SKILL.md) | | Platform and developer platform | [platform-architect](../../delivery/platform-architect/SKILL.md) | | Systems engineering | [systems-architect](../../delivery/systems-architect/SKILL.md) | | Identity and access | [iam-architect](../../delivery/iam-architect/SKILL.md) | --- ## 4. Method 1. **Establish** the domain reference architecture from the enterprise target state and the domain's business drivers. 2. **Codify** domain standards, patterns and reusable models. 3. **Govern** domain decisions: review solutions, record compliance evidence, escalate cross-domain conflicts to the enterprise architect. 4. **Maintain** the domain roadmap and the repository slice. 5. **Feed back** reusable patterns and constraints to the enterprise frame. --- ## 5. Common Mistakes | Mistake | Correction | |---|---| | Re-deciding the enterprise frame | Escalate; the frame belongs to the EA | | Designing individual solutions | Advise; the solution architect designs | | Treating every domain title as a distinct profession | Many are scope variants of this role | | Leaving no domain repository slice | Maintain the slice and feed it to the EA | | Citing domain standards from memory | Resolve each version in-session |