16-evolve

You can add features to a deployed service using delta spec updates, which apply incremental changes to specifications without full regeneration. This streamlines feature evolution by routing updates through planning, build, and verification stages.

Orchestrating scope changes for an existing microservice is managed by routing the process through intake, technical planning, build, verification, and deployment stages. This ensures consistent evolution with mandatory phase checkpoints for quality control.

Delta mode handles specification updates by applying incremental changes during service evolution, avoiding full spec regeneration. It updates only the modified components while routing the feature through build and verification checkpoints.

Yes, a pre-existing workflow state is required to manage service evolution stages. The process routes features through intake, planning, technical planning, build, verification, and deployment using this established state.

Architecture Decision Records are logged automatically for traceability when adding features to a deployed service. The system records ADRs as features route through technical planning, build, and deployment stages.

Use stage routing with mandatory checkpoints for feature management when evolving a deployed service with multiple features or scope changes. Checkpoints enforce quality control across planning, build, verification, and deploy phases.