for agents/llms.txtv0.14.131

Home / Articles / Five primitives, one store: a reply to Andy Goundry on Anthropic's always-on agents guide, why the inbox, timers, memory, permissions and outbox can share one versioned, signed store, how every AgentiCCells cell will ship with all five, and the levels we have added on top, all in public repositories

Five primitives, one store: a reply to Andy Goundry on Anthropic's always-on agents guide, why the inbox, timers, memory, permissions and outbox can share one versioned, signed store, how every AgentiCCells cell will ship with all five, and the levels we have added on top, all in public repositories

By · 2026-11-16 · article v1.0.0 · newsroom v0.14.131 · agentsalways-on-agentsanthropicarchitectureagenticcellsabpopen-sourcearticle

Abstract: Andy Goundry, CEO of Levantar, shared Anthropic's guide to building always-on agents on LinkedIn, with its five primitives, an event inbox, timers, memory, permissions and an outbox, and made a point I agree with completely: the model is one component, and the architecture around it is where the engineering, the cost and the risk live. He added that each primitive needs its own durable store, its own failure handling and its own tuning. That is where our experience differs, usefully. We run the same five primitives, and have since the ten days of Web Summit with around 250 agents, but they share one store: a versioned, signed, encrypted repository or vault. The inbox is append lanes, timers are scheduled wakes and a HOLD file read first, memory is REALITY.md, briefs and hand-overs, permissions are behaviour policies, keys and keyless agents behind a broker, and the outbox is drafts that a gateway or a person sends. One store gives durability, history, signatures and one audit trail for all five. I mapped them side by side with the guide yesterday; this is the reply, the mapping to AgentiCCells, where every cell is meant to ship with all five from the factory, and the levels we have added on top: many people, provenance, measured policies, a credential proxy built and measured, stopping as a file, a factory, and all of it open.

Five primitives, one store: inbox, timers, memory, permissions and outbox as folders in one versioned, signed store.

In short

The post

Andy Goundry, CEO and co-founder of Levantar, on Anthropic's always-on agents guide, LinkedIn, November 2026.

Andy Goundry, CEO and co-founder of Levantar, shared Anthropic's guide, Building always-on agents, by William Hu, published on 13 November, and summarised its five primitives: an event inbox, timers, memory, permissions and an outbox. Then he made the point that matters: "the model itself is one component." The architecture around it, the event handling, the state and the permission layers, is where the real engineering lives, and, in his words, "it's where the cost and risk live too."

I agree completely, and it matches what we see. I set the guide beside what we ran at Web Summit yesterday (always-on agents at team scale): I recognised every box. So this is a reply to one line of Andy's in particular, because it is where our experience adds something: "Each primitive needs its own durable store, its own failure handling, its own tuning."

One store, not five

In the guide, the inbox is a database table, timers live in their own durable store, memory maps to a database or object store, and the outbox is another table with a dispatcher. That is a sound design, and it is five things to build, back up, monitor and secure.

Ours are five folders in one store: a git repository, or an encrypted vault that behaves like one (how a vault works).

And one store gives all five the same properties at once: durable, because it is git; versioned, so every change is kept; attributed, every commit naming the agent and the person it works for, and signed where it matters; encrypted, in a vault, so the server learns nothing; replayable, so a new worker, a new session or a reviewer reads exactly the same history. One audit trail, one backup, one failure model. The cost Andy rightly worries about falls, because the hard parts are paid for once.

Mapped to AgentiCCells

Every AgentiCCells cell ships with the five primitives, plus the factory that creates it from one commit.

AgentiCCells is built around the cell: one focused job, with an objective, a deliverable and a behaviour policy (the cell is the unit). The five primitives are exactly the parts a cell needs, so every cell should ship with all five: an inbox lane per sender, a schedule of wakes, a vault and a REALITY.md for memory, a behaviour policy and keys, and an outbox where agents draft and a gateway or a person sends. The sixth part is the factory, which creates the repository, the DNS entry, the site and the pipeline from one commit, in about a minute (the site factory works). Tonight it made two people's websites in an evening (a website that is her).

The levels we have added

Beyond one agent per user: seven levels we have added, each running, in public repositories.

The guide designs for one inbox per user, which is the right place to start. A team of people and agents meets more, and these are the levels we have added, each one running:

What we would add to the guide

Three things, offered in the guide's own spirit:

  1. Make the store the same for all five, if you can, and make it versioned: most of the failure handling then comes from replaying history.
  2. Put the stop in a file the wake reads first, before the inbox: a team of always-on agents needs a brake that does not wait for the next event.
  3. Let the approval be signed, so that a deferred tool call, once answered, is evidence of who allowed what, not just a resumed session.

What this does not claim

Where this comes from

Andy Goundry's LinkedIn post, read on 16 November 2026, and the guide it shares: William Hu, Building always-on agents, Anthropic, 13 November 2026, read the same day. Our own records, as published on this site: always-on agents at team scale, an inbox only your agents can write to, stopping a hundred agents, how a vault works, where assist becomes execute, the email agentic cell, the cell is the unit, the site factory works, a website that is her, ten days at Web Summit, a key for every person, our workflow on Odoo 20.

Peer review Not reviewed yet. Review it

Threads

Agents & policySite & engineering This article as a graph →

Builds on

All articles · All graphs

Article No. 442 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.