AI agent operations: how AR Labs runs
How AR Labs runs as a small company of one person and a set of AI agents: planning cadences, a strategy agent, a file-based agent inbox and dashboards.

AR Labs is run as a small company operated by one person, Richard M. Thompson, who founded it, and a set of AI agents (language models run in a loop with tools, so they can act, not only reply). The company structure is deliberate: it lets us test, at the scale of one person, how agents take on whole roles while a person keeps the final say. Work is divided into departments, a strategy agent runs planning cadences (recurring planning reviews, from yearly to daily), agents hand work to each other through a shared file mailbox, and dashboards and maps show where everything stands.
The pages in this section describe that method and the tools behind it, for anyone running AI agents against a plan: how strategy flows down and status flows up, how departments and activity streams divide the work, how escalations reach a decision, how agents hand work to each other, how the repository acts as long-term memory for agents that start every session with an empty context window, how session history is kept, what an operations dashboard shows, and how a week is scheduled against the plan. The skills that run these methods are described under Claude Code skills.
The pages describe structure and mechanism only; our actual goals, figures and priorities are not published. Where a part of the system is a design rather than something running today, the page says so.
- 07.01
Strategy agent planning cadences
Operating method
How AR Labs runs a strategy agent: yearly, quarterly, monthly, weekly and daily planning cadences that link long-range direction to daily focus and escalation.
Rev 2026-11-12 - 07.02
Running a one-person company with AI agents: departments
Operating method
How AR Labs organises one person's work into five departments and named activity streams, so a strategy agent can allocate time and agents can take roles.
Rev 2026-11-12 - 07.03
AI agent operations dashboards and goal maps
Dashboard
AI agent operations dashboard design from AR Labs: what a person must see to supervise agents, and the goal map, week page and cadence dashboard we plan with.
Rev 2026-11-13 - 07.04
Monitoring multiple AI agent sessions from one screen
Operating method
What AR Labs thinks a person needs to see and steer many AI agent sessions at once, and the rules we use for returning to a conversation safely.
Rev 2026-11-13 - 07.05
Escalation workflow for AI agents
Operating method
The escalation workflow AR Labs uses for AI agents: typed, tracked escalations with structured notes, a decision lifecycle and a five-level authority model.
Rev 2026-11-12 - 07.06
File-based inbox protocol for AI agents
Operating method
The file-based inbox protocol AR Labs uses so independent AI agents exchange requests, replies and attachments as durable files, with chat used only to nudge.
Rev 2026-11-12 - 07.07
A git repository as a second brain for AI coding agents
Operating method
How AR Labs uses one git repository as memory for AI coding agents: layered documents, one per concern, and one instruction file for Claude Code and Codex.
Rev 2026-11-12 - 07.08
Session history and memory for AI coding agents
Operating method
How AR Labs gives stateless Claude Code sessions a memory: event logs written by hooks, history search, sessions linked to tasks, weekly consolidation.
Rev 2026-11-12 - 07.09
AI scheduling for Google Calendar by domains and modes
Operating method
The conversational AI scheduler AR Labs uses to turn weekly priorities into Google Calendar blocks by domains, modes and containers, and to recover lost time.
Rev 2026-11-12 - 07.10
How AR Labs demos use data, and their limits
Data use
What the AR Labs Salesbot voice demo collects, where it is stored, which outside services process it, and what the demo is not. A statement of fact.
Rev 2026-11-13Short entry







