Version 1 ships the trunk: a working multi-agent workspace with persistent, auditable memory. Every capability beyond it is a branch that grows only when the user chooses it. The same branching grammar repeats at every scale, so the tree can grow outward and upward indefinitely without ever changing its trunk. Design specification by Beth Sea.
How the tree grows. The product makes no assumption about its use case. It ships as a trunk: memory, seats, briefings, and consent machinery, working on day one. Every fork above the trunk is a decision the user makes: add a role, deepen verification, shape what the system may remember, extend its reach. Decline, and the branch stays a bud. Choose, and it unfurls. Revoke, and it folds back. Each authorization is dated, revocable, and visible in settings, and no branch can grow itself: forks only open from the trunk side, by the user's hand.
Why a fractal. The branching rule is the same at every level. A household tree and an enterprise canopy grow by the identical grammar of choice, which is why one design serves both, and why the tree never outgrows its owner: however tall it gets, every branch traces back to a decision somebody made on purpose.
Use-case templates are pre-grown branch patterns the user can start from and reshape freely. Three examples of the same trunk grown three ways:
verification grown deep; claims re-checked against sources before anything is kept
seats grown wide; drafting, editing, and archive roles working one document
memory grown rich; a household record with confirmation gates on everything inferred