LensReading which lens this session carries.

Function cockpit

Engineering

Agents build, test and document. Engineers own architecture and release.

Autonomy0% / 80%

Phase: Phase 3 — Functional orchestration

Run the intent-to-release graph as a governed system: decomposition, code generation, testing, documentation, vulnerability detection and deployment preparation are agent work; product intent, architecture and production release remain human.

Trust score

0

Touchless

0%

Human review

0%

Override rate

0%

Capacity released

25-40% engineering capacity in selected software-factory settings (case-specific)

Accountable human

Chief Technology Officer

CoS agent: Engineering Chief of Staff

Strategy, policy, observe, workflow, and AI GBS side by side

Five layers

What Engineering actually runs

A function is not one thing. It sets direction, writes the rules it is bound by, watches the world and itself, does the work on lines, and pushes repeatable transactions into a shared spine. Agents work in all five — not just the last two.

Strategy

16 agents

Agents that take positions, argue them, and get held to the outcome.

16 positions on the record

6 ratified, 4 in challenge

Policy

7 agents

The written rules every other agent is bound by, with version and owner.

34 binding rules

29 active, 5 superseded or retired

Observe

15 agents

Continuous sensing of the outside world and of the agents themselves.

15 watchers running

They watch the outside world and the agents themselves

Workflow

37 agents

Doing the work: lines, stations, and live units moving through them.

33 lines, 174 live units

23 held for a person right now

AI GBS

14 agents

Repeatable transaction processing run once for the whole enterprise.

4 shared towers

75 stations on this function run inside AI GBS

Strategy layer — positions on the record

Every position names its author, the agent paid to argue against it, and the conditions that would break it.

Investment Position

Ratified

Hold the ceiling at A3 for portfolio & intake. Triage, estimation and dependency mapping are agentic. What the engineering organization spends its quarter on is a leadership commitment. Raise it only after two consecutive quarters where the override rate stays under five percent and every override has a written cause.

author Portfolio Strategy Agentchallenged by Portfolio & Intake Challenger Agentratifier VP Engineering Operationsconfidence 70%outcome partially held

Portfolio & Intake Operating Position

Draft

Keep the repeatable request volume in the spine and pull the exception tail back into the function. The spine is cheaper per unit; the tail is where the context that prevents rework actually sits.

author Portfolio Strategy Agentchallenged by Portfolio & Intake Challenger Agentratifier VP Engineering Operationsconfidence 85%

Design Decision

Rejected

Hold the ceiling at A2 for architecture & design. Agents author the design options and the decision record. Architecture decisions constrain years of future work, so a review board ratifies them. Raise it only after two consecutive quarters where the override rate stays under five percent and every override has a written cause.

author Architecture Strategy Agentchallenged by Architecture & Design Challenger Agentratifier Chief Architectconfidence 69%

Architecture Strategy Position

In challenge

Keep the repeatable design decision volume in the spine and pull the exception tail back into the function. The spine is cheaper per unit; the tail is where the context that prevents rework actually sits.

author Architecture Strategy Agentchallenged by Architecture & Design Challenger Agentratifier Chief Architectconfidence 84%

Architecture & Design Operating Position

Draft

Redesign the lane around exception density rather than volume. Volume is already absorbed; the cost that remains is concentrated in a small share of design decision cases that no current agent resolves without a human.

author Architecture Strategy Agentchallenged by Architecture & Design Challenger Agentratifier Chief Architectconfidence 75%

Build Operating Position

Draft

Hold the ceiling at A4 for build. Code generation and dependency maintenance are near-touchless. A human still approves every merge into a protected branch — that gate is the whole control. Raise it only after two consecutive quarters where the override rate stays under five percent and every override has a written cause.

author Build Orchestratorchallenged by Build Challenger Agentratifier Director, Platform Engineeringconfidence 87%
16 positions across 11 sub-functions. Open a sub-function to see dissent, alternatives considered, and break conditions.

Policy layer — what binds the agents

Versioned rules with an owning agent, a human approver, and the agents they constrain.

Portfolio & Intake Decision Envelope

vv5.6

Agents in this lane may act without a human when the request sits inside the stated value, risk and confidence envelope. Outside it, the unit holds at a gate with a named approver and a running clock.

owner Engineering Intake Orchestratorapproved by VP Engineering OperationsAPACbinds 5 agents

Portfolio & Intake Evidence Standard

vv1.0

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. An action with no evidence record is treated as a control failure, not a fast decision.

owner Engineering Intake Orchestratorapproved by VP Engineering OperationsGlobal · EUbinds 5 agents

Portfolio & Intake Escalation Rule

vv3.5

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires. VP Engineering Operations owns the response clock.

owner Engineering Intake Orchestratorapproved by VP Engineering OperationsEU · UK · USbinds 5 agents

Portfolio & Intake Autonomy Ceiling

vv3.8

The ceiling for this lane is 74 on the platform scale. Triage, estimation and dependency mapping are agentic. What the engineering organization spends its quarter on is a leadership commitment. The ceiling is a governance decision, not a technical limit, and only VP Engineering Operations can propose moving it.

owner Engineering Intake Orchestratorapproved by VP Engineering OperationsAPACbinds 5 agents

Architecture & Design Decision Envelope

vv5.8

Agents in this lane may act without a human when the design decision sits inside the stated value, risk and confidence envelope. Outside it, the unit holds at a gate with a named approver and a running clock.

owner Pattern Compliance Agentapproved by Chief ArchitectLATAM · USbinds 4 agents

Architecture & Design Evidence Standard

vv1.6

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. An action with no evidence record is treated as a control failure, not a fast decision.

