How can I set up AI support to work when energy is low?
The Continuity Over Intensity Rule — work when energy is low is a named operating pattern in the Billionaire High Performance Coach system. It applies Continuity Over Intensity Rule, which prioritizes repeatable participation over heroic effort, to work when energy is low.
What this page recommends
The Continuity Over Intensity Rule — work when energy is low is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Continuity Over Intensity Rule — work when energy is low
A block arrives, the state does not match the work, and the hour goes to rereading the same paragraph.
Work has an energy profile and so does a block. Mismatch produces a stalled hour, and the stall gets attributed to discipline rather than to the mismatch.
Do this first. Categorize your work as high, medium, or low in advance, then take work from the category that matches the state you are actually in.
Do not do this. Forcing high-category work through a low block. It produces an unproductive hour and a conclusion about yourself, and neither is useful.
This level fits when: the behavior you want is stable and you want it by default. It does not fit when: you are still working out what you want. Configuring an unsettled preference makes it harder to change.
When this framework is the right one. Use it when planning a commitment you intend to keep for months, and the version you are about to commit to is the version you could do this week.
- Describe your worst plausible week honestly: illness, travel, a crisis at work.
- Size the commitment so it is still doable in that week, not in this one.
- Write the floor version explicitly, so that on a bad day there is something to do rather than a decision to make.
- Let good weeks overflow, but never let the overflow raise the floor.
Configuring standing assistance: what to supply and what to expect
| Layer | What it means here | Why it matters |
|---|---|---|
| Standing instruction | What should always be true of the responses. | Keep it short; long standing instructions get partially ignored. |
| Invocation | The phrase that starts the routine. | One phrase, memorable, used consistently. |
| Review date | When you will read the configuration again. | Configuration rots because nobody rereads it. |
| Cold test | Does it work in a fresh context with no history? | If not, it is depending on something invisible. |
Common misreadings: configuring standing assistance
| Element | What it is here |
|---|---|
| What it is usually mistaken for | A one-time task. Configuration rots quietly because nobody rereads it. |
| The metric that misleads | How much you configured. Long standing instructions get partially ignored. |
| What to do in the first week | Configure one thing, set a date to reread it, and test it in a fresh context. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Common misreadings: work when energy is low
| Element | What it is here |
|---|---|
| What it is usually mistaken for | Laziness, which is a description rather than a diagnosis and comes with nothing to do. |
| The metric that misleads | Output on your best days, which sets a bar the low days will be judged against. |
| What to do in the first week | Label each block high, medium, or low as you enter it, and note what it produced. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Worked example: Work when energy is low while configuring standing assistance
Someone sits down with this on the list. A block arrives, the state does not match the work, and the hour goes to rereading the same paragraph.
Write the standing instruction, then open a completely fresh context and check it behaves the same way. Categorize your work as high, medium, or low in advance, then take work from the category that matches the state you are actually in.
The framework then runs in order. First: describe your worst plausible week honestly: illness, travel, a crisis at work. Then: size the commitment so it is still doable in that week, not in this one.
What to measure. Record the state and the category worked. Repeated mismatch at the same time of day is a scheduling fact, not a character fact.
Running Continuity Over Intensity Rule for configuring standing assistance
Effort is elastic and schedules are not. A commitment sized to a good week fails in a normal one, and each failure costs more than the extra output of the good week bought. Sizing to the worst plausible week produces a commitment that survives, and surviving is what accumulates.
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 configuring standing assistance.
What this is not. It is not an argument against hard work. Intensity is fine; it just cannot be the thing the system depends on.
You are putting something in place that will be there tomorrow without being rebuilt: standing instructions, a stored template, a routine you can invoke by name.
Setup cost: a short configuration session, plus a cold test in a fresh context.
Where it is strong: it applies without you remembering to apply it, which is where most of the value is.
Where it is weak: configuration is invisible once set, so a bad rule keeps operating silently until you go and read it again.
Frequently asked questions
Doesn't this mean the hard work never happens?
Only if you never protect a high block. Schedule at least one where your state is reliably high, and let the matching rule govern the rest.
Is Continuity Over Intensity Rule the right framework for this?
Use it when planning a commitment you intend to keep for months, and the version you are about to commit to is the version you could do this week. It is not an argument against hard work. Intensity is fine; it just cannot be the thing the system depends on.
What should a reader do in the first week on work when energy is low?
Label each block high, medium, or low as you enter it, and note what it produced. Laziness, which is a description rather than a diagnosis and comes with nothing to do.
What should a reader do in the first week on set up AI support to?
Configure one thing, set a date to reread it, and test it in a fresh context. A one-time task. Configuration rots quietly because nobody rereads it.
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.