SRE Coverage — Estate You Run

Federal Frontier SRE covers VitroAI, EKS and RKE2, Outrider, Ceph, network, and platform control with task-configured agents on one harness; Remuda is the tool plane.

Federal Frontier covers the estate you run — with task-configured SRE agents on one governable harness. Runners are OpenCode Runner or Claude Code runner. Remuda is the tool plane (namespace slices the Job selects) — not a separate binary per domain.

You bring the problem; sre-dispatch starts the Job; Remuda tools and Warrant/FAS govern remediation. Specialist routes accelerate known classes on that same path.

Estate coverage

Domain What agents work against
VitroAI Compute / HCI landing for the Federal Frontier Platform
EKS Amazon EKS Kubernetes (clusters, workloads, cluster lifecycle surfaces)
RKE2 RKE2 Kubernetes (clusters, workloads, cluster lifecycle surfaces)
Outrider VMware landing / migration Layer 1 estate
Ceph Storage plane (volumes, capacity, PV / PVC-class pressure)
Network Fabric and network control surfaces on the platform
Platform control Dispatch, Outpost/API/ticket intake, Warrant/FAS, Remuda registration

Coverage is the estate you operate on Federal Frontier — not a per-domain agent product line.

How coverage is delivered

  1. Intake — English problem brief (Outpost / API / ticket) or alert payload.
  2. Dispatch — sre-dispatch starts a Job on OpenCode Runner or Claude Code runner.
  3. Tools — Job selects a Remuda namespace slice (specialist or wide).
  4. Remediate — under Warrant / FAS.

Auto-route specialists (generic / wide Remuda, plus the four Kubernetes classes) are accelerators when the classifier recognizes a known class. Unknown or estate-wide problems still take the primary path on the shared harness.

Eupraxia Labs · Federal Frontier · Platform docs