AEGIS · Stage 1
CrashLoopBackOff vertical slice
Walk the thinnest defensible product path: one tenant · one agent · one model · one tool · one approval · one audit execution ID. Remediation stays held — evidence before action.
Console remains read-only. Stage-1 proves the correlation fabric — not AutoRemediate.
- 01AEGIS freeze
Freeze the contract
AEGIS Stage-1 exit: end-to-end trace and evidence complete; no secret leakage; no production write from the console.
- 02Command Centre
One tenant scope
Nordic Federated Bank · FS Core Banking · production. Scope filters bind every tool call.
- 03Agent passport
One read-only agent
Kubernetes Agent 01 passport: L2 investigate, write verbs stripped, step budget enforced.
- 04Model Gateway
One local model
Model Gateway routes to Ollama llama-3.3-70b. Sovereign Mode denies external LLM APIs.
- 05Tool registry
One tool
k8s-read MCP — get/list/watch only. Delete and exec stripped at the gateway.
- 06Incident workspace
Investigate CrashLoopBackOff
payments-auth pod after deploy v4.21 — missing AUTH_JWKS_URI. Full timeline + sealed RCA.
- 07Open exec-clb-01
One immutable execution ID
AI Control Tower exec-clb-01: prompt → firewall → agent → Ollama → MCP → evidence → policy → approval hold.
- 08Approval queue
One approval gate
apr-clb-01 queues ConfigMap patch + rollout. Deterministic remediator does not start until approved.
- Exit criteria: complete AI path in Control Tower
- Exit criteria: sealed RCA with rejected hypotheses
- Exit criteria: approval pending — no silent write