R.7

Glossary

Each term below has one meaning across the manual, and the last column names the section that explains it.

The meanings come from the Agent Substrate source and documentation at v1.0.0 and from our runs. Terms in code font are literal names that you type or read in output.

TermMeaning in this manualExplained in
Access policyA list of bindings that grants roles on the API, for one atespace or for the whole install5.2
ActorOne isolated workload with an identity and a state that Substrate can suspend to a snapshot and resume on a fitting worker. While a node holds its last snapshot, it resumes on that node1.1
Actor JWTA signed token that states the identity of one actor, which the egress gateway can attach to an outbound request5.3
ACTOR_STATE_CRASHEDThe state of an actor whose sandbox, worker, or restore was lost. Only a revert or a delete leaves it.3.5
ActorTemplateThe record that describes the containers, the resource limits, and the snapshot fidelity of the actors made from it3.1
Agent (kagent)The pair of one AgentTemplate and one Harness, which kagent compiles into one ActorTemplate7.1
agentgatewayAn open-source proxy that Substrate can run as its dataplane in place of Envoy6.6
AgentTemplateThe kagent object that holds the model, the prompt, and the tools of an agent7.1
Asynchronous suspendA suspend that returns when the snapshot is on the node, before the upload to the bucket. The default.3.3
ate-api-serverThe Substrate API server. It serves both gRPC services and is the only component that reads and writes Postgres.1.2
ate-controllerThe component that turns each WorkerPool into worker pods and registers them as workers2.4
ate-idp-serverThe component that publishes the public keys for actor JWTs5.3
ate-setupThe installer program in the Substrate repository2.1
ateletThe Substrate agent on each node. It drives the workers of its node and moves snapshots to and from the bucket.2.4
atenet-egressThe egress gateway: the dataplane pod that every outbound connection of an actor passes6.2
atenet-routerThe router: the dataplane pod that receives each request for an actor and forwards it to the worker6.1
AtespaceA name that groups actors, templates, and tags, and that carries one access policy. It is a Substrate record and has no link to a Kubernetes namespace.3.6
Ballast actorOur test actor. It holds a set number of MiB of random bytes and reads one byte of each MiB on a request.3.3
BindingOne role with the identities that hold it, inside an access policy5.2
Bootstrap ownerA principal from the server flag --authz-bootstrap-owners that always holds the global owner role5.2
BucketThe object store location that holds durable snapshots. In our clusters it is ate-snapshots on rustfs.8.1
CrashedThe actor state after a sandbox or a worker is lost, or after a failed resume. Only a revert or a delete leaves it.3.5
Credential injectionThe egress gateway replaces a header of an outbound request with a secret that the actor never holds6.5
Credential providerThe service that returns that secret to the egress gateway6.5
DataplaneThe router and the egress gateway together, built on Envoy or on agentgateway6.6
Default denyAn actor with no matching egress rule reaches no host and resolves no name6.2
DNS relayThe resolver inside the sandbox network that answers only for names that the egress policy allows6.3
Durable snapshotA snapshot whose files are in the bucket, with the storage state completed3.4
EgressPolicyThe rules of one actor that name the hosts and ports it can reach and the headers that the gateway replaces6.2
EpochA number that a worker process gets when it starts. Actors from an older epoch of the same worker become crashed.the API reference
Files-only snapshotA snapshot at volumes fidelity. It keeps the durable directories, and the processes start again at a resume.3.4
First callThe first request to a new actor, which includes a resume from the golden snapshot3.1
Golden snapshotThe snapshot that Substrate takes of one started actor for each template, so that new actors resume from it3.1
Golden tagThe tag under which Substrate stores the golden snapshot of a template3.1
gVisorThe sandbox class that runs an actor under a user-space kernel. The API has no default class: each WorkerPool names exactly one. The pool of the counter demo names gVisor.4.2
HarnessThe runtime that executes an agent and decides when to suspend its actor. In kagent it is also the object that names the WorkerPool and the snapshot location.7.1
Ingress allowlistThe list of client identities that the router accepts5.1
InstallerThe program ate-setup, which installs and removes Agent Substrate from a checkout of the tag2.1
Interception CAThe certificate authority whose key signs the certificates that the egress gateway shows to an actor for an https rule6.4
kagentAn open-source agent framework for Kubernetes. Version 1.0.0 installs its own distribution of Substrate.7.1
kubectl ateThe command-line plugin for the Substrate API2.2
LeaseA row in Postgres that gives one workflow the right to change one object. The workflow renews it, and it expires 30 seconds after its last renewal.8.1
microVMThe sandbox class that runs an actor in a small virtual machine. It needs KVM on the node.4.2
Mock modelThe server in our kagent cluster that answers model calls with a fixed reply, so that model time is near zero7.1
Model gatewayA mode of agentgateway that routes requests to model providers and applies budgets and failover. It is separate from the Substrate dataplane.7.2
Node-local snapshotThe copy of a snapshot on the node disk. After an asynchronous suspend it is the only copy until the upload.3.4
Object storeThe service that holds the bucket: rustfs in our clusters, Google Cloud Storage or S3 in the documentation8.1
Parked requestA request that the router holds open while it retries the resume of the actor4.4
Parking budgetThe time that the router holds a request with no worker before it returns a 503. The default is 5 s.4.4
Placeholder headerThe header that an actor sends with a value that is not a secret, which asks the gateway for the swap6.5
PlacementThe choice of a worker for an actor that resumes4.3
PluginThe binary kubectl-ate, which kubectl runs for each command that starts with kubectl ate2.2
Preview featureA feature that is off unless the server flag --preview and the client header both allow itthe flags reference
PrincipalThe identity that ate-api-server derives from a credential, and the name that access policies grant roles to5.1
Proxykubectl ate proxy actor: a local listener that forwards TCP to one actor through the router2.3
Request parkingThe router holds a request and tries again while no worker has room4.4
ResumeRestore an actor from its latest snapshot on a worker. The router asks for it on every request.3.3
ResumeActorThe call that places a suspended actor on a worker and restores its newest snapshot3.3
RevertReturn an actor to its last durable snapshot and discard what came after it3.5
RevertActorThe call that discards the current run of an actor and returns it to suspended at its last completed durable snapshot3.5
Routing headerThe HTTP header ate-target-actor, with the value <atespace>/<actor>, which tells the router where a request goes6.1
SandboxThe isolated environment that a worker starts for one actor4.2
Sandbox classThe kind of sandbox: gvisor or microvm4.2
SandboxConfigThe Kubernetes object that names the runtime versions of one sandbox class and their files4.2
SessionIn kagent, one conversation. kagent maps each session to one actor.7.1
Shared identityThe ServiceAccount ate-client in ate-system, which kubectl ate uses when you give no token5.1
SnapshotThe saved state of an actor at one suspend3.4
Snapshot cacheA directory on the node that keeps downloaded snapshot files for later resumes8.1
Snapshot fidelityHow much a snapshot holds: volumes only, the root filesystem too, or process memory too3.4
SPIFFE IDThe identity in a client certificate, such as spiffe://cluster.local/ns/ate-system/sa/atenet-client5.1
Standing port-forwardOne kubectl port-forward that you keep open, so that parallel CLI calls do not each open their own7.1
SuspendWrite a snapshot of a running actor and release its worker3.3
SuspendActorThe call that checkpoints a running actor, stops its sandbox, and frees its place on the worker3.3
Synchronous suspendA suspend that returns after the snapshot is in the bucket3.3
TagA named copy of the snapshot of a suspended actor, from which new actors can start3.4, the API reference
TLS interceptionThe egress gateway ends the TLS connection of the actor and opens its own to the host, so that it can read the request6.4
TLS pass-throughThe egress gateway forwards the TLS connection unread, after it checks the server name6.4
Trust bundleThe file that holds the interception CA certificate, so that the actor can verify intercepted connections. A sandbox has it only when its template mounts a systemInfo volume with a trustBundle source. The code in the actor must also be set to trust it.6.4
TurnIn kagent, one user message and the reply to it. kagent resumes the actor before the turn and suspends it after.7.1
Wakeup probeAn HTTP check in a template that a resume waits for before the actor counts as running3.1
Warm callA request to an actor that is already running3.3
WorkerOne pod of a WorkerPool that registered with the API. It hosts actors up to its capacity.4.1
Worker selectorThe labels in a template or an actor that choose which pools can host it4.3
WorkerPoolThe Kubernetes object that asks for a number of worker pods with one image and one resource size4.1

Agent Substrate 1.0.0 · b34fbee · 2026-11-05 · Edition 2026.11