Build for change, not stability
The right way to build an AI-enabled product can change in a few months. Sometimes rebuilding makes more sense than adapting a system built around assumptions that no longer hold. The same tools causing the change also make rebuilding easier.
You can't wait for everything to stabilize. For me, the best answer right now is to keep domain knowledge in markdown that I can adapt as the tools change. I don't have a more settled answer than that.
Originally posted on X. Lightly edited for reading here.