Reason. Select. Propose.
The kernel creates intent and structured requests. It does not hold write authority.
Prometheus AGS // Runtime Infrastructure
One trusted boundary for agent execution.
UAR coordinates models, tools, skills, knowledge, memory, policy, and streaming protocols without giving the agent kernel authority to mutate the world.
Execution Contract
Capability inversion is the safety boundary.
Authorize. Execute. Record.
The host enforces tenancy, credentials, governance, persistence, and observable effects.
Four-Step Surface Ladder
From intent to evidence, every layer stays inspectable.
Canvas
Runtime intent and user context
Chrome
Navigation, tenancy, and policy
Surface
Turns, steps, tools, and retrieval
Raised
Evidence, approvals, and results
Open Protocols First
One runtime, multiple typed entrances.
Protocols describe how work crosses the boundary. They do not bypass policy, identity, or lifecycle control.
- OpenAI-compatible
- Anthropic-compatible
- MCP
- A2A
- AG-UI
- A2UI
Choose Your Path
Move from theory to a working boundary.
01 // Understand
Start with the runtime boundary
Learn why agents propose work while trusted hosts own side effects, policy, persistence, and credentials.
Open guide →02 // ConfigureChoose a supported profile
Configure server-full, minimal, or embedded-mobile without transferring claims across profiles.
Open guide →03 // BuildCreate an agent workflow
Connect models, tools, skills, knowledge, memory, and approvals through one runtime contract.
Open guide →04 // IntegrateUse typed protocol surfaces
Enter through HTTP, MCP, A2A, AG-UI, A2UI, or a supported SDK while UAR keeps execution coherent.
Open guide →Evidence Has Boundaries
Profiles are separate contracts.
server-full, minimal, and embedded-mobile differ in capability and evidence. A result for one never transfers silently to another.
Compare configuration boundaries →