Anyone who has been through an ISO audit has heard it: if it isn't written down, it didn't happen. The auditor doesn't take your word for it. They ask for the record.
Bots need this rule even more than people do.
Records in ISO
In an ISO quality management system, records are Level 4. ISO calls them retained documented information. They're the evidence that work was done the way the procedures and work instructions say.
A record is things like a signed inspection sheet, a training log or a corrective action report. It has a date. It shows who did what. It's kept, and it isn't quietly changed later.
Why bots need it more
A person who forgets something can often reconstruct it. "I'm pretty sure we agreed on Tuesday." A bot can't do that. When the chat ends or gets shortened, what was said in it can be gone. See How bot memory works.
So for a bot, the rule is: the file is the record, not the chat.
| Lives in chat | Lives in a file |
|---|---|
| Disappears when the session ends | Stays until someone changes it |
| Can get shortened and summarized | Stays word for word |
| Only this bot sees it | Other bots and people can open it |
| Hard to audit | Easy to audit |
What should be a record
- Decisions: what was decided, by whom, when.
- Approvals: who said yes to what.
- Finished work: the version that actually went out.
- Test results: what was checked, and whether it passed.
- Changes: what changed in the bot's instructions, and why.
Records don't get edited
A record shows what happened. If something changes later, you add a new record. You don't rewrite the old one. That's what makes records trustworthy.
A real example
Our AN Creation office bots have a save skill with a few simple steps. Finished records go into a set folder. A dated copy goes into a History folder. After saving, the bot reads the file back and checks it, so "saved" really means saved. Once saved, a record isn't edited. That's a rule in the skill, not something the system enforces, so it depends on the bot following its work instruction.
In our review of 90 published marketplace templates, only 9 spelled out "the file is the record, not chat" (good-practice.md). It's rare, and it's one of the most useful rules a bot can have.
Re-read before acting
The flip side of writing it down is reading it back. A good bot re-reads the plan file before it acts, instead of working from what it half-remembers. That's ISO's operational control: do the work from the controlled document.
What this means for you
- Ask every bot: where do your records go?
- Keep chat for working, files for keeping.
- Add new records instead of editing old ones.
- When you check a bot's work, check the file, not its summary.
If the bot can't show you the record, treat it as if it didn't happen.