validate-architecture-spec

What problem does it solve?

It prevents enterprise delivery from proceeding when the architecture outputs do not satisfy the required six-artifact contract and their decision-manifest integrity rules, ensuring the derived architecture is structurally complete, consistent, traceable, and validation-ready.

Core Features & Use Cases

• Validates six required architecture artifacts: refined quality-profile, systems-inventory, logical-architecture, physical-architecture, tech-stack, and technical-risks, including artifact non-emptiness.
• Enforces logical and physical consistency: checks component shape, capability coverage, and cycle absence across both logical and physical graphs.
• Verifies NFR and tech-stack discipline: ensures every NFR characteristic is delivered, pattern citations are valid and grounded, and tech-stack entries follow the required schema.
• Guards risk quality and provenance: validates technical-risks structure and stage ordering, verifies refined quality-profile delta_log integrity, and ensures inventory provenance (including byte-for-byte KB grounding).

Quick Start

Ask the system to run validate-architecture-spec after tech-architect finishes producing the /arch derive artifacts to produce a validation-result.yaml file showing passed/failed status and all blocking violations.