AI agent operations glossary
The words teams use when work runs through AI agents, defined plainly. Each entry says what the term means in general and what it means in OrgX.
- Agent orchestration
- Coordinating several AI agents on one body of work: who does what, in what order, with which tools, and who reviews the result. In OrgX, an orchestrator breaks an initiative into workstreams and hands tasks to domain agents.
- Artifact
- A durable output of work, such as a document, pull request, page, dataset, or design. OrgX stores artifacts with their version, owner, producing agent, and evaluation result so a reviewer can inspect what was made.
- Decision
- A choice that needs a named person to approve, reject, or pick an option before work continues. OrgX lifts decisions out of chat into a queue with the options, evidence, and consequences side by side.Prove delegated work got done
- Execution receipt
- A record of what an agent run did: the route it took, the tools it called, what it cost, and what it produced. Receipts let a reviewer verify work without replaying the conversation.
- Human-in-the-loop approval
- A checkpoint where an agent pauses and a person approves before an action runs. In OrgX, agents can be configured to require approval for guarded actions, and the request lands in the Decisions queue.
- Initiative
- A company goal with a defined outcome, broken into workstreams, milestones, and tasks. In OrgX it is the unit that ties agent work, decisions, and artifacts back to what the business is trying to achieve.
- MCP tool profile
- A named subset of a server’s tools chosen for one kind of work. OrgX exposes profiles such as chatgpt, memory, planner, and executor through the ?profile= query parameter.
- Model Context Protocol (MCP)
- An open protocol that lets AI clients such as Claude, ChatGPT, Cursor, and VS Code call tools and read context from external servers through one standard interface.OrgX MCP config for every client
- Quality gate
- A check an artifact must pass before it counts as done: measured checks, independent review, references, and a ship rule. In OrgX these are published in Quality Studio and stay attached to every verdict they governed.
- Remote MCP server
- An MCP server hosted on the web rather than run locally, reached over streamable HTTP and usually secured with OAuth. OrgX runs one at https://mcp.useorgx.com/mcp.OrgX MCP config for every client
- Spend boundary
- A hard limit on what agents may spend per day, week, or month. When routes compete, OrgX applies the tightest eligible cap.
- Work ledger
- A time series of agent activity (sessions, tool calls, runs, receipts, decisions, and artifacts) broken down by initiative and client, so a team can see where agent effort went.
- Workstream
- A parallel track of work inside an initiative, usually owned by one function or agent, with its own milestones and tasks.