I think the anti-fragile concept applies not to the codebase, but the processes and ecosystem surrounding it (users, devs, communication tools, social dynamics)

I think the anti-fragile concept applies not to the codebase, but the processes and ecosystem surrounding it (users, devs, communication tools, social dynamics). Software is best modeled as a living thing intertwined with humans, not just the current snapshot of its source code. For instance, a web app with a public bug tracker is more anti-fragile than one without. I've also heard strategies of making errors and warnings public on production, so that problems stick out like a sore thumb, and get fixed more quickly. (Obviously, this isn't a good idea in all cases.)