The six brain files
| File | Purpose | Who updates it |
|---|---|---|
| Soul | Personality, tone, values, and hard limits | You |
| Procedures | Step-by-step workflows and escalation rules | You |
| Heartbeat | Scheduled tasks — what to check and when | You |
| Memory | Contacts, decisions, patterns, and context | The employee (grows over time) |
| Tools | Connected integrations (Slack, Gmail, CRM…) | Auto-generated |
| Learning | Performance insights, adaptations, and goals | The employee (self-improves) |
Soul
The Soul file defines who the employee is. It contains their personality, communication style, values, and any absolute limits on what they will and won’t do. You write the Soul file when you hire the employee and update it when you want to change their character or add new guardrails. The employee does not modify this file. Examples of what goes in Soul:- “Always be concise and direct. Never send emails longer than five sentences.”
- “Do not make commitments to customers without board approval.”
- “Prioritize speed over perfection on first drafts.”
Procedures
The Procedures file contains the employee’s standard operating procedures — step-by-step instructions for recurring situations, escalation rules, and decision trees. You write and maintain Procedures. When you want an employee to handle something in a specific way, this is where you define it. Examples of what goes in Procedures:- How to qualify an inbound lead
- What to do when a task is blocked
- When to escalate versus act autonomously
Heartbeat
The Heartbeat file controls the employee’s scheduled work loop. It defines what the employee should check and act on during each heartbeat cycle. You write the Heartbeat file. It is the employee’s standing agenda — the list of things they do every time they wake up. Examples of what goes in Heartbeat:- “Check the inbox for new support requests and triage them.”
- “Review open tasks and update their status.”
- “Check the CRM for deals that haven’t been touched in 3 days.”
Memory
The Memory file stores everything the employee has learned about their work: contact details, past decisions, recurring patterns, and ongoing context. The employee writes and updates Memory autonomously. It grows every time they complete a heartbeat. You can read it at any time, but you don’t need to manage it — the employee does. Examples of what gets stored in Memory:- “Alice at Acme Corp is the decision-maker. She prefers email over calls.”
- “The engineering team uses linear for task tracking.”
- “Last week’s campaign had a 3.2% click rate.”
Tools
The Tools file lists every integration the employee has access to: Slack, Gmail, GitHub, Salesforce, and so on. It is auto-generated by Zmeel based on the connections you’ve set up for that employee. You connect tools through the employee settings. Zmeel then keeps this file up to date automatically.Learning
The Learning file is where the employee tracks what’s working, what isn’t, and how they’re adapting their approach over time. The employee writes this file autonomously as they accumulate experience. You can read it to understand how an employee’s behavior has evolved or to identify patterns in their performance. Examples of what gets stored in Learning:- “Subject lines with questions have 40% higher open rates.”
- “Sending follow-ups on Tuesday mornings outperforms other days.”
- “Breaking large tasks into subtasks reduces blocking incidents.”
How brain files work together
On every heartbeat, the employee runs through a consistent loop:Read all six brain files
The employee loads their Soul, Procedures, Heartbeat, Memory, Tools, and Learning files to establish their full context.
Check connected tools
The employee polls their integrations — inbox, Slack, CRM, task board — for anything that needs attention.
Decide what to do
Using their Procedures and Memory as a guide, the employee decides what action to take.
Take action
The employee acts: sends a message, updates a task, creates a subtask, escalates a blocker, or completes their work.
Brain files are stored in the database and injected into every LLM call the employee makes. They are not files on disk — the “file” framing is a mental model to help you reason about each piece of context your employee carries.