A role's knowledge is everything that tells it how to behave and how to do its work. It is made of three kinds of piece (instructions, skills, and memories), and each piece lives at a level, which says whom it applies to.
Three levels
| Level | Applies to |
|---|---|
| business | every role |
| role | that role, in all its conversations |
| person | that person, in their conversation |
The levels do not form a hierarchy. They go from the broadest to the narrowest, but none overrides another: role and person are two dimensions that cross in each person's conversation. A piece's level is chosen when it is created and does not change.
The reason for having levels is to avoid contamination. Some things belong to the whole company («all customers are addressed on a first-name basis»), others to a job («this is how a quote is put together»), and others to a person («prefers short answers»). Mixing them in a single pile makes the personal end up in the general, and someone's preference becomes, without anyone meaning it to, a rule for everyone.
When two pieces clash
The agent receives the sum of the levels that apply to it, and no level wins by rule. If two instructions contradict each other, the agent decides with judgment and, if asked, explains why. The healthy thing, when that happens, is for a person to correct the instruction that is wrong.
It might seem tidier to set a priority (the person wins over the role, the role over the business). There is a case for the opposite view: a fixed priority rule works in the common cases and fails in the rare ones, which are precisely the ones that matter. It is better for the agent to reason and for people to fix the source of the clash.
Instructions and skills
An instruction says how to be: «always speak on a first-name basis, and never promise delivery dates without checking with the workshop». A skill says how to do one concrete thing, and the agent reads it only when it needs it. Skills are usually of three kinds:
- those that explain how to use a tool (its map, how to get in, the common tasks and their pitfalls);
- those that explain how this business does a type of work with its tools;
- those that say what to do when something fails or a person is needed.
The skills the business writes live in the business definition, at its three levels. Those that say how every business factory works (how roles hand work to one another, how finished work is kept) are part of the blueprint, and they are updated without touching the business's own.
Memory: each level written by its own
A memory is a fact about how to behave that a conversation saves for later. It is written without asking for confirmation, and stays in view, with its history, so that a person can correct it or undo it.
Who writes each level is fixed, and each level is written by its own:
| Level | Written by |
|---|---|
| role | the role's main conversation, in any copy |
| person | that person's owner conversation |
| business | the owner, and only in the copy of someone who has access to change what belongs to the business |
Routines and tasks do not write memory. What they learn about the work stays in the role's work (chapter 6).
Memory is not work. Memory keeps how to behave («the proprietor likes one-page reports»); the state of what is being done («yesterday's customer quote is on its second version») goes into the role's work. The distinction keeps memory from filling up with data that goes stale in days.
Memories are not orders. They are presented to the agent as notes, with who wrote them and when, and the agent treats them as data. A memory that looks like an order is not followed as one, and this matters more than it seems: it is one of the doors through which a malicious text could try to take up residence in an agent system.
What is always loaded, kept short
There is a part of the knowledge that every conversation reads when it starts: the common rules, the business's instructions, and the role's. That part should be short. Every line that is always loaded is paid for in every conversation, and a long text that nobody rereads ends up being noise (chapter 19).
The practice that works is simple: what always applies stays in what is always loaded; the history of why something was decided, the quotes, and the dates go to a separate record that is consulted when needed; and what belongs to a single role goes into that role's knowledge, not everyone's. A glossary, for example, is consulted when a doubtful term comes up, instead of being read in full every time.
What knowledge never does
Knowledge informs, but does not authorize. An instruction that says «customers can be deleted without asking» does not raise anyone's ceiling. The ceiling is access (chapter 3), and it holds firm whatever the knowledge says.
In short, knowledge lives at three levels that add up without a hierarchy, each level is written by whoever it belongs to, and nothing that is known widens what can be done. The next chapter looks at where what each role does is kept.