validating-architecture-analysis

Architecture diagrams are validated against subsystem catalogs by checking cross-document consistency, ensuring catalog dependencies align with diagram arrows, and producing a detailed validation report with traceable findings and line references.

Cross-document consistency validation checks architecture artifacts like subsystem catalogs, diagrams, and final reports to ensure dependencies and references align across documents, generating a structured report with an APPROVED or NEEDS_REVISION status.

Generate an architecture validation report by running the validation workflow on prepared artifacts like 02-subsystem-catalog.md and 03-diagrams.md, which outputs a detailed report in workspace temp with clear APPROVED or NEEDS_REVISION status and actionable fixes.

Final reports are checked against formal contracts automatically to surface missing sections and inconsistencies, providing a structured validation report suitable for review and archival with actionable fixes and line references.

Architecture artifact validation requires markdown files including 02-subsystem-catalog.md, 03-diagrams.md, and 04-final-report.md, which are validated against contract requirements to produce a structured validation report in workspace temp.

A validation report shows NEEDS_REVISION status when architecture artifacts fail contract compliance or cross-document consistency checks, providing traceable findings with line references and actionable fixes to address missing sections or misaligned dependencies.