Glossary
A
Admin:
a special Authorization allowing a user to use additional functionality and special views. See more detailed information here.
Agent:
An is the collective term for any users/LLMs that can interact with tasks. Human agents being Users, while LLM users are called AI Agents.
Authority:
A category that users can be assigned to, giving them special permissions and access to special tasks. E.g. Admin or Budget Manager.
B
Boundary: A defined separation that limits responsibility, access, or control between systems or workspaces.
C
Coordination: The alignment of multiple actors or systems to complete work in the correct order.
D
Dependency: A prerequisite that must be satisfied before an execution step can begin.
Deploy:
The act of creating/updating a build to the current list of usable processes/datastores. When a process build is executable from the Processes tab it is “deployed”, and even if other versions with changes exist in the past, only the process in current use listed on the Processes tab is the “deployed” build/process.
Deploying also refer to Creating and Updating.
Datastore:
A collection of data stored as worksheet similar to Excel and Google sheets. The datastores can be integrated into processes. Datastores can be imported and exported as CSV files.
E
Execution Step: The smallest executable unit of work within a process, performed by an agent.
F
Fulfillment: The completion of a requested outcome through one or more execution steps.
G
Governance: The policies and controls that define who may perform which actions and under what conditions.
Group:
A group is a category to contain a group of users that should all receive the same tasks.
E.g. The group ‘Researchers’ would contain Users that are researchers, so that any tasks directed to the group researchers is correctly sent to those specific Users.
H
Handoff: A controlled transfer of responsibility from one agent or system to another.
I
Instance Naming Template:
The process property allowing dynamic instance naming based on context information from the instance itself. Defines what is shown as the instance name on the Process Instance View. Typing ${ shows a list of available symbols in a drop down. Can be combined with normal text. Default Value is ${instanceID}
Inter-Tenant Protocol (ITP): A protocol that defines how processes interact across multiple workspaces while preserving isolation and control.
J
Job: A scheduled or triggered unit of work that may map to one or more execution steps.
K
Key: A unique identifier used to reference an entity across systems or workspaces.
L
Lifecycle: The sequence of states an entity goes through from creation to completion (or termination).
M
Message: A structured piece of information exchanged to trigger actions or report state changes.
N
Note:
While building a process, it is sometime helpful to leave a note to yourself or to others working on the process. They can be added using the Right-Click Menu in the Workspace. Notes can be dragged and dropped. They automatically resize. Notes are only visible in the Builder.
O
Orchestration: The coordination of execution steps across agents to achieve a defined outcome.
Organisation:
A collective of Users and Groups.
P
Process:
A repeatable sequence of steps and rules that transforms inputs into outcomes.
Process Tags:
One or more tags can be set on for a process in the builder. The tags are used to define in which groups a process is shown in the Process Viewer
Process Viewer:
Shows all available Processes for a given user. Reachable through the main navigation. Further documentation here.
Q
Queue: A mechanism that holds work items until an agent can pick them up, often used to manage load and ordering.
R
Responsibility: Clear ownership over a step, outcome, or decision, assigned to an agent, role, or workspace.
S
State: The current persisted condition of a process or entity used to determine what can happen next.
T
Template:
Any text containing a direct reference to a symbol in the process context. Further documentation here.
Tenant: A distinct organizational boundary with its own data, rules, and control, often mapped to a workspace.
U
User:
An account through which a person can interact with metamorphOS. The User is what allows for a history of who has done what, as well as allowing tasks to go to specific people.
Many things are assigned to a User, such as the name, authority and any groups they belong to.
V
Validation: A check that ensures inputs or outcomes satisfy required rules before a process can proceed.
Version:
the published version of the process which was current when a process instance was created, or the version if a process instance was migrated to. Begins with version 1 when a new process is created. It is automatically incremented when a process is updated using the Update Process core process.
W
Workspace: An isolated operational context in which processes, agents, data, and execution rules are defined and managed.
X
XTP: A placeholder term for a cross-tenant interaction protocol variant; replace with your canonical definition.
Y
Yield: A controlled pause in execution where work waits for an external signal, input, or condition.
Z
Zero-Trust: A security approach that assumes no implicit trust and requires explicit verification for every access request.