Audience member observes that fixing or changing code seems to amount to removing or adding features, and asks what distinguishes the transformations. Gamsjaeger: the key is atomic commits. A remove is typically just red lines (optionally with call-site adjustments). A fix addresses a violation of any established rule — including a suboptimal-state rule, not only production bugs (e.g. redundant whitespace extracted as its own fix). The question really boils down to atomicity: under true atomic discipline, a naive 'add' commit usually decomposes into a sequence of smaller transformations that can then be ordered by priority.