SRE Investigator Overview

Federal Frontier SRE — problem to agent on OpenCode Runner or Claude Code runner; Remuda-shaped Jobs; estate coverage for the platform you run.

Federal Frontier provides OpenCode Runner or Claude Code runners on the shared Investigator harness. Specialization is a Remuda slice + playbook + scout brief — not a new binary per domain, and not an agent farm.

Primary path

Operator or alert names a problem on the Federal Frontier Platform → sre-dispatch starts a Job on OpenCode Runner or Claude Code runner → Remuda tools → remediate under Warrant/FAS. Same Job shape for an English problem brief (Outpost / API / ticket) or an alert payload.

Specialist routes accelerate known classes on that path. You bring the problem; we dispatch the agent.

What Federal Frontier covers

Federal Frontier covers the estate you run — VitroAI compute, EKS and RKE2 Kubernetes, Outrider VMware landing, Ceph storage, network, and platform control — with task-configured SRE agents on one governable harness.

See Coverage for the estate coverage map.

In this section

• Coverage — estate you run
• SME Catalog — automatic routing for known classes (+ YAML export)
• Harness Shaping — operator enablement
• Local-First Inference — Gemma hot path / Opus cold path
• Federal Frontier SRE architecture — architecture positioning
• ADR-033 — shared harness decision
• What’s New — 2026-09-21 — primary path + dual runners

Related platform pages: Autonomous SRE Agent, Agent Harness (ADR-005), Frontier Warrant, Sovereign Inference.

Remuda

Agents reach tools through Remuda — Federal Frontier’s MCP registry and router. Specialist playbooks select Remuda namespace slices on the shared harness (OpenCode Runner or Claude Code runner); they do not multiply runners.