owner Pattern Compliance Agentapproved by Chief ArchitectAPACbinds 4 agents
34 rules in the register. An agent cannot act outside the version in force.

Workflow layer — the lines doing the work

Each line is a workflow. Each station is a stage. Each unit is a live piece of work.

109 clear42 evidenced23 held
LineSub-functionKindUnits / wkTouchlessTimetableActualStations
EN1A

Intake-to-Backlog

Portfolio & Intaketransactional4,38872%8.2h8.3h7
EN1B

Capacity Rebalance

Portfolio & Intakeanalytical7347%135.6h131.7h4
EN1C

Investment Position

Portfolio & Intakejudgment142%297.1h327.3h5
EN2A

Design Decision

Architecture & Designjudgment528%828.0h665.3h7
EN2B

Pattern Compliance Sweep

Architecture & Designtransactional6,93967%6.6h8.3h5
EN2C

Architecture Strategy Position

Architecture & Designjudgment234%281.2h306.4h5
EN3A

Feature Build

Buildtransactional1,61081%18.7h24.5h6
EN3B

Dependency Update

Buildtransactional6,82682%22.8h24.6h6
EN3C

Documentation Sync

Buildtransactional7,09189%16.9h20.3h4
EN4A

Pull Request Review

Code Review & Qualitytransactional6,83889%11.9h14.8h6
EN4B

Quality Debt Sweep

Code Review & Qualitytransactional30486%19.1h22.1h4
EN4C

Convention Change

Code Review & Qualitytransactional2,43286%21.5h16.2h4
EN5A

Release Test Cycle

Test & Assurancetransactional5,59789%1.7h2.2h6
EN5B

Flaky Test Remediation

Test & Assurancetransactional2,70690%11.5h10.2h5
EN5C

Performance Baseline

Test & Assurancetransactional7,69793%9.1h8.6h4
EN6A

Production Release

Release & Deploymenttransactional2,59879%23.0h18.7h7
EN6B

Emergency Revert

Release & Deploymenttransactional6,80988%10.9h9.5h5
EN6C

Release Readiness

Release & Deploymenttransactional4,65678%21.4h20.2h3
EN7A

Incident Response

Site Reliabilitytransactional7,79385%17.7h17.8h8
EN7B

Error Budget Enforcement

Site Reliabilitytransactional3,05385%24.4h31.5h5
EN7C

Capacity Response

Site Reliabilitytransactional5,26385%23.6h20.6h4
EN8A

Debt Remediation

Technical Debttransactional7,72778%17.8h20.8h6
EN8B

Deprecation Campaign

Technical Debttransactional4,77282%6.1h7.3h5
EN8C

Debt Doctrine Position

Technical Debtjudgment449%268.4h345.6h5
EN9A

Environment Request

Developer Experiencetransactional3,67488%9.2h8.0h5
EN9B

Friction Remediation

Developer Experiencetransactional5,89094%22.4h25.3h6
EN9C

Developer Onboarding

Developer Experiencetransactional4,39190%9.5h9.2h5
EN10A

Vulnerability Remediation

Security Engineeringtransactional3,32681%1.0h0.9h7
EN10B

Secret Exposure Response

Security Engineeringtransactional4,24180%13.8h15.2h6
EN10C

Threat Model Review

Security Engineeringjudgment352%655.1h708.3h6
EN11A

Monthly Engineering Read

Engineering Analyticsanalytical8375%168.1h208.6h6
EN11B

Cost per Service Read

Engineering Analyticsanalytical5262%171.7h142.8h4
EN11C

Measurement Doctrine Position

Engineering Analyticsjudgment442%163.3h150.2h5

Observe layer — the watchers

Sensing agents and the agents that supervise other agents.

Engineering Intake Orchestrator

Owns the portfolio & intake lane end to end. Sequences the other agents, holds the timetable, and decides what surfaces to a human.

A394%

Portfolio & Intake Challenger Agent

Adversarial reviewer for portfolio & intake. Argues the opposite case on every position and flags where the evidence does not carry the claim.

A290%

Architecture Orchestrator

Owns the architecture & design lane end to end. Sequences the other agents, holds the timetable, and decides what surfaces to a human.

A293%

Architecture & Design Challenger Agent

Adversarial reviewer for architecture & design. Argues the opposite case on every position and flags where the evidence does not carry the claim.

A286%

Build Orchestrator

Owns the build lane end to end. Sequences the other agents, holds the timetable, and decides what surfaces to a human.

A393%

Build Challenger Agent

Adversarial reviewer for build. Argues the opposite case on every position and flags where the evidence does not carry the claim.

A288%

Code Quality Orchestrator

Owns the code review & quality lane end to end. Sequences the other agents, holds the timetable, and decides what surfaces to a human.

A390%

Complexity Monitor

Watches code review & quality continuously. Detects drift, quantifies it, and routes what matters without waiting for a reporting cycle.

A491%

AI GBS layer — the shared spine

Repeatable transaction processing does not belong to this function. It runs once for the enterprise.

c2l20,462 units / wk routed

Portfolio & Intake · Test & Assurance

it21,633 units / wk routed

Release & Deployment · Security Engineering

ai-ops30,064 units / wk routed

Site Reliability · Developer Experience

data-analytics139 units / wk routed

Engineering Analytics

Stations running inside AI GBS

75 of 176 stations(43% of the function's stations)

Read this page as the honest answer to “what would an 80% agentic Engineering look like?” The strategy and policy layers are where the argument happens. The workflow and AI GBS layers are where the volume goes. The observe layer is the only reason the other four can be trusted.

Sub-function breakdown