Seen from the disk, a business factory is a folder tree with clear rules about who writes where. This chapter describes that tree and the blueprint that generates it.
The tree
<business>/
AGENTS.md the business: who is who, what each person decides
.factory/ how every business factory works; nobody in the business writes it
<role>/
AGENTS.md the role, in the business's words
work/ the role's work: its git repository
.assets/ the role's materials and tools that are not its work
.sessions/
with-person/<person>/ a person's owner conversation (in the coordinating role)
as-routine/<routine>/ a routine's conversation
at-task/<task>/ a task's conversation
Instructions are read from the top down: each conversation reads the business's AGENTS.md, its role's, and its session folder's if it has one, as well as the common rules it receives at startup.
Who writes where
- A name with a dot belongs to the business factory; one without a dot, to the business. Whatever has a dot is generated by the platform.
- A role writes only in its own
work/. What it needs from another role, it asks for. - At the root of
work/there are only folders, and inside them, one file per thing. - A person's conversation folder is a private place for that person, with its own repository; whatever comes from someone's personal connections stays there.
- Routine and task folders keep nothing: what has to last goes to
work/. A turn's scratch work goes to a temporary folder outside the tree, which is emptied after each turn. .assets/holds what the role uses but that has its own origin (tool repositories, materials): it is not cloned with the business factory.
Cloning a business factory
One consequence of these rules: to clone a business factory, each role's work/ is enough, plus its data store (chapter 14). Everything else (the session folders, the common rules, the permissions) is generated again. It is the simplest test that the separation between what belongs to the business and what belongs to the business factory has been done right.
The blueprint
On the inside, the blueprint (chapter 1) is versioned code that lives in the coordinator. It takes three things:
- the business definition (its roles, its knowledge, its connections);
- the directory of people (who has access to what);
- a version of the blueprint;
and produces the files for each folder, the access table and the list of conversations that must exist. When any of that changes, it regenerates them. Blueprint versions only move forward: a business factory never goes back to an earlier folder design.
If a business factory runs in two places (a local computer and the cloud), it is best for both to come from a single template with blocks marked for each side, so that the rules do not drift apart over time.
Permissions, generated
Each conversation's permissions (chapter 13) are also generated at startup, from a base list with placeholders for the root and the role: they are filled in for whoever the conversation belongs to, the conversation is forbidden from writing in other roles' work and, except for owner, it loses the tool for asking a person a question. The rule stops being a sentence and becomes a permission (chapter 10).
To recap, a business factory is a tree where whatever has a dot belongs to the platform and whatever does not belongs to the business; each role writes only in its own work; it is cloned with the work/ folders; and a versioned blueprint generates everything else. Part V returns to people: how a business factory is directed. The appendix, for its part, turns these four chapters into a guide an agent can follow.