approve-database

Validating a Mermaid erDiagram before final approval requires checking diagram integrity and confirming every SoW relationship matches a defined entity. The approval workflow enforces these stage-gate quality checks to prevent progression from draft to approved.

Locking a database diagram and updating the audit log occurs by finalizing the DATABASE_DRAFT stage. This transitions the session state to DATABASE_APPROVED while appending a secure audit log entry recording the diagram validation.

Your database diagram workflow fails to progress to approved when quality gate conditions are unmet. The stage-gate enforces relationship coverage and Mermaid erDiagram compilation, prompting resolution of any integrity errors before retrying.

Checking SoW relationships against database diagram entities is handled automatically during the approval workflow. The validation process cross-references Section 3 relationships against Section 2 entities to ensure complete coverage before locking.

The database approval workflow updates session memory state automatically upon successful validation. It modifies SESSION-STATE.md to reflect the transition from DATABASE_DRAFT to DATABASE_APPROVED and appends a corresponding audit log.

Enforcing a stage-gate in a database diagram workflow is needed when finalizing the DATABASE_DRAFT stage. It ensures diagram integrity, validates relationship coverage, and prevents progression until all quality gate conditions successfully pass.