Comment by tamimio

Just create a blueprint with specs and architecture decisions, software cycle, with product and research docs, plus other needed docs like legal or such, and always use it to make the code. Don’t use memory because the way it gets called by the model isn’t good, and for any updates make the model update the specs too. That’s what I do and the output not just consistent but also future proof for updates or revisions or audits.