What in your codebase have you declared "frozen" and refuse to touch?
by•
There is one directory in my project I am not allowed to refactor, even to tidy it up: the code that draws the actual Nutrition Facts panel, to the regulator's spacing rules.
It is not pretty code. But it is correct, it is verified against the regulation's worked examples, and every "improvement" I can imagine risks nudging a hairline rule by half a point and making thousands of generated labels subtly non-compliant. So it is frozen. Bugs elsewhere get fixed; that folder gets read-only respect.
Do you have a part of your product like this? Something you have consciously decided is done, where touching it is banned no matter how much it itches?
15 views
Replies
In my case it is the column names in my database. We renamed a pair of fields across the whole codebase because the old names read backwards to anyone new, but the columns kept their old names and the code just maps to them. The code moved on, the storage didn't, and it stays that way
The parts I care about are frozen by a test instead. One fails if the old names show up anywhere outside five allowed files. Another fails if a marketing claim we can't back sneaks back into the copy. The agent hits the red test and backs off, no memory needed.
Our utils directory is completely frozen for coding agents. One lost context mid-task and "rebuilt" a helper that already existed two files away under a new name. Plus callers split between the two and drifted apart. So now shared utilities are strictly manual edit only.