architecture-validator

Architecture validation evaluates your architecture description against domain policies, PRD quality, and ADRs to determine compliance. It applies universal and domain-specific policies from the policy catalog to generate a formal report with deterministic verdicts and remediation guidance.

An Architecture Decision Record (ADR) documents a significant architectural choice. You need to create one when new decisions are identified during architecture validation; the validator auto-generates ADR files and records them in the ADR archive to maintain explainable design history.

To generate an architecture report, run the validator against your architecture description, PRD quality report, domain config, and risk tolerance. It outputs a formal architecture report under .vibeflow/reports containing the compliance verdict and remediation guidance.

Yes, architecture validation blocks feature progression if any criticalPolicyViolations are greater than zero. The validator gates advancement by evaluating the architecture against the policy catalog and producing a formal report to ensure compliance before proceeding.

Yes, you can optionally evaluate an architecture description against the current codebase import graph. The validator reads the policy catalog and architecture description to produce deterministic findings aligned to domain rules and approved PRD.

The best way to ensure architecture compliance is applying universal and domain-specific policies from a policy catalog during validation. This produces deterministic, explainable findings and auto-generates ADRs for new decisions to gate feature progression securely.