The fleet

Agents & governance

Named agents with curated tool grants work a durable queue through a lease → checkpoint → events lifecycle. What they produce is proposals; what they cannot do is act outward on their own.

Named agents, curated tools

The fleet is a roster of named agents — finance, customer feedback, marketing, a librarian, and the rest — each carrying exactly the tool grants its job needs. Grants are curated per agent, so capability is a property of the role, not of whoever wrote the prompt.

Agents carry skills — house playbooks for how this company does things — and share the Company Brain, so a run starts from what the company knows rather than a blank context window.

The run lifecycle

queue

Work enters as queued runs — from automations, the Coordinator, or a person.

lease

A worker leases the run; leases expire, so a dead worker's run is picked up, not lost.

checkpoint

Long runs checkpoint progress; a resumed run continues instead of restarting.

events

Every step lands in the run's event stream — the run is replayable and auditable after the fact.

The lifecycle is what makes an agent workforce operable: you can see what every agent is doing, interrupt it, and read exactly what happened afterwards.

The approval gate

Agent output lands as proposals on the workboard — a drafted reply, a plan, a card, a change. A person approves, edits or rejects. Approval is the act that lets anything touch the world.

Physically absent, not discouraged

Outbound tools — sending mail, posting, deploying, spending — are not in the tool catalog autonomous runs execute with. The gate is architecture, not policy.