gaia-edit-arch

To edit an architecture document while preserving traceability, apply scoped cascade-aware edits to architecture.md, which assesses downstream artifacts like epics and test plans for impact and maintains version history.

Cascade impact analysis in architecture change management evaluates how modifying sections of an existing system architecture document affects downstream artifacts, ensuring consistency across epics, stories, test plans, and infrastructure design.

You can log Architecture Decision Records with auto-incremented IDs by triggering the architect subagent Theo during the architecture edit flow, which records ADRs and updates the version history automatically.

Yes, editing architecture.md affects downstream artifacts because the process assesses epics, stories, test plans, and infrastructure design for cascading impact to ensure strict consistency across the planning artifacts.

Before modifying a system architecture document, setup gates are enforced through validation scripts like checkpoint.sh and validate-gate.sh, ensuring the environment is correctly configured before loading the architecture for editing.

Yes, you can update specific sections of architecture.md without altering unchanged parts, as the cascade-aware edit flow enforces strict preservation of unchanged sections while applying targeted modifications.