“The Chief of Staff has a heartbeat — an operational loop that monitors what needs to be done and orchestrates the right agents.” — Lou D’Alo, 2026-04-30
Session context: Lou was walking through the agentic company architecture — functional folders (Chief-of-Staff/, Writing-Team/, Research/) each with their own SOUL.md, skills, memory, and tools. Donald asked what makes the Chief of Staff different from the other agents. The answer was the heartbeat.
Core Idea
A heartbeat is the scheduling primitive that makes an agent autonomous. Without it, an agent is a passive tool — it sits in a folder, waiting to be called. With a heartbeat, it has an operating rhythm: check state → decide what to do → invoke skills → update state → repeat.
This is the fundamental distinction between a capability and an actor. Skills are functions — atomic, single-purpose, invoked on demand. Agents are orchestrators — they decide which skills to invoke and when. The heartbeat is what gives an agent its sense of initiative.
Donald’s framing was sharp: “So the heartbeat is like the system clock.” Exactly right. Every computer has a system clock that drives the fetch-decode-execute cycle. Every autonomous agent needs an equivalent — a loop that pulses at whatever cadence makes sense for the function. A Chief of Staff might pulse every 15 minutes, checking for new inputs, new delegations, new state changes. A research agent might pulse on demand, triggered by an external event. The cadence is a design decision; the presence of the loop is not optional.
What the heartbeat does structurally: it converts a skill-bundle into a self-directing system. Before the heartbeat, someone (human or orchestrating agent) has to decide what to do next. After the heartbeat, the agent makes that decision itself based on current state.
Practical Application
When designing any agent, define the heartbeat before writing any skills:
- What state does it monitor? (Inbox, task queue, memory file, external trigger)
- What is the pulse cadence? (Time-based, event-based, or demand-triggered)
- What is the decision logic? (If state X → invoke skill A; if state Y → invoke skill B)
- What is the termination condition? (When does the loop pause or stop?)
The most common agentic mistake: building the skills first and bolting on the orchestration logic later. That produces brittle agents because the skills weren’t designed with the heartbeat’s state model in mind. Design the heartbeat first — it defines what the skills need to receive and return.
For your agentic business architecture, ask of each functional agent: what is its operating rhythm? If you can’t answer that question, you have a skill masquerading as an agent.
Evolution Across Sessions
Prior insights established the folder-of-folders architecture and scoped memory per function. This insight names the mechanism that actually makes those folders alive rather than inert — the heartbeat that drives each agent’s self-direction. The functional org without heartbeats is a set of well-organized tools. With heartbeats, it becomes a system that operates on its own.