Repository navigation
Reference configs (sre-prometheus-k8s.toml, sre-mezmo-full.toml) #241
Description
Activity
- added a parent issue
on Jun 11, 2026 Two candidates for this from the July/August benchmark campaigns:
- The generic analyst/operator/debugger/verifier config from the Benchmark continuation-prompt clarity for a batteries-included default config #386 experiments. Score parity with domain workers on the RCA suite but 2.2x token cost, so it lost the init-default decision (feat(init): apply benchmark-validated orchestration defaults #505) - as a reference config for non-SRE workloads it still makes sense, with the cost numbers documented.
- The benchmark-winning domain configs themselves: the RCA fan-out config (144/144 on the mock-mcp suite) and the SREGym k8s port live in the ai-experiments repo (
aura-e2e/configs/rca/,sregym-aura-benchmark/configs/) and are close to the sre-prometheus-k8s shape this issue describes - mostly needing real MCP server blocks in place of the mocks.
The
aura inittemplate (#505) now carries the validated defaults, so reference configs here can focus on the per-stack parts: server blocks, mcp_filter lists, and worker rosters.- removed a parent issue
on Sep 2, 2026
Metadata
Metadata
Assignees
Labels
No labels
Figure out what a default batteries included config looks like for popular SRE use cases - probably mostly focused around hitting the ground running with K8s. This ties into the #251 as it would be used in the boostrap/onboarding flow and it will also tie into #239 (skills could be used to lazy load in heavy tool use details that are normally in the system prompt)