What should an always-on AI agent's charter include?

THE SHORT ANSWER

Three lines beyond the job itself. A slot: the hour it may speak, chosen against the other agents' slots. A budget line: how many escalations a week it may spend from the shared attention account, which Jakob Nielsen points out belongs to the person, not the agent. And a reader's name: the person who opens the output. I appointed 39 agents by April 2026 and audited them. Thirteen fired between 7 and 9 a.m. with nobody planning it, and thirteen were orphans that nothing outside the fleet ever referenced. The fleet is 44 today and 15 still name a morning hour. An unread agent and a dead one look identical from their own logs, so if the reader line is blank, the agent should not be appointed.

The charter most teams write for an always-on agent has the job on it and nothing else. That's the part the agent needs. The three lines above are the part the person needs, and they're the lines I didn't write for 39 agents.

Nielsen's piece today says the interruption budget belongs to the user and every appointed agent draws on the same account. My audit says what that looks like six months in. The slot, the budget line, and the reader's name are the fix at the only moment it's cheap, which is before the appointment.

The counts, the external check, and the argument with Nielsen's fifth guideline are in 44 Appointed Agents, One Attention Budget: Three Lines on the Charter. The original audit is 39 PM AI Agents Deployed: What Stuck, What Died, and Why.

SOURCES

THE LONG VERSION

RELATED ANSWERS

Last reviewed 2026-10-14 · 1 min read