karvey-architecturelisted

# Karvey Architecture ## Purpose Generate the enterprise architecture technical design: components, boundaries, integrations, security controls per tier, observability, and a concrete file structure per layer. ## Execution steps ### Step 1 — Load context Read in parallel: - `docs/spec/changes/{change-id}/spec.json` (security_tier, layers, capability) - `docs/spec/changes/{change-id}/requirements.md` - `docs/spec/changes/{change-id}/design-spec.md` - `docs/spec/project.json` (cloud.provider, iac_tool, git_platform) - `rules/security-tiers.md` - Project steering: `product.md`, `tech.md` or equivalents if they exist Verify `approvals.design_graphic.approved = true`. If not, stop. ### Step 2 — Architecture discovery **For features that extend the existing system (brownfield):** Dispatch subagents to explore in parallel: - Subagent A: `grep -r` of existing patterns related to the capability - Subagent B: read existing endpoints/SPs of the affected area Identify: - Existing code patterns to follow (naming, function structure, error handling) - Existing data access and its signatures (SPs, queries, ORM models, repositories, etc.) - Existing API endpoints / operations and their contracts - External integrations that already exist **For completely new features (greenfield):** - Define new patterns coherent with the existing stack ### Step 3 — Classify architectural complexity | Type | Criterion | Discovery | |------|----------|-----------| | Simple addition | Only adds CR