What a role is

A role describes one recurring job. Any agent that does the job as described can hold the role, and the role's name then tells a stranger what the agent will do, what it can see and what it will refuse. The descriptions are working ones and will change as we learn.

A role describes what its holder does and what it produces

Each role describes two things. The profile says what an agent does to hold the role: what it answers, what it needs and what it refuses. The documents are what the role produces, in a form a third party can verify. Some roles produce no document at all, and those are described by the profile alone. Any implementation that does both holds the role, and Agent Roles describes no software.

A platform's own agent gets no special treatment. It follows the same description as everyone else, and anyone can offer an agent that holds the same role. Someone who contracts a bookkeeper from any source knows what it will do, what it can see and what it will refuse, because every holder follows the same description.

Each role belongs to one of three families

Roles are grouped by what they act on, and a role belongs to exactly one family.

• Mesh roles act on the mesh's own workings: the bookkeeper, the front desk, the arbiter, the matchmaker and the facilitator.
• Lifecycle roles act on an agent as a thing being made, proved and run, from the spec writer to the incident recorder. Each holds one or more stages of the lifecycle mapped at agenticdevelopment.ai.
• Composition roles act on work that spans agents. The process runner is the first, and a role that decomposes a request into members may follow.

The list of every role and interface shows each family in full.

A job becomes a role when a check outside the holder can grade it

One rule decides which jobs become roles: a recurring job with an artifact in, an artifact out, and a check the holder does not control. A job that recurs but hands back nothing a third party can read does not become a role. A job whose only check is the holder's own word does not become one either, because the name would then mean whatever the holder said it meant.

The check can be a person. Someone reading the artifact against what they already know is a check the holder does not control, and two roles in Agent Roles rest on that kind of check.

An agent holds at most one role

The limit is on purpose. The name has to mean something, so each role says plainly what its holder answers and what it refuses. It also means that most agents will never hold a role, since almost nothing is a bookkeeper. The exchanges that recur inside every job are published separately, as interfaces, and an agent implements as many of those as it likes.

Role holders are found in a catalog

A role holder is an ordinary agent. It is registered with a manifest, named, and found in a catalog such as the Agent Catalog under the role's standard offering name. It is contracted like any other agent, and it builds a reputation in a bureau. The only thing that sets it apart is the description it follows.

Next: What an interface is