Terminology
The concepts that carry most of the domain, worth keeping straight:
| Term | What it is |
|---|---|
| Workflow | A reusable, pre-designed unit of work: an agent skill plus the task templates generated for it. |
| Design session | The chat in which a workflow's task templates are produced and refined. Exactly one per workflow, and it exists before any run does. |
| Workflow execution | One run of a workflow: the workflow and skill metadata snapshotted at run time, and the parent of the run's WorkflowTasks, Approvals, and message metadata. |
| Workflow session | The chat that one workflow execution happens in — the run-time counterpart of a design session. |
| Branch session | A session forked from a workflow session when the run's task graph branches, so the branch is worked alongside the rest of the run. It finishes with a summary once its tasks are done. |
| Tenant | The top-level organizational boundary: nearly every record belongs to exactly one, and no request crosses from one into another. |
| User group | A named bundle of users within a tenant, carrying a set of roles that every member inherits. |
| Tag | A tenant-wide label for classifying secrets, MCP servers, agent skills, knowledge bases, workflows, tool mocks, and user groups — one vocabulary shared by all seven. A tag flagged Access control also restricts the records it labels to members of groups carrying it. |
| Agent Skill | A SKILL.md procedure in a Git repository, versioned like code; a workflow is generated from one, and a run executes its published revision. |
| Knowledge base | A wiki the LLM writes from registered web pages and documents, one page per topic. A workflow linked to it has its design and execution agents look things up there. |
| MCP server | A registered Model Context Protocol server whose tools the agent can bind to a workflow's tasks. |
| Secret | A named bundle of key/value credential entries, referenced elsewhere as name/key and resolved lazily at use time. |
| Tool certificate | The short-lived X.509 certificate a task must present on every MCP tool call. It freezes the task's tool set at the moment it is issued — when an approval is granted, or when a task nobody was asked to approve starts — and names whose authority it carries. |