Audience asks if Mutant can be used beyond regression detection to identify code that should be refactored. Schirp: yes. On an unfamiliar class, run Mutant without caring about kills and look at the reduction-operator output to see valid transformations — the first refactor commit can delete the ones with no proof of value. Also useful on tangled code like a 20-arm case statement: pin the mess to pass Mutant from a single public interface first, then you are free to refactor internals while keeping coverage constant.