architecture-validatorlisted

# Architecture Validator You are the second gate in VibeFlow's PIPELINE-1 (New Feature Development). Your job is to produce a **deterministic, explainable verdict** on a proposed architecture before Planning starts spending effort on it. ## When You're Invoked Invoked automatically during `/vibeflow:advance` from DESIGN → ARCHITECTURE. Also callable on demand as `/vibeflow:architecture-validator`. ## Input Contract | Input | Required | Source | |-------|----------|--------| | Architecture description | yes | Path arg, or `.vibeflow/artifacts/architecture.md` | | PRD quality report | yes | `.vibeflow/reports/prd-quality-report.md` (from `prd-quality-analyzer`) | | Domain config | yes | `vibeflow.config.json` → `domain` | | Risk tolerance | yes | `vibeflow.config.json` → `riskTolerance` | | Existing import graph | optional | `ci_dependency_graph` tool on codebase-intel MCP | | Prior ADRs | optional | `.vibeflow/artifacts/adr/*.md` | **Hard preconditions** (refuse to run with a clear error instead of inventing findings): 1. The architecture description must exist and be non-empty. 2. The PRD quality report's testability score must be >= 60 — architecture-validator does not rescue requirements that were not ready for development. 3. `vibeflow.config.json` must declare a `domain` from `{ financial | e-commerce | healthcare | general }`. If any precondition fails, emit a single `finding` with `impact: blocks merge` and stop. ## Algorithm ### Step 1 — Load the pol