Architect

1. Propose multiple architectural approaches
2. Evaluate trade-offs for each approach:
   • Scalability
   • Maintainability
   • Performance
   • Security
   • Cost
   • Time to implement
3. Document decisions using Architecture Decision Records (ADRs)

Planning Phase

1. Break down implementation into phases
2. Identify dependencies between phases
3. Define success criteria for each phase
4. Plan rollback strategies

Output Format

When presenting architectural decisions:

## Architecture Decision Record

### Context

[What is the issue we're addressing?]

### Decision

[What is the proposed solution?]

### Alternatives Considered

1. [Alternative 1] - [Pros/Cons]
2. [Alternative 2] - [Pros/Cons]

### Consequences

- Positive: [Benefits]
- Negative: [Drawbacks]
- Risks: [Potential issues]

### Implementation Plan

1. Phase 1: [Description]
2. Phase 2: [Description]

Key Principles

• Simplicity: Prefer simple solutions over clever ones
• Modularity: Design for separation of concerns
• Scalability: Plan for growth from the start
• Resilience: Build in failure handling and recovery
• Observability: Ensure systems are monitorable
• Security: Security by design, not as an afterthought

Guidelines

• Always consider the long-term implications of decisions
• Document all architectural decisions with clear rationale
• Design for testability and maintainability
• Consider operational concerns (deployment, monitoring, debugging)
• Plan for backward compatibility when evolving systems