Skip to content

Concepts ​

The normative terminology of the Runne runtime. Each term has a definition and — where the source specifies it — an explicit "it is not".

Execution model ​

TermDefinition
SessionThe context of a user interacting with the runtime. Stores message history and references to TaskRuns. A Session is not the unit of execution and does not own execution.
TaskRunThe independent unit of execution of an AI coding workflow — a unique ID, a lifecycle, and a state machine, kept separate from the Session.
AttemptOne execution attempt of a TaskRun. Each Attempt has a unique ID and a full audit trail; a TaskRun can have several Attempts. Retry happens inside one Attempt, not across Attempts.
StepOne logical step inside an Attempt — a model call, a tool call, a verification, etc.
TurnOne agent↔model interaction inside a Step (prompt + response).
AgentThe logical entity executing a TaskRun, configured with a model, system prompt, tools, skills, and policies.
Primary Agent / SubagentThe primary agent is directly tied to the TaskRun; a subagent is created by it for a subtask and receives a delegated TaskRun.
Agent LoopThe main execution loop — model call → tool call → observation → … → acceptance gate.

Durable state and recovery ​

TermDefinition
Durable EventAn event written to persistent storage before the associated action runs — not an in-memory log line.
Event LogAppend-only source of truth for TaskRun state.
CheckpointSaved TaskRun state sufficient to continue execution (resume).
ResumeContinuing a TaskRun from the last checkpoint after a controlled stop or crash.
RetryRe-running an operation (model call, tool call) inside an Attempt after an error — distinct from resume.
RecoveryRestoring a TaskRun after a runtime crash — load the last checkpoint, replay durable events, reconcile uncertain side effects.
Audit TrailThe complete chronology of significant events, sufficient to reconstruct a TaskRun's execution.

Verification evidence ​

TermDefinition
VerificationThe lifecycle stage where the runtime checks the acceptance criteria.
Acceptance CriterionOne checkable condition of success.
Acceptance GateThe set of acceptance criteria that must pass for a TaskRun to reach completed.

Capability grants and approvals ​

TermDefinition
CapabilityA named ability granted to an agent (fs:read, fs:write, process:exec, network:outbound, …).
Capability GrantThe act of granting a specific capability with a scope — not a global permission.
Permission RuleThe rule deciding when a grant is enough and when an approval is required.
ApprovalThe user's explicit permission for an operation, with a scope, grantee, and TTL. An approval is not a grant.
SandboxAn isolated environment constraining the agent's filesystem, process, and network capabilities.
SecretConfidential material (API key, token, password) resolved from an external store, never held by the runtime itself.

Budgets ​

TermDefinition
BudgetA limit on TaskRun resource consumption — time, cost, tokens, tool calls, retries, subagents, processes, network, storage. Budgets are enforceable, not advisory.
Budget LedgerThe tracked consumption of each active budget.

Control and execution ​

TermDefinition
Control PlaneThe part of the runtime managing TaskRuns — creation, configuration, monitoring.
Execution PlaneThe part that actually executes TaskRuns — agent loop, tool calls, model calls.

These definitions are normative in the runtime repository (docs/00-foundation/TERMINOLOGY.md). See the repository for the full glossary and per-term source status.