System Topology
This page describes the system as layered runtime responsibilities.
Topology In One View
This abstract model is the canonical topology.
Layer Responsibilities
| Layer | Purpose |
|---|---|
| Client surfaces | Accept user intent, display progress, and return outcomes. |
| Runtime core | Frames intent, coordinates planning, and enforces policy. |
| Capability layer | Selects the relevant skills, tools, and context for a turn. |
| Execution layer | Performs approved actions within explicit boundaries. |
| Evidence and state | Records intent, plan, actions, results, and confidence signals. |
Topology Principles
- Layers communicate through defined contracts.
- Policy is evaluated before execution begins.
- Capability selection must be explainable and bounded.
- Execution results must flow into durable evidence.
- State informs future turns without bypassing guardrails.
Why This Topology Matters
The layered model keeps the system understandable under change. It provides clear authority, controlled execution, and evidence-backed outcomes.