approve-architecture

To validate a Mermaid architecture diagram before approval, run the governance workflow to verify SoW coverage, check for unresolved placeholders, and ensure all services are mapped correctly. The pipeline proceeds only when artifact integrity checks pass.

Stage gating in an architecture governance pipeline is the process of locking the architecture draft after validating diagram integrity, SoW alignment, and placeholder resolution. It updates the audit log and session-memory before unlocking downstream database drafting steps.

To detect manual edits and drift in a system architecture draft, the workflow uses a manual-edit detection protocol with safe fail-safes. This prevents uncontrolled progression by identifying unauthorized changes before the architecture stage is locked.

To ensure SoW coverage matches the system architecture HTML, the validation workflow checks that the architecture aligns with the approved Scope of Work, verifies cover-sub reflects the project name, and confirms all placeholders are resolved before approval.

After architecture approval in the workflow pipeline, the system locks the ARCHITECTURE_DRAFT, advances the state to ARCHITECTURE_APPROVED, updates the audit log and session-memory, and provides the next valid commands to guide users toward database drafting.

Uncontrolled progression happens with architecture drafts when manual edits bypass the stage-gate validation. The workflow prevents this by detecting drift, enforcing placeholder resolution, and applying safe fail-safes to halt the pipeline until integrity is restored.