# Hermes Modular Architecture Review — Request Template

Use this template to trigger a comprehensive Hermes review. Fill in what you have; Hermes will ask targeted follow-ups for gaps.

---

## Review Request

**System Name**: [e.g., Order Platform v2]

**Review Type**: [ ] Full architecture  [ ] Single module deep-dive  [ ] Pre-launch gate  [ ] Brownfield extraction  [ ] Post-incident boundary audit

**Context & Constraints**:
- Team size: [e.g., 3 squads, 18 engineers]
- Stage: [greenfield / brownfield / scaling / migration]
- Traffic/scale: [e.g., 2k RPS peak, 99.9% SLA]
- Hard constraints: [deadlines, compliance, legacy dependencies]

**Modularization Goal**:
> [Why modularize? e.g., independent release of payments, reduce build times, team autonomy]

---

## Architecture Artifacts (attach or paste)

### Module Inventory
| Module | Responsibility | Owner Team | Deploy Unit |
|--------|----------------|------------|-------------|
| [name] | [one-line purpose] | [team] | [monolith/pkg/service] |

### Dependency Description
```
[Paste import graph, diagram, or describe: A calls B via REST, C publishes OrderCreated events...]
```

### Public Contracts
```
[Paste OpenAPI snippets, event schemas, shared lib interfaces, or package exports]
```

### Data Ownership
```
[Which module owns which tables/collections? Any shared DB access?]
```

### Known Pain Points
- [e.g., deploy coupling, flaky cross-module tests, circular dependency between X and Y]

### ADRs / Design Docs (optional)
```
[Links or excerpts]
```

---

## Specific Questions for Hermes (optional)
1. [e.g., Is our Payments ↔ Ledger boundary correct?]
2. [e.g., Should Notifications be a separate module or part of Core?]

---

## Expected Output
Please deliver:
- Executive summary with **Ready / Ready with conditions / Not ready** verdict
- Hermes Scorecard (5 pillars)
- Severity-ranked findings with remediation roadmap
- Dependency diagram (Mermaid if ≥3 modules)
- Quick wins for next sprint

---

*Submit this completed template to begin the review.*