How to use Billionaire High Performance Coach with Claude for weekly review protocol
The Execution Evidence Ledger — weekly review protocol in Claude is a named operating pattern in the Billionaire High Performance Coach system. It applies Execution Evidence Ledger, which uses observable outcomes instead of intention as the source of truth, to weekly review protocol in Claude.
What this page recommends
The Execution Evidence Ledger — weekly review protocol in Claude is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Execution Evidence Ledger — weekly review 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.
Read the week from the record rather than from memory. It runs on one trigger: a fixed time each week, kept even in weeks that felt bad.
When this framework is the right one. Use it when you need to know what is actually happening over weeks rather than what it feels like is happening.
- Record one line per working day: the output that exists, in a form someone else could verify.
- Never record effort, intent, or how it felt. Those go elsewhere if you want them.
- Review weekly by reading the lines, not by remembering the week.
- Draw exactly one conclusion per review, and change one thing.
Weekly review protocol: purpose, trigger, output
| Element | What it is here |
|---|---|
| Purpose | Read the week from the record rather than from memory. |
| Trigger | A fixed time each week, kept even in weeks that felt bad. |
| Output | One conclusion and one change to next week's commitments. |
| Where it stops | Organizational support only. It is not clinical, legal, or financial advice. |
Where the weekly review protocol goes wrong
| Element | What it is here |
|---|---|
| How it usually fails | It becomes a long reflective write-up, which makes it skippable in the weeks it matters. |
| What to do in the first week | Read the record, write one conclusion, change one thing, and stop. |
| 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 weekly review protocol in Claude
A fixed time each week, kept even in weeks that felt bad. Read the week from the record rather than from memory.
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.
Record one line per working day: the output that exists, in a form someone else could verify.
What to measure. One conclusion and one change to next week's commitments.
Running Execution Evidence Ledger for the weekly review protocol
Memory of a period is reconstructed rather than recorded, and reconstruction is heavily weighted by the most recent and the most emotional days. A ledger written at the time is the only input to a review that is not itself a product of the review's mood.
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 weekly review protocol.
What this is not. It is not a time tracker and it does not measure hours. It measures artefacts.
What it leaves behind: one conclusion and one change to next week's commitments.
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 weekly review protocol produce?
One conclusion and one change to next week's commitments.
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 weekly review protocol usually fail?
It becomes a long reflective write-up, which makes it skippable in the weeks it matters. Read the record, write one conclusion, change one thing, and stop.
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.