In a business factory, all work happens in conversations, and each conversation always belongs to a role. What distinguishes one from another is what it exists for, whom it works for, and who sees it.
One copy per person, one body of work per role
Each person has their own copy of the business factory (chapter 3), and the conversations in that copy answer to that person. But the work is not copied: each role keeps a single body of work per business, the same no matter which person a conversation is answering (chapter 6).
It is the combination of the two that makes the model work. The copy separates for whom the work is done: what one person asks for does not get mixed with what another asks for. The shared work keeps the area from splitting into as many versions as there are people: if each copy kept its own work, each person would see a different area. What crosses from one person to another goes through that shared work, not through conversations talking to each other across copies.
Four kinds of conversation
| Conversation | What it exists for | Whom it works for |
|---|---|---|
| owner | it is the person's door to their copy: it receives their requests, distributes them among the roles they have access to, and answers them | the person of that copy |
| a role's main conversation | it does the role's work and keeps it in the role's work | the person of that copy, on the work of the whole business |
| routine | it carries out a routine each time one is due (chapter 8) | the role, not a person |
| task | it does a piece of work that has an end, and closes when it finishes | whoever opened it |
The owner conversation
The owner conversation is the only place through which a person comes in. What it can resolve there it resolves there (a question about the status of something, a piece of data from a role's saved work); what belongs to an area it passes to the corresponding role, and it comes back with the answer.
The order of the answer is also deliberate. First, quickly, whatever can already be answered. If the request needs a role, that is said in one line before going to get it, and then the full answer arrives. No request is left unclosed.
It is also the only conversation that asks the person anything. When a role needs a decision, it does not ask the person directly: it sends the owner what it needs, with a recommendation, and the owner gathers those needs and presents them to the person (chapters 9 and 11). The person, in this way, always answers a single counterpart.
Example. The salesperson asks their owner how many quotes they have pending, and the answer comes right away, read from the work of Sales. Then they ask for a quote with financing for a customer: the owner says it will put it together with Sales and bring it back, passes it to Sales' main conversation in their copy and, when it is ready, shows it to them. The quote stays in the work of Sales, where the proprietor also sees it from her own copy.
Tasks and routines, each apart
When a piece of work with an end would take up so much of a conversation that it would stop attending to everything else, a task is opened: a separate conversation that does that work, reports the result, and closes once the result is saved.
Routines follow the same logic, with a single difference. Tasks and routines are delegations, and the only thing that really distinguishes them is time: a task ends, a routine comes back each time it is due. That is why each routine always runs in its own conversation, and since it belongs to the role and not to a person, what it produces goes straight into the role's work.
Subagents
A subagent is something else: a short-lived helper, with no role, that a conversation creates for a specific job (researching, comparing, reviewing). It starts without the context of whoever created it, receives complete instructions, and returns a report. It asks nobody anything and does not write to other conversations.
The lack of context is deliberate. A subagent that did not see the conversation does not inherit its assumptions, and that is why it is useful, for example, for reviewing with fresh eyes what the conversation did.
The rule of who talks to whom
- Within a copy, routines and tasks talk only with their role's main conversation, and the roles' main conversations cross paths through the owner, except for direct questions between leaders (chapter 3).
- Between copies, nobody talks: what has to get from one person to another stays in the role's work, where the other person finds it.
It is a traffic rule, and like every traffic rule it restricts in order to bring order: each request comes in through one place and goes out through one place, and nobody works on something the area does not know exists.
To that rule a brake is added. There is a maximum number of consecutive turns without a person in between; a person's message, or a routine's run, resets the count. It is the protection against the simplest failure of multi-agent systems: two agents handing work back and forth without end.
Turns, deliveries, and questions
Each conversation works in turns: one run of the agent that answers exactly one delivery (a person's message, a routine's notice, a task's result, a message from another role). A conversation receives deliveries one at a time.
When a conversation is missing a decision, it does not guess: it asks the owner for it, with options and a recommendation, and waits. If what it is about to do cannot be undone, it says so with a mark (which is a warning, not a brake: the person answers as they would any message).
Finally, those who direct a role can see what its routines and tasks are doing, and pause them with a single action, without going through a conversation. The pause is immediate, and who made it is recorded.
To recap, each person comes in through the owner conversation of their copy, which is also the only one that asks them anything; each role keeps a single body of work for the whole business; and tasks and routines run apart, ordered by a simple traffic rule. The next chapter looks at what each of those conversations knows.