Build for change, not stability
The right way to build AI-enabled products can change within a few months. Sometimes rebuilding is more sensible than adapting a system designed around assumptions that no longer hold. The same tools creating the change also make rebuilding cheaper.
You cannot wait for everything to stabilize. Build something useful, keep the underlying knowledge portable, and design the process so that replacing a component does not mean losing what the team learned.