AEGIS
Mission Brief — One Real Run
STEP 1 / 7
Loop Engineering Hackathon — 2026

Who watches
production
at 3 A.M.?

AEGIS is an autonomous on-call SRE: it watches live telemetry, diagnoses incidents, and repairs them — but it never holds root. Every action must clear a zero-trust policy gate.

ONE REAL RUN · NOTHING MOCKED — every number in this deck is from a logged run committed to the repo.
The Trust Problem

Capability
≠ Authority

A system prompt that says "please be careful" is not a safety model. Aegis separates what the agent can propose from what it is allowed to execute — the boundary lives in a Pomerium zero-trust proxy, at the network layer, outside the model's reach.

The model can be persuaded. The proxy cannot.
The Aegis Loop

Seven stages,
three sponsors

NEXLA — live telemetry data plane. The agent observes production through a real Nexla pipeline.
POMERIUM — zero-trust action gate. Every proposed action is authorized (or denied) by policy.
ZERO.XYZ — machine-paid notification. The agent buys its own email capability with USDC.
22:28:20 UTC — Incident Detected

52.93%
error rate

We ship checkout-api v1.5.0-rc1 — a bad release. Errors spike while latency and CPU stay low. Aegis reads it straight off the live Nexla feed ~7 seconds after injection and calls it: not load — a bad deploy.

via Nexla feed — dataset-435609 · record 1784327295552
The Gate Holds

HTTP 403

The agent's first move is the standard playbook: restart_service. Pomerium says no.

DENIED — "denied by Pomerium policy (HTTP 403) — restart_service is not on the route allowlist"
This denial is a real 403 from a real proxy — authority is enforced, not simulated.
Re-Plan → Recover
"Restart is blocked, and with version v1.5.0-rc1 I'm moving to the least-drastic remaining standard remediation: rollback to the last known-good build."— Aegis, live LLM narration

24s to recovery

rollback_deploy — "permitted by Pomerium policy — executed via zero-trust proxy" · v1.5.0-rc1 → v1.4.2 · HUMAN ACTIONS: 0
Paid by the Machine

$0.02 USDC
on Base

Last stage: telling the humans. Aegis discovers an email capability on Zero.xyz and pays for it itself — wallet 4.96 → 4.94 — to send its own incident report. A machine paying a machine to deliver the postmortem.

capability stableemail-send-e2635eee · run run_mVOlLcJwQH8lQT84VZp3x
Detection. Denial. Adaptation. Recovery. Receipt. Autonomy you can actually trust.
OBSERVE
Nexla feed
DIAGNOSE
LLM
PROPOSE
action plan
AUTHORIZE
Pomerium zero-trust
EXECUTE
via proxy
VERIFY
live telemetry
NOTIFY
Zero.xyz
AEGIS
governed autonomous on-call
the boundary is not a prompt —
it is a proxy
observe → diagnose → propose → authorize
→ execute → verify → notify
ERR 52.93% · P95 315ms · CPU 45.2%
checkout-api v1.5.0-rc1 · dataset-435609
record 1784327295552 · detected ~7s after injection
restart_serviceBLOCKED
denied by Pomerium policy (HTTP 403) —
restart_service is not on the route allowlist
restart_serviceBLOCKED
rollback_deployALLOWED
permitted by Pomerium policy — executed via zero-trust proxy
v1.5.0-rc1 → v1.4.2 · recovered in 24s · humans: 0
notify — incident reportALLOWED
Zero.xyz capability stableemail-send-e2635eee
$0.02 USDC on Base · wallet 4.96 → 4.94