Re: Snapshot Recipe Heirarchy
I think the best way would be to code functionality to allow a "snapshot" recipe to become the "default" while archiving the old "default" recipe. That way, we can track the evolution of a recipe as we try tweaks, change, abandon changes that don't work and keep those that do. And, worst case, can revert if we get too far off track. A "snapshot" that failed the improvement test could also be archived to help prevent making the same error twice. I'm approaching this from the aspect of a Lean practitioner - experimentation is important but it's important to keep good records as well to know what you've done, what worked, what didn't - it's just the same as keeping records of process improvements in any business!
