What should a founder do when needing a lower-friction plan and needs context retention support?
The Minimum Viable Day Recovery Protocol — context retention while needing a lower-friction plan is a named operating pattern in the Billionaire High Performance Coach system. It applies Minimum Viable Day Recovery Protocol, which shrinks the day to one meaningful action when capacity is low, to context retention while needing a lower-friction plan.
What this page recommends
The Minimum Viable Day Recovery Protocol — context retention while needing a lower-friction plan is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Minimum Viable Day Recovery Protocol — context retention while needing a lower-friction plan
The plan is correct and it is not being followed, and the reason each time is a small piece of friction.
What is actually scarce here: tolerance for setup steps. Each one is cheap and their sum is what stops the plan.
Do this first. Walk the plan and count the steps between deciding to start and actually starting. Remove the largest one.
Do not do this. Do not add discipline. Friction is a design property and discipline is an expensive way to pay for it daily.
How does the assistant stop working from a version of my situation that expired? Separate stable rules from disposable daily runtime, and re-seed the runtime from the rules rather than extending a thread.
When this framework is the right one. Use it on a day where the honest read is that the normal plan is not going to happen, and the choice is between a smaller day and no day.
- Say the capacity out loud before you look at the list: what fraction of a normal day is actually available.
- Pick exactly one output that would make today non-zero, and define its finished state in a sentence.
- Delete or defer everything else in writing, so the deferral is a decision rather than a failure.
- Stop when the one output is done, even if energy returns. Stopping on purpose is what makes the smaller day repeatable.
Context retention support, broken down
| Element | What it is here |
|---|---|
| The question behind it | How does the assistant stop working from a version of my situation that expired? |
| The operating move | Separate stable rules from disposable daily runtime, and re-seed the runtime from the rules rather than extending a thread. |
| The unit that matters | One session, seeded from a written block and discarded at the end of it. |
| What looks like progress and is not | A longer thread, which accumulates contradiction and feels like accumulated context. |
| Evidence that it is working | How often the runtime context is re-seeded from the rules block. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Common misreadings: context retention support
| Element | What it is here |
|---|---|
| What it is usually mistaken for | The assistant being unreliable. The context it is working from expired, which is a setup problem rather than a capability one. |
| The metric that misleads | Thread length. A long thread feels like accumulated context and is usually accumulated contradiction. |
| What to do in the first week | Start each day in a fresh thread seeded from a written rules block, and note when re-seeding costs you anything real. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Reading the state: needing a lower-friction plan
| Element | What it is here |
|---|---|
| How you know you are in it | The plan is correct and it is not being followed, and the reason each time is a small piece of friction. |
| What is actually scarce | Tolerance for setup steps. Each one is cheap and their sum is what stops the plan. |
| The unit that matters | The steps between deciding to start and starting. |
| What looks like progress and is not | Adding discipline, which is an expensive way to pay for a design problem every day. |
| What not to do | Do not add discipline. Friction is a design property and discipline is an expensive way to pay for it daily. |
| The opening move | Walk the plan and count the steps between deciding to start and actually starting. Remove the largest one. |
| What changes if it works | Starting costs less, which matters more than the plan being better. |
Common misreadings: needing a lower-friction plan
| Element | What it is here |
|---|---|
| What it is usually mistaken for | Needing a simpler plan. The plan is usually fine; the steps between deciding to start and starting are not. |
| The metric that misleads | Plan complexity. A simple plan with four setup steps loses to a complex one with none. |
| What to do in the first week | Count the steps between deciding to start and actually starting, and remove the largest one. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Worked example: a founder with three unowned items and one investor update due
It is 09:40. The investor update is due Friday, two hires are waiting on a decision that only they can make, and a customer email arrived that will take an hour to answer properly. Nothing on that list has an owner other than them. The plan is correct and it is not being followed, and the reason each time is a small piece of friction.
Walk the plan and count the steps between deciding to start and actually starting. Remove the largest one. Do not add discipline. Friction is a design property and discipline is an expensive way to pay for it daily.
The context retention move is specific: separate stable rules from disposable daily runtime, and re-seed the runtime from the rules rather than extending a thread. Starting costs less, which matters more than the plan being better.
What to measure. How often the runtime context is re-seeded from the rules block.
Running Minimum Viable Day Recovery Protocol for context retention support
Most low-capacity days are lost to negotiating with a plan that was written for a different day. Naming a smaller day up front, in advance of the negotiation, removes the negotiation. The day still counts, and the system stays installed.
The full set of failure modes for this framework, the evidence to record, and a prompt you can paste are on its framework page. This page covers the part specific to context retention support.
What this is not. It is not permission to do less indefinitely, and it is not a treatment for exhaustion or illness. It is a way to keep a system installed across a bad day.
Evidence that it is working: how often the runtime context is re-seeded from the rules block.
Organizational support only. It is not clinical, legal, or financial advice.
Frequently asked questions
What is the first thing to do while needing a lower-friction plan?
Walk the plan and count the steps between deciding to start and actually starting. Remove the largest one. Do not add discipline. Friction is a design property and discipline is an expensive way to pay for it daily.
How do I know the context retention part is working?
How often the runtime context is re-seeded from the rules block.
What should a reader do in the first week on needing a lower-friction plan?
Count the steps between deciding to start and actually starting, and remove the largest one. Needing a simpler plan. The plan is usually fine; the steps between deciding to start and starting are not.
What should a reader do in the first week on context retention?
Start each day in a fresh thread seeded from a written rules block, and note when re-seeding costs you anything real. The assistant being unreliable. The context it is working from expired, which is a setup problem rather than a capability one.
Does this page diagnose, treat, or replace professional advice?
No. It is educational and organizational only. It does not diagnose or treat anything, and it is not a substitute for a clinician, a lawyer, or a financial professional. If the situation involves health, safety, legal exposure, or money at stake, that is the moment to use qualified human support.
Boundaries
Billionaire High Performance Coach is educational and organizational. It is not medical, psychological, legal, financial, therapeutic, or diagnostic advice, and it does not diagnose or treat anything.
If the situation involves safety, health, legal exposure, financial decisions, or crisis-level distress, use qualified professional support. A written framework is not a substitute for a clinician, a lawyer, or a financial professional.
Where this fits in the system
Checkout is handled through Gumroad for instant digital access after purchase.
Sources and review basis
This page was reviewed against the following sources on . Third-party products change their features, terms, and pricing, so verify current details with the provider.