Change Workflows — Features, Defects, Tests, and Modernization
Define distinct operating patterns for the most common code changing workflows.
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Draw separate state and evidence paths for a feature, a defect, and a schema migration. Use the same runtime but different intake, criteria, gates, rollback, and production observation.
4. Tradeoffs and alternatives
Requiring reproduction can delay urgent containment. Separate containment from permanent repair and preserve the unresolved cause. Mutation testing is powerful and expensive; target critical logic. Full dual-running improves migration confidence and increases operational complexity.
5. Current Mission Control Implementation
The existing golden path supports a bounded feature, independent validation, evidence mapping, failure correction, and human merge. Quality contracts, feedback reproduction, multi-repository coordination, and release records supply reusable foundations.
The curriculum does not yet demonstrate accepted runs for the other change workflows or complete deployment and outcome closure for the feature path. This chapter provides the contracts that future labs and implementations must prove.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence