One brain. Many situations.
A branch is a named partition inside a single brain, Acme, the Series A, the hiring lane. Not a git fork. Reads walk child to parent to main; siblings never leak.
The branch the situation implies.
Sessions can pin a working branch, inherit from the folder you are in, or follow the name a recall already uses. The brief says which partition you are reading, and why.
- Child → parent → main, never a sibling
- Health is derived: empty, at risk, stale, active
- Depth capped; main has no parent
- Ingest files under the session branch
What you see is what the brain owns.
The graph view shows the nodes that live on that partition. Inheritance is for reading and recall, not a silent copy into every branch.
Callable from main is not the same as listed on a fresh branch.
Nest under a parent when the situation splits further.
Customer-facing branch never means merge-and-rebase.
Built for how work actually splits.
Deals, clients, and projects are partitions of attention. Branches give the brain the same shape, so Cursor and Claude do not answer from the wrong account.
- Name a branch when the question is about one situation
- Leave it unset to read across the whole brain
- Past-due plans roll up into at-risk health