Glossary
Agent
What runs on a vault’s data. Three kinds: a workflow, an LLM agent, and a code agent. All three publish, deploy, and connect the same way, and a workflow can use either of the other two as a step. See Agents and workflows.
Agent id
<agentServicePubkey>:<alias>: the Agent Service’s public key, then the agent’s
name. The platform derives the publisher from the prefix.
Agent Service
The developer’s account on Manykind: it holds your workflows, LLM agents, and code agents, plus the cubby schemas, widgets, datasets, and members that belong to them. Created in ROC. See Your Agent Service.
Agreement
The signed record of a vault owner’s consent to connect an Agent Service’s agent to named scopes of their vault. Held in the agreement registry; revoking it removes the authority. See Connections and consent.
Bundle
An agent’s built code, stored content-addressed in the Agent Service’s bucket. A connection pins the bundle the owner consented to run.
Code agent
TypeScript engagement classes that react to events, written with
@cef-ai/agent-sdk. See Write an agent.
Connection
- Agent connection: the vault’s record that an agent may run on named
scopes, with its settings, pinned bundle, and status (
provisioning,active,revoking,revoked). - Connector connection: one configured account of a connector in a vault.
Connector
A kind of outside system a vault supports: Slack, Email (SMTP), Telegram, or an MCP server. Workflows use a vault’s connections as triggers and actions. See Connectors.
Context
The field on an event that names its stream. Events sharing a context form one stream and one Job.
Cubby
A SQLite database an Agent Service declares. Every agent of the service shares it by alias, one per vault. See Cubbies.
Dataset, case, experiment, result
Evaluation terms. A dataset is a workflow’s set of cases; a case is one input and the expected result; an experiment runs a dataset version on a workflow version; a result is what a workflow declares as its output. See Evaluations.
Engagement
The building block of a code agent: a class marked @Engagement({ id, goal })
whose @OnEvent methods handle event types. One engagement is selected per Job
and pinned.
Event
One typed message published into a vault scope, with type, context, and
payload. The only way work enters the platform. See
Runs and events.
Execution token
The short-lived credential a running agent or workflow uses to reach the vault, minted per task and bound to the connection. Your code never handles it directly.
Item
One element of a list a workflow processes with split and aggregate steps. See Items.
Job
A long-lived run, keyed by vault, agent, scope, and context. The record of a workflow run is a Job. Each event in it is a Task.
LLM agent
An agent defined by instructions, a model, tools, connections, and scopes,
created in ROC and hosted on the Agent Bridge; or an A2A agent you run
elsewhere, registered from its Agent Card (cef push --kind external). See
LLM agents.
Manifest
The JSON document cef build produces for an agent: identity, bundle, models,
cubbies, settings schema, event schemas, widgets. The vault reads it at connect
time.
Manykind
The platform these docs describe: Agent Services on the developer side, vaults
on the customer side, and the connection between them. Its packages are
published under @cef-ai/*, and its CLI is cef. See
How it fits together.
Member
Someone other than the owner who may use a vault, with a role (admin or
member), per-scope levels (Write, Read, Audit), and an optional privacy
ceiling. See Members.
Memory Bank
The vault’s durable graph of records and relations that its agents and workflows filed, each with a scope and a privacy class. See Memory Bank.
Model alias
The name an agent or workflow calls a model by (ctx.models.<alias>), bound in
config to a model in the platform’s catalogue. See Models.
Privacy class
How sensitive a Memory Bank record or relation is: public, internal,
private, or restricted. Required on every write.
ROC
The Manykind web console: where you create Agent Services, build and run workflows, and browse connectors, models, members, and the Memory Bank. See How it fits together.
Run
One execution of a workflow or agent, from a trigger event to its result. Its record is a Job.
Scope
A named partition of a vault. Events, objects, and grants are per scope. Shown as Domains in ROC. See Vaults.
Step
One unit of a workflow’s graph: a trigger, a model call, an agent, a person, a cubby read, a connector action, and so on. See Steps.
Task
One event’s worth of work inside a Job, with its own status, attempts, and logs.
Trigger
The step that starts a workflow run: an event, a schedule, a webhook, or a connector message. See Triggers.
Vault
The customer side: a person’s or an organization’s own store, owned by a wallet. Holds scopes, events, objects, the Memory Bank, connectors, agent connections, and members. See Vaults.
Wallet
The cryptographic identity that owns a vault and signs agreements and grants.
Widget
A browser screen an Agent Service publishes. It acts as the signed-in person and reads the service’s cubbies and the vault’s Memory Bank. See Widgets.
Workflow
An agent whose behaviour is a typed graph of steps, built in the ROC Workflow
Builder or in code with defineWorkflow. See
Workflows overview.