System Design Validator

Validate evidence, not intentions. Read references/contract-v1.md, references/handoff-v1.md, and references/rule-catalog-v1.md. Emit validator findings as SDV-* records in a state patch.

Decision policy

• FAIL when any unresolved Critical, critical traceability gap, unit inconsistency, or required phase gate is missing.
• CONDITIONAL when unresolved High findings remain only with explicit risk acceptance and owner.
• PASS when no unresolved Critical/High findings remain and required gates are satisfied.

Procedure

1. Determine rule applicability from the state before running a rule; do not apply every checklist item blindly.
2. Check FR/NFR coverage, measurable NFRs, EST formulas/units/scenarios, and links between requirements, assumptions, estimates, decisions, failure modes, and findings.
3. Check whether advanced complexity has a measurable rationale and simpler alternative. Flag microservices, sharding, Kafka/event streaming, multi-region, or polyglot persistence without evidence.
4. Check operation-level consistency, invariant, transaction boundary, idempotency, retry safety, detection, recovery, security boundary, and operational ownership when applicable.
5. Create one stable SDV-* finding per issue with rule ID, severity, evidence, affected IDs, remediation, owner, and status. Revalidation resolves findings explicitly; do not silently erase history.
6. Return the envelope with decision, gate results, remaining risks, and the next capability. Never claim PASS without evidence.