run
4.1.1 - You Haven't Finished a Deploy Until You've Practised Undoing It - Decide what triggers a deploy to each environment, how you confirm it landed and the exact route back to the previous version.
The vibe2value framework
Run it
Keep a live system honest.
Run is where people rely on it and you are not watching. It is less about uptime and more about whether the system tells you the truth about itself: that a deploy can be undone, that a quiet failure gets noticed and that you can tell whether any of it is working. These ideas help you keep a live system honest without living inside it. When the question becomes whether it should still be running at all, that is Close.
- Releasehow it goes out and how it comes back
- Recoverwhat breaks quietly and who hears about it
- Settlehow you would know whether any of it worked
The five Run ideas
run
4.1.2 - If the Secret Only Exists on Your Machine, You Are the Single Point of Failure - Decide where secrets live and how they are set per environment, with every name the code reads written down and no real value anywhere near it.
run
4.2.1 - The Failure Whose Only Symptom Is That the Answer Looks Wrong - Decide where each kind of failure appears and what a person is handed when it does, including the ones that never go red.
run
4.2.2 - Decide What Reaches You Before Everything Does - Decide which work runs unattended, what hands itself back to a person and what that person actually receives when it does.
run
4.3.2 - How Would You Know If Any of This Worked? - Decide what evidence would tell you the knowledge base is doing its job, then take the reading before you start so you have something to compare against.