Federal Frontier SME Catalog

Specialist routes for automatic routing of known problem classes on the primary problem→agent path (OpenCode Runner or Claude Code runner) — Remuda slice, first tools, playbook/scout brief.

Federal Frontier’s primary path is problem → agent: an operator or alert names a problem, sre-dispatch starts a Job on OpenCode Runner or Claude Code runner, Remuda tools run, remediation stays under Warrant/FAS.

Specialist routes automatically accelerate known classes on that path. Each route configures a Remuda namespace slice, first tools, and a playbook/scout brief on the shared Investigator harness; it is not a new binary per domain or an agent farm.

Prefer “generic / wide Remuda specialist” in prose for generic — keep the id.

Machine-readable export: sme-catalog.yaml.

id	display_name	domain	remuda_path	first_tools	when it fires
generic	Generic Investigator (Wide Remuda)	general	/public/mcp	k8s_get, k8s_events	fallback / unknown
k8s-imagepull	Kubernetes ImagePullBackOff	kubernetes	/ns-9/mcp	k8s_get, k8s_describe, k8s_events	ImagePullBackOff, ErrImagePull
k8s-oom	Kubernetes OOM / Memory Pressure	kubernetes	/ns-9/mcp	k8s_get, k8s_logs, k8s_events	PodOOMKilled, KubePodOOMKilled, ContainerOOMKilled
k8s-pod-crash	Kubernetes Pod CrashLoop	kubernetes	/ns-9/mcp	k8s_get, k8s_logs, k8s_events	KubePodCrashLooping, KubePodNotReady, KubeContainerWaiting
k8s-storage	Kubernetes PVC / Disk Pressure	kubernetes	/ns-9/mcp	k8s_get, k8s_describe, k8s_events	KubePersistentVolumeFillingUp, KubePersistentVolumeErrors, PersistentVolumeClaimPending

Living export aligns with python -m app.playbooks (ADR-033). Public pages show these five specialist routes.