09 — Summary and Reset Protocol¶
This file is the final integration of the pre-mortem layer. It contains the decision tree you consult when something is going wrong, the formal RESET protocol you execute when you cannot tell what is wrong, and the doctrine that governs every escalation in this directory: the roadmap serves you, you do not serve the roadmap.
The decision tree¶
When a sprint retro is bad, or when a week has felt off, or when you’re not sure whether to keep pushing or to pause — walk this tree in order. Do not skip nodes. The nodes are ordered by seriousness, not by convenience.
The formal RESET protocol¶
Apply this when you have walked the decision tree and cannot cleanly place your problem, OR when the escalation trigger from any single file has fired. The RESET is not punishment; it is a legitimate move built into the roadmap by a calmer version of you.
RESET — five steps, in order, no skipping.¶
1. Stop coding for 3 days. Full stop. No commits, no editor, no man pages. Three days minimum. Not “light touch.” Off. Sleep, walk, eat with family, read something not-C. You have been running your cognition into the ground and the first thing that needs to happen is the ground has to level. If you cannot bring yourself to fully stop, that IS the confirmation that you needed the reset.
2. Reread 00_command/01_month_by_month.md and honestly re-baseline.
On day 4, open the month-by-month plan. Read it as if a friend had written it and you are auditing it for realism. Ask: where am I actually, in months and in rungs? Not where the plan says I should be — where I actually am. Write the honest number down. If you’re 6 weeks behind, that is the number. Do not round.
3. Rewrite the current month’s plan with 30% less scope. Take the current month’s plan and cut it. Not by 10%, not by 20% — by 30%, at minimum, and 50% if the burnout was serious. Drop outcomes. Simplify rungs. Push everything non-critical to a later month. You are re-planning FROM your actual position, not from where you wish you were. The old plan was a plan for a different person, one who had not encountered whatever knocked you into the RESET. The new plan is for you.
4. Ship the smallest possible deliverable in the next 7 days. Within one week of restarting, ship something. Anything. A single-file utility, a 200-word blog post, a bug fix in an old project, a rewritten README. The point is not the quality; the point is the momentum. You need one shipped artifact to remind your nervous system that the mechanism still works. Do not skip this step. This step is why RESETs succeed instead of failing again.
5. Post it publicly, regardless of quality. Whatever the smallest artifact is, put it somewhere with a URL and share the URL. LinkedIn, personal blog, dev.to, r/C_Programming, an internal Zoho channel. Public commitment closes the RESET loop. Private RESETs fail; public RESETs stick, because the world now expects you to keep going.
After step 5, resume sprint cadence normally. Do NOT try to catch up. Do NOT double the next sprint. The RESET is the new baseline, and you build from there.
The doctrine¶
Everything in this pre-mortem layer, and everything in this discipline layer, and honestly everything in this roadmap, rests on one sentence:
The roadmap serves you. You do not serve the roadmap.
Read that again. Every tactical decision, every escalation, every scope-down and every buffer sprint and every permission slip flows from that single doctrinal commitment. The moment the relationship inverts — the moment you start believing you owe the roadmap something, that the roadmap has authority over your family or your body or your peace — the roadmap has stopped being a plan and started being a religion, and the religion will grind you down until nothing that mattered originally remains.
Do not let the roadmap become a religion. It is a tool. Tools serve. When a tool stops serving, you put it down and pick it up again later, or you replace it, or you accept that you have grown past it. That is what tools are for. That is what this document is for.
Final meta-quote¶
The fortress has doors that open outward. When you need to leave, leave. When you’re ready to return, return. The stones will still be here.
Return to README.md · Back to ../README.md