Skip to main content

Glossary

Subbasis​

Definition: A governed agentic execution platform.
Why it matters: It combines AI reasoning with runtime governance for real operations.
Related: Runtime Core, Workflow, Governed Execution.

Runtime Core​

Definition: Deterministic distributed runtime for execution, coordination, and persistence.
Why it matters: It enforces boundaries around connector actions and approvals.
Related: Workflow Execution, Evidence, Policy.

Governed Execution​

Definition: Execution controlled by permissions, policy checks, approvals, and evidence.
Why it matters: Prevents uncontrolled side effects in business operations.
Related: Approval Gate, Policy, Evidence.

Governed Execution Credit​

Definition: Unit measuring meaningful governed runtime activity.
Why it matters: Links usage to operational execution, not only model tokens.
Related: Workflow Execution, Agent Task, Limits.

Workflow​

Definition: Durable business execution flow that can wait, resume, retry, and escalate with context.
Why it matters: Supports real operations over long timelines.
Related: Workflow Execution, Approval Gate, Connector / ACC Adapter.

Workflow Execution​

Definition: A concrete run instance of a workflow definition.
Why it matters: Separates design-time process from runtime outcome.
Related: Workflow, Evidence, Trace.

Agent​

Definition: Governed execution participant with role, skills, limits, permissions, and context scope.
Why it matters: Makes responsibilities explicit in multi-agent operations.
Related: Skill Pack, Agent Blueprint, Policy.

Skill Pack​

Definition: Reusable operational skill instructions for an agent role.
Why it matters: Improves consistency across similar operations.
Related: Agent, Agent Blueprint, Marketplace Asset.

Agent Blueprint​

Definition: Reusable configuration pattern for an agent role and runtime posture.
Why it matters: Speeds setup of consistent governed agents.
Related: Agent, Skill Pack, Governance Pack.

ACC​

Definition: Agent Connector Contract, an open contract proposal for governed connector execution.
Why it matters: Adds policy/evidence boundaries around tool use.
Related: MCP, Connector / ACC Adapter, Policy.

MCP​

Definition: Protocol layer used to connect tools and context endpoints.
Why it matters: Standardizes tool connectivity, but not governance by itself.
Related: ACC, Connector / ACC Adapter.

ARIN​

Definition: Local execution environment for persistent, sensitive, or environment-dependent workflows near customer systems.
Why it matters: Supports local execution patterns where proximity matters.
Related: Federation, Context Intelligence, Evidence.

Context Intelligence​

Definition: Operational state attached to workflow progression, not just memory.
Why it matters: Preserves continuity across waits, resumes, approvals, and retries.
Related: Workflow Execution, Evidence, Local LLM.

Evidence​

Definition: Execution-grade records of actions, decisions, approvals, and outcomes.
Why it matters: Enables reviewable execution history and audit-ready posture.
Related: Trace, Policy, Approval Gate.

Marketplace Asset​

Definition: Reusable governed execution asset distributed through marketplace patterns.
Why it matters: Helps teams install repeatable operations quickly.
Related: Execution Template, Skill Pack, Connector / ACC Adapter.

Execution Template​

Definition: Reusable workflow structure for a specific operation pattern.
Why it matters: Accelerates implementation while keeping governance defaults.
Related: Marketplace Asset, Workflow, Governance Pack.

Connector / ACC Adapter​

Definition: Integration path that executes external actions under governed contract boundaries.
Why it matters: Connects systems without bypassing policy and approvals.
Related: ACC, MCP, Evidence.

Local LLM​

Definition: Model resource executed in local or controlled environments where supported.
Why it matters: Supports privacy and local continuity requirements.
Related: Model Resource, BYOD Provider, ARIN.

BYOD Provider​

Definition: Bring-your-own-provider model path using external credentials/accounts.
Why it matters: Gives teams provider flexibility under governance constraints.
Related: Model Resource, Governed Model Orchestration.

Model Resource​

Definition: Governed model endpoint/category available to workflow tasks.
Why it matters: Allows per-task model decisions with policy and cost controls.
Related: Local LLM, BYOD Provider, Governed Model Orchestration.

Governed Model Orchestration​

Definition: Runtime-controlled allocation of model resources across workflow tasks.
Why it matters: Goes beyond simple routing by enforcing policy, privacy, and fallback logic.
Related: Model Resource, Runtime Core, Limits.

Federation​

Definition: Architecture path for controlled multi-node or multi-organization execution.
Why it matters: Extends governed workflows across trust boundaries.
Related: ARIN, Evidence, Policy.

Organizational Execution Space​

Definition: Operational context where workflows, agents, systems, context, and evidence are governed together.
Why it matters: Defines boundaries for permissions, policy, and accountability.
Related: Governance, Policy, Workflow Execution.

Policy​

Definition: Declarative execution constraints for what can run, when, and under which conditions.
Why it matters: Converts governance intent into runtime-enforced boundaries.
Related: Approval Gate, Governed Execution, ACC.

Approval Gate​

Definition: Human or delegated approval checkpoint before sensitive actions proceed.
Why it matters: Enables human-in-the-loop control in critical operations.
Related: Policy, Workflow, Evidence.

Trace​

Definition: Structured execution timeline of workflow steps, agent tasks, and runtime events.
Why it matters: Supports debugging, review, and observability.
Related: Evidence, Observability, Workflow Execution.

Evaluation Workflow​

Definition: Workflow pattern used to assess operation quality, policy adherence, or outcome consistency.
Why it matters: Helps teams improve governed operations over time.
Related: Trace, Evidence, Observability.