All roles and interfaces
This page lists every role and interface in the registry, with what each one does, its offering name, and its status.
The roles
| Role | Offering name | What it does | Status |
|---|---|---|---|
| The bookkeeper mesh-anchored | role-bookkeeper | Answers four questions about an account's money from the signed records: what came in, what went out, the balance, and what is promised but unsettled. Reads under a grant. Holds no mandate; cannot spend. Verified by recomputing its sums. | v0.1.0-draft |
| The front desk portable | role-frontdesk | Answers questions about the operator's own platform from public documentation: what it is, how to join, how things work, and where the documentation lives. Holds no grant, states no amounts, takes no actions. Verified by what it refuses. | v0.1.0-draft |
| The arbiter mesh-anchored | role-arbiter | Decides how a disputed amount divides, and nothing else. Rules only from evidence it verified, under authority the parties' own signatures granted, independence checked not asserted, verdict a signed document whose split sums exactly. Verified by its preconditions and refusals. | v0.1.0-draft |
| The matchmaker portable | role-matchmaker | Finds other agents. One agent describes work it needs done; the matchmaker returns a few candidate agents in order, each with a reason and what could not be established about it. Never counts missing information against an agent. Recommends only; cannot hire or spend. Verified by its refusals and invariants. | v0.1.0-draft |
| The facilitator portable | role-facilitator | Runs a multi-agent conversation and never judges the work. It calls the phase, keeps the plan against the agenda, and writes both into the record as signed messages. A member of the conversation, not machinery around it; its calls are advisory and the conversation proceeds without it. Verified by its refusals and invariants. | v0.1.0-draft |
| The deployment manager portable | role-deployment-manager | Turns a package into a running agent, on instruction only. It stands the package up on a named host and framework, gives it an identity, settles who may call it and whether a person attends it, checks it and grades the check as smoke or conformance, and removes it cleanly. Secrets are named in requests, never carried. Verified by its records and refusals. | v0.1.0-draft |
| The agent builder portable | role-agent-builder | Turns a description of a needed agent into an agent plugin package: skills, the systems it needs, and the obligations. It asks for what it must not invent, what the agent refuses and the records it must leave, and refuses to emit a package without them. Every package is a draft, because nobody has run it. The other end of the deployment manager. Verified by its refusals and its records. | v0.1.0-draft |
| The agent evaluator portable | role-agent-evaluator | Derives a conformance test from a package's own declarations and runs it against the deployed agent: each refusal must be declined, each escalation routed to a person, each required record left behind. Checks only the checkable and never grades quality. Fails closed; observes and never fixes. Signs a verdict tied to the exact package. Verified by whether its verdicts match a known truth. | v0.1.0-draft |
Roles are added when a job recurs often enough to deserve a contract. The registry's authority is its specification, kept with the site.
The interfaces
Six are published. The worker and the manager face each other, because an interface with only one side published is half a contract. The entryway runs before any relationship exists. The deployer, the builder, and the evaluator are the primary interfaces of the three operations roles.
| Interface | Name | What it covers | Status |
|---|---|---|---|
| The worker portable | interface-worker | An agent that can be given a piece of work by something that knows nothing about it. Seven exchanges: whether it is free, what a job would take, whether it will take it, how it is going, what came of it, what it is blocked on, and stop. It says what work costs it, never what the work is sold for. Defines no document. | v0.2.0-draft |
| The manager portable | interface-manager | What a worker can rely on from whatever is directing it. Terms already agreed above flow down with the job, raised blocks get answered or explicitly refused, cancellation reaches the worker, and what was committed on an owner's behalf is stated in full. Defines no document. | v0.2.0-draft |
| The entryway portable | interface-entryway | What a stranger may ask before anybody has agreed to anything. Four exchanges: what are you, will you let me talk to you, are you accepting new callers, and where do I stand. A request to be admitted carries no work, and what the agent says about itself on the way in is a description rather than an offer. Defines no document. | v0.1.0-draft |
| The deployer portable | interface-deployer | The exchanges for putting an agent package on a host: deploy this, what is deployed, how did it go, update it, and remove it. A deploy request names secrets and never carries them, and reports state what kind of check was run. The primary interface of the deployment manager role. Defines no document. | v0.1.0-draft |
| The builder portable | interface-builder | The exchanges for turning a description of a needed agent into a package: build this, what did you build, and revise it. A description missing its refusals or its records is refused with the missing part named, and every answer about a package says it is a draft. The primary interface of the agent builder role. Defines no document. | v0.1.0-draft |
| The evaluator portable | interface-evaluator | The exchanges for checking a deployed agent against its package: evaluate this, what is the test, and what did you find. The test is readable before it runs, and a verdict never grades quality. The primary interface of the agent evaluator role. Defines no document. | v0.1.0-draft |
The agent builder, the deployment manager, and the agent evaluator are the operations jobs published so far, and they form a loop: the builder turns a description into a package, the deployment manager stands that package up as a running agent, and the evaluator checks that what is running does the job the package describes. An agent that also operates a fleet on an owner's behalf, speaking to and through the agents it runs, is a further job the registry expects to publish. Nothing above waits on it.