The agents at a glance
Observer Agent
Eyes on every connected environment. Discovers topology, collects signals, keeps the graph current.
Memory Agent
Stores incidents, resolutions, and operator context. Surfaces prior art when relevant.
RCA Pipeline Agent
Builds evidence-linked causal chains from raw signals. Produces RCA reports.
SRI Agent
The conversational surface. Answers questions, runs skills, drafts actions.
Remediation Agent
Applies approved fixes inside their scoped blast radius. Watches for the stabilisation window.
Guardian Agent
Enforces policy on everything that could change state. Requires approvals where it matters.
Who does what in the OPEL loop
The mesh maps cleanly onto the four phases of the OPEL loop.| Phase | Primary agent | Supporting agents |
|---|---|---|
| Observe | Observer Agent | Memory Agent (surfaces relevant prior incidents) |
| Plan | RCA Pipeline Agent | Memory Agent, SRI Agent |
| Execute | SRI Agent (draft) and Remediation Agent (apply) | Guardian Agent (validate) |
| Learn | Memory Agent | Observer Agent (continuing verification) |
How the agents communicate
Typed events on a shared bus
Agents publish and subscribe to events: “anomaly detected”, “RCA ready”, “action proposed”, “verification complete”. Every event has a schema and a source.
The Knowledge Graph as shared state
Durable state lives in the graph, not in individual agent memory. Any agent that needs a resource, a signal, or a relationship reads it from the graph. Any update is applied there and broadcast.
Guardian as the gate
Anything that mutates your environment passes through Guardian policy. Policies are per-environment and versioned. Approvals are auditable.
Why specialisation beats a single generalist
Each agent has a narrow surface
Each agent has a narrow surface
A narrow surface means better prompts, smaller tool sets, cleaner evaluations. The Observer has one job. So does Guardian. The combined system is far more predictable than a single general-purpose agent with dozens of tools.
Auditing is clean
Auditing is clean
Every action has exactly one agent accountable for it. When something goes wrong, you can trace which agent produced which output and why.
Upgrades are independent
Upgrades are independent
The Observer upgrades on its own cadence. The SRI Agent upgrades on another. You never rebuild the entire stack to improve one phase of the loop.
Policies can be tight without being brittle
Policies can be tight without being brittle
Guardian can enforce strict limits on the Remediation Agent without constraining how the RCA Pipeline thinks. Different agents, different policy surfaces.
Where each agent runs
Observer Agent
Runs in your environment (cluster, cloud VM, or Linux host). Lightweight, read-only.
Every other agent
Runs in RubixKube Cloud. You never install, upgrade, or patch them.
Common questions
Can I add my own agents to the mesh?
Can I add my own agents to the mesh?
Custom agents are on the roadmap. In the meantime, custom skills let you extend the SRI Agent with your own runbooks, and custom integrations let you add tools any agent can use.
How does the mesh scale with more environments?
How does the mesh scale with more environments?
Agents are stateless relative to the graph, so adding environments scales linearly. The Observer fans out per environment. The Cloud-side agents work against the shared graph and spread load across investigation contexts.
What if one agent fails?
What if one agent fails?
The bus is fault-tolerant. If an agent is unreachable, events queue and retry. The Guardian never permits an action that relies on a missing agent’s output.
Do all agents see the same data?
Do all agents see the same data?
They see the same graph, but each agent has a scoped view of what matters to its job. The Observer does not need to read RCA reports. The Memory Agent does not need to stream raw metrics. This scoping keeps the system fast and the permissions sensible.
Related concepts
The OPEL Loop
The rhythm every agent in the mesh follows.
Safety and Guardrails
The policy layer that bounds what the mesh can do.