III · Gnōthi seauton · Know thyself
One truth, never two.
Agents need authoritative systems of record, and should never create an invisible second version of the truth.
Agents act on authoritative systems of record, never on a hidden copy.
In practice
What it means for your system.
An agent that keeps its own copy of a record creates a second version of the truth. We design systems so agents act on your records of truth, and nowhere else.
- Each kind of record has one authoritative home.
- Agents write only where they are authorized, and every write is logged.
- Conflicts are reconciled by agreed rules, with a person deciding the exceptions.
The word for it
Alētheia
ἀλήθεια
Alētheia is Greek for “truth, literally what is not hidden.” Agents work from the record everyone can see.
Why it matters
Two versions of the truth cost more than either one.
When systems hold different answers to the same question, someone has to decide which is right. That reconciliation takes staff time, and it tends to surface after a customer or an auditor has asked.
Agents raise the stakes. An agent that saves its own notes about a customer has created a second record, whether anyone intended it or not. It can then act on that copy at speed, out of sight of the people who own the original.
Agreeing which system wins is a small decision made once. Untangling two histories later is a project. With the hierarchy settled, every action traces back to a record your business stands behind.
Read it accurately
Scope of the rule.
- Copies serve a stated purpose, marked as copies.
- Reports, caches, and backups can hold copies for a stated purpose. They are marked as copies, and decisions are made from the authoritative record.
- Authorized agents write to the authoritative record.
- Agents can update records where they are authorized. Each write goes to the authoritative home and waits for a named person when it is consequential.
- The hierarchy changes when your systems change.
- When a system is replaced or records move, the hierarchy is updated. The record owner approves the change, and its history is kept.
How it is measured
Every rule is something you can check.
A source-of-truth hierarchy, reconciliation logic, and an audit trail for every write.
In an engagement
Where the rule is applied.
The rule is checked at each stage of the work, from the first design to the system in operation.
In the design
System-of-Record Architecture decides where each kind of record lives and who may write to it. The record owners approve that map in writing.
In the build
Custom Agentic Systems connects agents to the systems of record directly. Reconciliation logic is built in, and every write enters the audit trail.
At acceptance
Tests confirm that agents read from the authoritative home and write only where authorized. Sample writes are traced end to end.
In operation
A routine check compares systems and reports differences. A person decides each exception the reconciliation rules cannot resolve.
Check your own system
Five questions to ask this week.
Each one has a yes or no answer. A no marks where to start.
- For each kind of record, can your team name the system that wins when systems disagree?
- Do any spreadsheets hold facts that also live in a core system?
- Does any AI tool keep its own notes or copies of customer records?
- Is every change an agent makes logged with its source and its approver?
- Is there a routine check that finds differences between systems?
Delivered through
The services that apply this rule.
Gnōthi seauton
Know thyself.
We start with how your business actually works.
Apply the rule
Check it against your own system.
Questions
Does this mean consolidating into a single system?
Rarely. You can keep several systems, provided each kind of record has one authoritative home. System-of-Record Architecture sets that map.
Can an agent keep any memory at all?
Yes, for working context such as the task in progress. Facts about customers, orders, or money are read from the system of record each time.
Who decides which system wins?
The owner of each kind of record, often a business lead rather than IT. Engineers propose the hierarchy, and the owner approves it.
How do we check this rule on our own system?
Ask for the source-of-truth hierarchy in writing, and the reconciliation logic that enforces it. Then pick any write an agent made and follow its audit trail.
What about the spreadsheets our team relies on?
Each one is reviewed. Facts that belong in a core system are linked or moved there, and a spreadsheet kept for analysis reads from the record of truth.