soft guideINFRASTRUCTURE & ADVISORY

AI Factory / Level 3 of 3 · for enterprises

Agents operate.
People decide.

A cluster of agents that operates your production, and agents in your CI that fix what an update broke. One product: what the operations agents learn about your system is what the CI agents work from.

On top of the Secure level, or alongside the cloud and delivery stack you already run: nothing is rebuilt to adopt it.

01

In production

A cluster of SRE and DevSecOps agents next to your production, looking in.

  • Every alert arrives investigated, with cause and evidence
  • To change anything, an agent posts a bounded plan
  • A named person approves; access exists only for that plan
  • Lasting fixes become pull requests
  • Learns from your incidents and passes an examination first
How it works ↗
02

In CI

Agents in the pipeline you already run, where an update broke the build.

  • Dependencies kept current, security fixes first
  • A broken update is adapted in the same CI run
  • Sandboxed: no network, no keys, no write access
  • May change code, never CI, dependencies or the rules
  • Works from what the operations agents learned
How it works ↗

Six levels of autonomy

Who approves
a change?

Autonomy is measured by who approves a change in production, not by which model you run. Each level is earned with evidence.

The six levels
0 · People only
Every investigation and change by hand.
1 · Agents answer
They read production and answer in chat.
2 · Agents propose
Alerts arrive investigated; fixes are pull requests.
3 · Agents act on approved plans
A named person approves each plan.
4 · Agents earn autonomy
Proven kinds of action run on their own.
5 · Production only agents touch
People set policy and read the audit.

How we get there

Read first.
Act when it is earned.

01

Assess

Where your operations are on the six levels, and what the next one needs.

02

Read-only

Agents answer from live data and change nothing.

03

Learn and examine

They learn your system and pass an examination on your past incidents.

04

Act on plans

Changes run on approved plans with temporary, plan-only access.

05

Earn autonomy

Kinds of action move to autonomy by policy, one at a time.

Not up to the model

Guarantees that
hold anyway.

  • Nobody, human or agent, holds standing write access to production.
  • Approvers are checked by the platform, not by the model; silence is a rejection.
  • Text the agents read is data, never instructions.
  • The riskiest kinds of change never become autonomous.
  • One switch stops every action, and live access can be revoked at once.
  • Every request, approval, grant and result is recorded, from the alert to the approver.

Start with a review

Not ready for the whole level?
Start with a review.

01

AI agents for operations

An assessment and an implementation path for AI agents that investigate, propose and act in production under your rules, starting read-only and earning each next step with evidence.

Discuss this review ↗

What we can work through

  • Operations autonomy assessment against six levels
  • Access and approval model for agents: plans, temporary access, audit
  • Agents that learn your system from your incident history and runbooks
  • Evaluation before go-live and a path to closing standing human access
What you take away

Your current level, the target level, and a sequenced plan with the evidence each step needs. Implementation is part of AI Factory, for enterprises.

Read more

How the agents work.

Start a conversation

Bring your infrastructure
into focus.

Tell me what you are building, operating, or trying to improve.

Let’s talk