Build phase 5Planned
Multi-Agent + Secure Execution
The advanced layer: gVisor-sandboxed code execution for agents, and a multi-agent workflow with a human approval gate. This is the v1.0.0 milestone.
The final phase pushes into the hardest and most current problems in the space: how do you let an AI agent execute code on your cluster without handing it the keys, and how do you coordinate more than one agent safely? It targets the portfolio's v1.0.0: the point where a hiring manager clicking through GitHub sees a coherent, documented system.
Deliverables
- Agent Sandbox: gVisor-based secure execution for agent code, with no host kernel access, via a
RuntimeClasson the cluster. - Multi-agent workflow: a diagnostics agent that detects anomalies (using
crashdummyfault injection as reproducible test cases) and a remediation agent that proposes fixes. - Human approval gate: remediation requires explicit sign-off, with no autonomous changes to the cluster.
- Security threat model: a document covering the risks of AI agents on K8s and how gVisor mitigates them.
Portfolio v1.0.0
All repos tagged
v1.0.0, READMEs polished, architecture diagrams complete. Demo-ready: the whole system reads as one coherent, documented platform rather than a pile of experiments.Tasks
SANDBOX-001SANDBOX-002SANDBOX-003SANDBOX-004SANDBOX-005SANDBOX-006SANDBOX-007SANDBOX-008SANDBOX-009SANDBOX-010
Write-ups
- “Agent Sandbox deep dive: running untrusted AI code safely on Kubernetes.”
- “Multi-agent workflows on K8s: when one AI agent isn't enough.”