Glossary

Common Terms

Control Plane: the server-side capability layer that owns authorization, approval, task orchestration, audit, and delivery control.
Bootstrap: the install and initialization entry phase, not the final formal runtime.
Formal Runtime: the long-running target where services operate as image-based workloads inside K3s.
AppSpec: the unified application delivery input model.
Step-Up: a stronger identity confirmation requirement before high-risk actions.

Session: the current runtime/session identity used in Agent Platform control-plane and probe contracts, referenced by agentsession; not an HTTP session and not a browser login session.
Task: the durable model that records long-running execution state, progress, and result; not an approval record and not a scheduler trigger definition.
Approval: the model that records decision state for gated actions; not task progress and not authorization itself.
Gateway: the sole control-plane boundary in Agent Platform, owning command source, capability registration, routing intent, and global policy authority; not a probe-side worker.
Probe: the host-side runtime worker that consumes authorized commands, manages local channels/adapters, and reports events back to Gateway; not the control plane and not the owner of global policy.
Channel: a runtime communication binding managed by Probe, such as dialog or ssh_remote; not a session by itself.
Adapter: a runtime integration boundary registered on Probe for tool execution or channel transport; not a scheduler and not a policy engine.
Command Envelope: the Gateway-to-Probe control message wrapper carrying validated command metadata and payload; not an event.
Event Envelope: the Probe-to-Gateway runtime signal wrapper carrying lifecycle, channel, recovery, and capability metadata; not command intent and not a transcript-persistence substitute.