02 · Runtime
A layer that owns the runtime.
Observability watches. Orchestration schedules. Antimetal sits between your team and the cloud and keeps a current model of what is allowed to change. Agents do not chat about production; they hold it.
Antimetal · Production research
Production that runs itself.
It reads the live graph without waiting for a ticket.
It acts on the runtime with a sealed, reversible plan.
It improves the next loop from what last broke.
FIG. 01 · WORLD GRAPH
The agents already knew the blast radius before we opened the ticket. That is the difference between a dashboard and a colleague.
FIG. 04 · INCIDENT HALF-LIFE
30d · n=418
AntimetalBaseline ops
Aproduction graph is not a status page. It is a moving mechanical drawing: lag, certificates, queues, and the people who still have to sign.
Human-in-loop work decays slowly. Autonomous close, when the world model is current, drops the half-life of an incident instead of decorating it.
We keep the drawing thin on purpose. Color is reserved for the one curve that actually bent.
A new layer of the stack
Manifesto
Production should run itself.
FIG. 07 · CONTROL PLANE
01 Your Team
intent · policy · review
02 Antimetal Agents
patrol · triage · repair
03 Antimetal World Model
graph · memory · blast radius
04 Cloud platforms
AWS · GCP · Azure · k8s
05 Production
runtime that stays alive
AWS
EKS
RDS
IAM
04 · Operation
Everyone else watches. We operate.
A ticket is a delayed drawing of something the graph already knew. The useful layer is the one that can freeze writes, rotate a cert, and leave a record a person can still read at 03:00.