adapt-architecture

# Adapt Architecture Execute structural metamorphosis — transforming a system's architecture from its current form to a target form while maintaining operational continuity. Uses strangler fig migration, chrysalis phases, and interface preservation to ensure the system never stops functioning during transformation. ## When to Use - Form assessment (see `assess-form`) classified the system as READY - A system must evolve its architecture to meet new requirements without downtime - Migrating from monolith to microservices (or the reverse) - Replacing a core subsystem while dependent systems continue operating - Evolving a data model while maintaining backward compatibility - Any architectural change that must be gradual rather than big-bang ## Inputs - **Required**: Current form assessment (from `assess-form` or equivalent analysis) - **Required**: Target architecture (what the system should become) - **Required**: Operational continuity requirements (what must not break during transformation) - **Optional**: Available transformation budget (time, people, compute) - **Optional**: Rollback requirements (how far back must we be able to retreat?) - **Optional**: Parallel running duration (how long to run old and new simultaneously) ## Procedure ### Step 1: Design the Transformation Blueprint Plan the metamorphosis path from current form to target form. 1. Map the transformation as a sequence of intermediate forms: - Current form → Intermediate form 1 → ... → Target for...