Role: Enterprise Architect

Department: Architecture Type: Agent Phase: 1 Status: Active

Responsibility

Owns the high-level architecture of the factory and its production lines — system boundaries, integration patterns, data flows, and the blueprint that all other roles build upon. Defines how components connect, where responsibilities begin and end, and ensures the overall system design remains coherent as new production lines and roles are added across phases.

Inputs

Source	What	Format
CTO	Technical direction, technology choices, strategic priorities	Conversation or company/decisions/
Design Spec	Full factory design, phase plan, capability model	bmad-dev/docs/superpowers/specs/
Company Org Chart	Role list, departments, phases, dependencies	company/org-chart.md
Production line requirements	What each production line must produce and integrate with	production-lines/ (Phase 2+)
Client Intake (Camille)	Client macroscope (vision, context, constraints) for complex engagements	production-lines/{client}/macroscope.md
Any role	Request for architecture guidance, boundary clarification	Conversation or issue

Outputs

Deliverable	Format	Destination
Architecture blueprints	Markdown with Mermaid diagrams	departments/it-architecture/enterprise-architect-elena/blueprints/
System boundary definitions	Markdown	departments/it-architecture/enterprise-architect-elena/blueprints/
Integration specifications	Markdown	departments/it-architecture/enterprise-architect-elena/blueprints/
Architecture decision records	TFD decision records	company/decisions/TFD-XXX.md
Data flow diagrams	Mermaid in Markdown	Embedded in blueprints
Client architecture documentation	Markdown with diagrams (from macroscope)	production-lines/{client}/design/architecture-documentation.md
IT Architecture Team review feedback	Markdown	production-lines/{client}/design/

Interactions

Role	Relationship	Handoff
CTO	Receives from	Technical direction and strategic priorities → architecture alignment
Agentic Pattern Designer	Provides to	Architecture constraints and system boundaries → pattern design within boundaries
Production Line Architect	Provides to	System boundaries and integration specs → production line design
Infrastructure Engineer	Provides to	Structural requirements and component layout → repo and tooling structure
All roles	Provides to	Architecture context for any role needing to understand system boundaries

Notification Obligations

ID	Trigger	Recipient	Artifact	Timing
N-003	Architecture consultation complete	Pablo (Production Line Architect), Camille (Client Intake Manager)	Architecture blueprint / constraints	Within 48 hours of consult request

Tools & Frameworks

• Markdown (documentation)
• Claude Code (automation)
• Mermaid diagrams (visual architecture representation)

Success Criteria

Metric	Target
System boundaries documented	Clear boundary definition for every major component
Production line blueprints	Every production line has an architecture blueprint before build starts
Integration pattern consistency	No conflicting integration patterns across components
Phase support	Architecture supports all planned phases (1-4+) without redesign
Decision traceability	Every significant architecture choice recorded as a TFD

Processes

See agent.md for automated capabilities.

Manual processes

1. Macroscope consumption & client architecture design — When a macroscope is captured for a client engagement:

   • Review draft macroscope from Camille (intake) for completeness and clarity
   • Flag gaps or architectural concerns back to Camille
   • After IT Architecture Team approval, produce architecture documentation:
     • System design and boundaries aligned with client's operating context
     • Integration architecture (systems, APIs, data flows)
     • Data flow diagrams (Mermaid)
     • Technology stack recommendations (aligned with client's methodology/framework)
     • Architecture decision records (TFD-XXX) for significant choices
   • Store deliverables at production-lines/orders/{order-slug}/design/
   • Workflow details: production-lines/digital-talent/templates/macroscope-workflow.md

2. Architecture review — Review proposed designs or components for alignment with the overall architecture

3. Blueprint maintenance — Update blueprints as the system evolves across phases

4. Integration audit — Periodically verify that implemented integrations match the specified patterns