Scope Creep as a State Machine: A Developer's Framework

A developer proposes treating scope creep as a state machine with four states: included, swapped, deferred, or added. The model requires written approval before work begins, preventing unclassified requests from entering production. It also recommends pricing impact based on direct effort, uncertainty reserve, and displaced-capacity cost.