review-infrastructure

To safely edit an infrastructure diagram, use iterative stage-gated editing that enforces strict validation and automatically logs changes to an audit trail while bumping the diagram version after each save.

Stage gates in deployment architecture restrict modifications to specific lifecycle states like DRAFT, APPROVED, or COMPLETE. You need them to prevent unauthorized infrastructure changes and ensure only validated updates are applied.

You can modify specific sections of an infrastructure diagram by selecting one of the nine distinct sections per interaction. This section-level approach isolates edits and automatically logs each validated change to the audit log upon saving.

Yes, you can update an approved infrastructure diagram. Modifying APPROVED or COMPLETE infrastructure reopens it to DRAFT status, allowing iterative updates while strictly maintaining the versioned audit log trail.

Versioning infrastructure diagrams requires access to session-memory/SESSION-STATE.md and the project-diagrams HTML file. These files track the current stage gate and apply the automatic version bump after validated section edits are saved.

If infrastructure is not in DRAFT state but is APPROVED or COMPLETE, attempting edits automatically reopens it to DRAFT. This stage gate mechanism ensures all modifications are re-validated and securely logged before returning to a finalized state.