Reducing Entropy

This is for when you need to actually shrink your codebase, not just refactor it. It flips the usual bias: instead of minimizing churn, it measures success by total lines after you're done. Writing 50 lines that delete 200 is a win. Keeping 14 functions to avoid writing 2 is a loss. It asks three questions every time: what's the smallest result, does this reduce total code, and what can we delete. The red flags section is worth reading,it calls out "better separation of concerns" and "adds flexibility" as entropy in disguise. Manual activation only, which makes sense since this is a specific mode you want control over.