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` (absent when design_graphic was skipped) - `docs/spec/project.json` (cloud.provider, iac_tool, git_platform, **standards**) - `../karvey/rules/security-tiers.md` - `../karvey/rules/engineering-standards.md` - **Engineering standards for the change's layers/targets**: resolve `project.json:standards` (or `docs/spec/standards/_index.md`) and read the relevant `standards/{layer}.md`. These are a **hard constraint** on this design, not a suggestion. If no standard exists for a layer, announce it and treat every non-trivial pattern choice for that layer as a gray zone to ask (never silently pick one). - Project steering: `product.md`, `tech.md` or equivalents if they exist Check the precondition with the state tool: every earlier phase **approved or skipped** (`../karvey/rules/state-machine.md`): ```bash S="${CLAUDE_PLUGIN_ROOT}/scripts/karvey-state.py" python3 "$S" next "{change-id}" --json # relay the blockers and stop if any python3 "$S" advance "{change-id}" architecture ``` ### Step 2 — Architecture discovery **For featu