Three-chat Architecture for weekly planning Glossary

The Three-Chat Architecture — weekly planning as a defined term is a named operating pattern in the Billionaire High Performance Coach system. It applies Three-Chat Architecture, which separates source-of-truth rules, daily runtime, and governance edits, to weekly planning as a defined term.

What this page recommends

The Three-Chat Architecture — weekly planning as a defined term is a named operating pattern in the Billionaire High Performance Coach system. The Three-Chat Architecture — weekly planning as a defined term is a named operating pattern in the Billionaire High Performance Coach system. It applies Three-Chat Architecture, which separates source-of-truth rules, daily runtime, and governance edits, to weekly planning.

Three-Chat Architecture — weekly planning as a defined term

Use it when one long assistant thread has become both the rulebook and the daily workspace, and the rules have started drifting.

Three-Chat Architecture separates source-of-truth rules, daily runtime, and governance edits.

Do this first. Fix the week's commitments first, then place at most three outputs against the remainder.

Do not do this. The metric that misleads here: number of items placed. It measures ambition at the start of the week, which is the least informative moment.

What is the week for, given that most of it is already committed? Fix the week's commitments first, then place at most three outputs against the remainder.

When this framework is the right one. Use it when one long assistant thread has become both the rulebook and the daily workspace, and the rules have started drifting.

  1. Create a rules chat that contains only the standing instructions. Never do daily work in it.
  2. Create a runtime chat for today, seeded by pasting the rules block at the top. Discard it when the day ends.
  3. Create a governance chat where proposed rule changes are argued and either accepted into the rules chat or rejected.
  4. Change the rules only in the rules chat, and only from a decision made in the governance chat.

Weekly planning support, broken down

ElementWhat it is here
The question behind itWhat is the week for, given that most of it is already committed?
The operating moveFix the week's commitments first, then place at most three outputs against the remainder.
The unit that mattersA week whose commitments are fixed first and whose outputs are placed against the remainder.
What looks like progress and is notMore items placed, which measures ambition at the least informative moment of the week.
Evidence that it is workingOutputs placed against outputs completed, read at the end of the week.
Where this stopsOrganizational support only. It is not clinical, legal, or financial advice.

Common misreadings: weekly planning support

ElementWhat it is here
What it is usually mistaken forNeeding to plan more. Most weeks are over-planned and under-subtracted.
The metric that misleadsNumber of items placed. It measures ambition at the start of the week, which is the least informative moment.
What to do in the first weekPlace at most three outputs for the week and leave the rest unplaced. Read what happened on Friday before changing the number.
Where this stopsOrganizational support only. It is not clinical, legal, or financial advice.

Chat responsibility split

ChatHoldsLifetime
RulesStanding instructions, modes, boundaries, definitions.Permanent. Edited deliberately and rarely.
RuntimeToday's plan, today's work, today's mess.One day. Discarded without regret.
GovernanceArguments for and against changing a rule.Ongoing. Produces decisions, not work.
Anything elseNot part of the architecture.If a fourth chat appears, one of the three has lost its job.

Worked example: Three-Chat Architecture applied to weekly planning

Use it when one long assistant thread has become both the rulebook and the daily workspace, and the rules have started drifting.

What is the week for, given that most of it is already committed? Fix the week's commitments first, then place at most three outputs against the remainder.

Create a rules chat that contains only the standing instructions. Never do daily work in it.

What to measure. Outputs placed against outputs completed, read at the end of the week.

Running Three-Chat Architecture for weekly planning support

A single thread mixes three incompatible jobs: holding stable rules, running a disposable day, and deciding what the rules should be. The daily traffic pushes the rules out of context, so the rules quietly change without anyone deciding to change them. Splitting the three gives the rules a location that daily volume cannot displace.

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 weekly planning support.

What this is not. It is not a feature of any particular assistant product and does not depend on saved memory, projects, or custom instructions existing.

Evidence that it is working: outputs placed against outputs completed, read at the end of the week.

Organizational support only. It is not clinical, legal, or financial advice.

Frequently asked questions

What does Three-Chat Architecture actually mean?

A single thread mixes three incompatible jobs: holding stable rules, running a disposable day, and deciding what the rules should be. The daily traffic pushes the rules out of context, so the rules quietly change without anyone deciding to change them. Splitting the three gives the rules a location that daily volume cannot displace.

When does it stop applying?

It is not a feature of any particular assistant product and does not depend on saved memory, projects, or custom instructions existing. Organizational support only. It is not clinical, legal, or financial advice.

What should a reader do in the first week on weekly planning?

Place at most three outputs for the week and leave the rest unplaced. Read what happened on Friday before changing the number. Needing to plan more. Most weeks are over-planned and under-subtracted.

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

This is one of the frameworks inside the Billionaire High Performance Coach system — a structured executive OS for using ChatGPT as your accountability and decision partner.

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.

Related pages

Weekly and long-range planning elsewhere in the library

See all weekly and long-range planning pages