Concept map
Main Branch concepts
Last updated May 25, 2026
These are the mental models behind the commands. Read them when you need to understand why Main Branch separates memory, wagers, execution, approvals, and settlement.
Business memory
Business memory is not a prompt dump. It is a repo with named lanes so agents can cite the right context without flattening the business into a stale summary.
| Lane | Files | Purpose |
|---|---|---|
| Core | (voice | offer | audience | proof | soul) | Identity, positioning, and operating rules |
| Judgment | (research | decisions | content-strategy | playbooks) | What the business has learned and chosen |
| Wagers | (bets | pushes | MoneyPath | outcomes) | What is being tested, shipped, measured, and settled |
| Continuity | (checkpoints | books | metrics | systems) | What changed, what it cost, and what carries forward |
Operator loop
The loop is the shape of a Main Branch session: sense what is true, decide the wager, ship through rails, then reflect the lesson back into owned memory.
- Sense
- Decide
- Ship
- Reflect
Offers, bets, and pushes
Main Branch keeps the stable business promise separate from the wager and the execution work. That separation makes agent output easier to check.
| Offer | Durable promise and audience. It changes slowly. |
|---|---|
| Bet | Time-boxed wager with appetite, KPI, timeframe, and kill criteria. |
| Push | Coordinated execution work that moves a bet into the world. |
| Outcome | What happened after the push, including proof, revenue, cost, and lesson. |
MoneyPath
MoneyPath connects attention to the business result. It tracks the offer, proof, channel, call to action, page readiness, revenue, cost, and outcome feedback instead of treating marketing as isolated output.
Approval gates
Main Branch can inspect facts, draft work, and explain tradeoffs. It does not get silent authority over money, accounts, customers, or public surfaces.
| Publishing | Drafts are allowed. Going live requires approval. |
|---|---|
| Spend | Planning is allowed. Budget changes and campaign launches require approval. |
| Provider accounts | Posture checks are allowed. Mutation requires approval. |
| Customer contact | Drafts are allowed. Sending requires approval. |
| Destructive changes | Plans are allowed. Apply commands require approval. |
Books as settlement
Books are the settlement layer for business bets. Revenue, costs, exposure, and cash reality need to feed the reflection loop so future decisions do not drift away from financial truth.
Related routes
Start with mb-start for orientation, use mb-think when a decision needs research, and use mb-end to turn the session into durable memory.
Business Memory
Core files, research, decisions, bets, pushes, books, outcomes, and checkpoints.
Operator Loop
Sense what is true, decide the wager, ship through rails, reflect into memory.
Offers, Bets, Pushes
Durable offers, time-boxed wagers, and coordinated execution stay distinct.
MoneyPath
Attention, proof, revenue, cost, and outcome signals tied to the business result.
Approval Gates
Spend, publishing, account mutation, customer contact, and destructive changes require approval.
Books as Settlement
Financial truth belongs in the operating loop, not after-the-fact reporting.