Key concepts

Ten concepts the rest of the docs are written in. Each in one line, with where it lives in the panel.

Organization and region

An organization is your team of people and agents: one sign-in, one set of data, one approval queue. The region is chosen when the organization is created and never changes: US (worldwide) or RU (Russia and Asia). Data never leaves the region.

Workspace

What people sign into: Chat, Tasks, Projects, Approvals, Workforce, Builds. More in Workspace.

Workforce

The section where digital employees live: roles, teams, scenarios, budgets, nodes. More in Workforce.

Role and risk class

A role is a document: what the agent does, what is forbidden, which channels it may use. The risk class: r0 reads public sources only; r1 works with data and never writes outside; r2 writes to people and every message is approved by a human. Roles are versioned; agents get only published versions.

Team

A set of roles and scenarios that together cover a piece of work. Every organization already has seven teams from 47 roles: the catalog (in Russian).

Scenario

The graph of steps an agent follows for a task: actions, waiting for input, compensations on failure, conversation phases. The hpl/v1 format: reference (in Russian).

Task

One run of a scenario. The agent pulls the task itself, writes checkpoints along the way, and the task keeps a run transcript: what it was started with, what the model was asked, what it answered.

Approval

A card in the queue: an agent wants to do something outbound or expensive, a human decides. A customer message from an r2 role, a budget raise request, hiring a new agent, a production deploy.

Budget

The task budget is enforced by the server. The monthly agent budget in dollars is set for an agent in Workforce, on its card in Nodes: 80 % is a warning, 100 % is a pause. Model tokens are paid to the provider on your own keys.

Agents, nodes and keys

The agent from the HolyAgent app is registered by signing in with HolyCode ID and is listed under Agents; it needs no key. A node is a machine registered in Workforce: an agent that takes scenario tasks, or a build runner. Such an agent is connected with a one-time enrollment key from the Nodes card; after the first run a node keeps a permanent key. A runner is HolyAgent in build mode, added from Builds → Add → Runner with its own one-time key valid for 24 hours. An access key (PAT) is for scripts and external systems with read or read, write rights. A company package is roles, scenarios and skills in one file.

Next

Access and first sign-in, then the five-minute path. The full glossary is at the end of the section.