Promenaut01
Per-agent control plane
Each agent has one control surface covering identity and entitlement, contract and intent, model and behaviour, capabilities, boundary, lifecycle and versions, control and containment, and assurance and cost.
Layer 4 · The platform
Agents
What an agent is and can do: kinds and roles, capabilities, models and channels, prompts, versions, the registry and the control plane.
What it is not. Not a prompt. An agent is a versioned, published record with a declared boundary, a model route and a control surface, and it is checked against what it declares.
01Three to know
What it does.
02
Versioned, diffable agent configuration
An agent configuration is a versioned object with its own lifecycle: versions can be listed, compared against each other, and published deliberately rather than taking effect on save.
03
Per-agent model routing with fallback
Each agent is configured in the model registry with a primary model and a fallback, which can be from another provider.
02What it covers
The parts of Agents.
Kinds and roles
The kinds of agent, the roles and intent each carries, and running one on its own.
Models and routing
Which models an agent calls, fallback between providers, retries, time limits and prompt caching.
Output checks and repair
Making what a model returns parseable and checking its quality before it is used.
Guardrails and model limits
Guarded model traffic, and keeping every call inside the limits of the model and the guardrail.
Documents and media
Reading uploaded documents, images and speech, splitting large ones safely, and producing reports.
Registry and versions
Agents as versioned records, and the shared register of what they can do.
Fleet and control plane
Seeing and managing the whole set of agents: readiness, lifecycle decisions and each agent's controls.
03Questions it answers
Who asks about this layer.
See it on a workflow you own.
Bring a real process. We'll show what your first agentic workflow looks like on the platform.
