How to use Billionaire High Performance Coach with Claude for minimum viable day protocol
The Minimum Viable Day Recovery Protocol — minimum viable day protocol in Claude 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 minimum viable day protocol in Claude.
What this page recommends
The Minimum Viable Day Recovery Protocol — minimum viable day protocol in Claude is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Minimum Viable Day Recovery Protocol — minimum viable day protocol in Claude
Long documents can sit alongside the conversation, so the rules block can be a file rather than a paste.
Stored context is a convenience. Keep a plain-text copy so the setup survives a product change.
Do this first. Put the rules in a file that sits alongside the conversation, and give the file a version marker so a behavior change can be attributed to an edit.
Do not do this. Letting the file grow. A rules document too long to read in full stops being read, and then it stops being the source of truth.
Keep a low-capacity day non-zero without pretending it is a normal day. It runs on one trigger: an honest read that the normal plan is not going to happen today.
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.
Minimum viable day protocol: purpose, trigger, output
| Element | What it is here |
|---|---|
| Purpose | Keep a low-capacity day non-zero without pretending it is a normal day. |
| Trigger | An honest read that the normal plan is not going to happen today. |
| Output | One output with a written finished state, an explicit deferral list, and a stop condition. |
| Where it stops | Organizational support only. It is not clinical, legal, or financial advice. |
Where the minimum viable day protocol goes wrong
| Element | What it is here |
|---|---|
| How it usually fails | The declared small day turns into a normal day, which teaches you the small day was not real. |
| What to do in the first week | Stop at the stop condition even when energy returns. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Running this in Claude: setup and state
| Element | What it is here |
|---|---|
| Seeding the rules | Keep the rules in a short document alongside the conversation, with a version marker at the top. |
| What carries between sessions | Documents persist and drift silently. Put the review date in the document itself. |
| What to verify with the provider | Stored context is a convenience. Keep a plain-text copy so the setup survives a product change. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Common misreadings: Claude
| Element | What it is here |
|---|---|
| What it is usually mistaken for | A place to store everything. Long context makes it easy to keep material that has expired. |
| The metric that misleads | How much you have attached, which is not the same as how much of it is current. |
| What to do in the first week | Read the attached rules document in full once. If you will not, it is too long to be governing anything. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Worked example: the minimum viable day protocol in Claude
An honest read that the normal plan is not going to happen today. Keep a low-capacity day non-zero without pretending it is a normal day.
Long documents can sit alongside the conversation, so the rules block can be a file rather than a paste. Keep the rules file short enough to read in full, and version it so you can tell which version produced a session.
Say the capacity out loud before you look at the list: what fraction of a normal day is actually available.
What to measure. One output with a written finished state, an explicit deferral list, and a stop condition.
Running Minimum Viable Day Recovery Protocol for the minimum viable day protocol
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 the minimum viable day protocol.
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.
What it leaves behind: one output with a written finished state, an explicit deferral list, and a stop condition.
Frequently asked questions
Does this depend on Claude specifically?
No. Stored context is a convenience. Keep a plain-text copy so the setup survives a product change.
What does the minimum viable day protocol produce?
One output with a written finished state, an explicit deferral list, and a stop condition.
What should a reader do in the first week on Claude?
Read the attached rules document in full once. If you will not, it is too long to be governing anything. A place to store everything. Long context makes it easy to keep material that has expired.
How does the minimum viable day protocol usually fail?
The declared small day turns into a normal day, which teaches you the small day was not real. Stop at the stop condition even when energy returns.
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.