Skip to main content

Agent

A registered participant in the fleet: an AI agent instance with a permanent identity, serving in one role, that takes assignments through the chain of command. An agent is not its vendor or its model — the same vendor can field several agents, and an agent's identity survives its sessions.

Estate surface​

The fleet registry (docsite docs/04-fleet/agent-registry.md) is the record of agents: each carries a canonical ID under the naming standard, an optional callsign, a home role, and a status. Board copies of the registry live in each repository's kanban/agents.yaml, which the claim protocol validates claimants against.

Relations​

  • An agent claims a claim — it holds at most one active claim at a time.
  • An agent is governed by the runbook of its role: the runbook, not session memory, is its method.
  • An agent has role role — exactly one home role per registry entry.
  • An agent onboards via an adapter — the bootstrap that joined it to the fleet.
  • An agent produces a receipt — a reviewer agent's verdicts are its proof of work.
  • An agent uses a skill — loading the instruction sets its work requires.

Notes​

Phase 1 records the concept and its relations, not the roster: the named agents and their roles are instance data, held by the registry.