Most software welds ownership, delivery and release into a single repository, then spends years paying for the weld.
I think it should be the other way round. Each repository answers for exactly one thing, and the composition itself can be described, checked, and taken apart again.
That's WanWeave.
I spend most of my time not writing code. I write down what we agreed to build, then I go and check whether it's still true. Usually it isn't, and nobody notices for a month.
It's less romantic than it sounds. It's mostly files.
Then there are the agents. I use them as engineers, not as autocomplete, so their boundaries live in files instead of staying in a conversation. Not out of distrust. I'm not good at remembering what I promised yesterday either.
Sessions forget. Files don't.
Code is like poetry, concise and elegant.