2. Knowing and doing

The architecture of a business factory rests on a separation: on one side, the definition of what the business is; on the other, the execution of what its agents do. The first describes; the second works. Neither replaces the other.

The business definition

The business definition is the record of how the business operates: what roles it has, what work each one does, with which tools, with what knowledge, and how far it is from its goals. It has no people and no conversations: it only describes.

That record is the source of truth. When a conversation starts, it reads from there what its role knows and what it can do; when someone changes an instruction, they change it there, and from that moment on every conversation of the role sees it the same way.

Execution

Execution is the business factory at work: the agents, each in its role, conversing, thinking, and acting. A coordinating component reads the business definition and assembles the business factory according to it (which conversations exist, what falls to each one), and the conversations run on a machine of the business's own, isolated from the others, which goes to sleep when there is nothing to do and wakes up when a message arrives or something falls due.

The shift this implies is worth pointing out. In a first version of this kind of system, it is usually the same service that thinks for the agents and stores everything else. In this model, the coordinator stops thinking and starts coordinating: it decides which conversation has to answer what, and the thinking happens on the business factory's machine, with an artificial intelligence engine that each business chooses.

Why separate them

The main reason is the pace of change. What a business is changes little and is decided by a person; what its agents do happens all the time, conversation by conversation. If both lived together, any conversation could rewrite the business, by mistake or through a malicious text that came in from outside.

Kept apart, each one has its own rules:

Business definition Execution
What it holds roles, knowledge, connections, goals conversations, turns, work in progress
Who changes it people with access for that, or their conversations when they ask for it the agents, all the time
What happens if execution is erased nothing of the business is lost it is reassembled from the definition

The last row is perhaps the most important. A business factory can be destroyed and brought back up without losing anything of the business, because everything that matters lives in the definition or in each role's saved work (chapter 6), and never only in a conversation's memory.

Example. In Ópticas Horizonte, the business definition says there is a role «Sales», that it follows the skill «How to put together a quote», and that its goal is to close 120 sales a month. When someone writes to Sales, the business factory reads that, and only then does the agent answer. If tomorrow the business factory's machine is replaced by another one, Sales still knows exactly the same things.

A small core and extensions

The same logic applies to the rest of the system. What has to be always on (people's identity, the business definition, the coordination of the agents, the event wire between services, and spending control) forms a small, stable core. Everything else (a customer tracking system, a document archive, mechanical processes, integration with a messaging platform) comes in as an extension.

The rule runs one way only: the core never depends on an extension to work; extensions, on the other hand, can use the core. Extensions add capabilities to the core; they do not replace it.

To recap, the business definition knows and the business factory does; the first is the source of truth and the second can be rebuilt from it. With that separation as a base, Part II goes through how work is organized inside the business factory.