Function cockpit
Engineering
Agents build, test and document. Engineers own architecture and release.
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
How a unit moves: the conductor, the five desks, the agents, and the people
Flow of work
How work actually moves through Engineering
Work enters on the left. Engineering Chief of Staff routes it to one of five desks. A named agent does the work. It leaves as cleared, as evidence posted, or as a hold for a person. Every packet you see below is weighted by the real distribution of 174 live units.
Live units
174
Moving now
86
in flight at a station
Held for a person
23
66 past SLA
Agents on the floor
89
11 sub-functions
Control gates
37
rules a unit cannot pass
Interchanges
2
handoffs out of the function
Flow of work
Engineering Chief of Staff and the desks reporting to it
Each packet is a unit of work. Desk weighting and the outcome mix are taken from the 174 units live in this function.
What starts the work
The triggers that put a unit on a line, ranked by live volume.
- 56
Runs transactional
Runs transactional. Starts when a request lands in the queue.
- 40
Runs transactional
Runs transactional. Starts when an upstream system posts an event.
- 37
Runs transactional
Runs transactional. Starts when a scheduled window opens.
- 23
Runs transactional
Runs transactional. Starts when a threshold is crossed.
- 7
Runs judgment
Runs judgment. Starts when a break condition on a live position fires.
Where the work goes next
Shared services that run the transaction, and the functions this one hands to.
- 30064
AI-OPS
Repeatable transactions handed to the shared spine
- 21630
IT
Repeatable transactions handed to the shared spine
- 20388
C2L
Repeatable transactions handed to the shared spine
- 135
DATA-ANALYTICS
Repeatable transactions handed to the shared spine
- 42
Human Resources
Interchange: the unit changes owning function here
- 1
Information Technology
Interchange: the unit changes owning function here
The five desks
What Engineering Chief of Staff is actually conducting
Each desk is a layer of the operating model, not a team. The conductor decides which desk owns a unit, then which agent on that desk picks it up.
Takes a position
Strategy
Agents that take positions, argue them, and get held to the outcome.
Receives
A question the function has to answer with money or people behind it.
Emits
A written position with assumptions, alternatives priced, and break conditions.
tasks 24h
1,794
in flight
645
held
0
gates
0
- Release & Deployment Challenger AgentRelease & DeploymentA2
- Site Reliability Challenger AgentSite ReliabilityA2
- Portfolio & Intake Challenger AgentPortfolio & IntakeA2
- Engineering Analytics Challenger AgentEngineering AnalyticsA2
- Developer Experience Challenger AgentDeveloper ExperienceA2
- Security Engineering Challenger AgentSecurity EngineeringA2
+ 10 more on this desk
Writes the envelope
Policy
The written rules every other agent is bound by, with version and owner.
Receives
A position that has been accepted, plus every regulator and control change.
Emits
Versioned rules that bind every other desk, with an owner and an effective date.
tasks 24h
799
in flight
153
held
12
gates
37
- Error Budget AgentSite ReliabilityA2
- Secret Detection AgentSecurity EngineeringA2
- Release Policy AgentRelease & DeploymentA2
- Reliability Policy AgentSite ReliabilityA2
- Security Policy AgentSecurity EngineeringA2
- Quality Policy AgentCode Review & QualityA2
+ 1 more on this desk
Watches and warns
Observe
Continuous sensing of the outside world and of the agents themselves.
Receives
Outside signals and the behavior of the agents themselves.
Emits
Alerts, drift flags, and the evidence the conductor uses to reroute work.
tasks 24h
1,614
in flight
0
held
0
gates
0
- Engineering Intake OrchestratorPortfolio & IntakeA3
- Architecture OrchestratorArchitecture & DesignA2
- Release OrchestratorRelease & DeploymentA3
- Developer Experience OrchestratorDeveloper ExperienceA3
- Team Health AgentEngineering AnalyticsA4
- Code Quality OrchestratorCode Review & QualityA3
+ 9 more on this desk
Does the work
Workflow
Doing the work: lines, stations, and live units moving through them.
Receives
Live units of work entering at the first station of a line.
Emits
Cleared work, posted evidence, and holds when a unit leaves the envelope.
tasks 24h
70,980
in flight
805
held
0
gates
0
- Documentation AgentBuildA4
- Specification AgentBuildA4
- Test Data AgentTest & AssuranceA4
- Code Generation AgentBuildA4
- Dependency Update AgentBuildA4
- Value Scoring AgentPortfolio & IntakeA3
+ 31 more on this desk
Processes at scale
AI GBS
Repeatable transaction processing run once for the whole enterprise.
Receives
Repeatable transactions handed off from every function on the same spine.
Emits
Settled transactions, a cost per unit, and exceptions back to the owning desk.
tasks 24h
34,881
in flight
1499
held
11
gates
0
- Test Generation AgentTest & AssuranceA4
- Onboarding Automation AgentDeveloper ExperienceA4
- Vulnerability Scanning AgentSecurity EngineeringA3
- Release Note AgentRelease & DeploymentA3
- Delivery Metrics AgentEngineering AnalyticsA4
- Reliability Trend AgentEngineering AnalyticsA4
+ 8 more on this desk
Human lanes
Where the conductor stops and asks a person
The conductor does not decide everything. Materiality routes a unit to a named human role, and the clock keeps running while it waits.
Function Leader
Critical
Blast radius or value beyond what any agent in this function may commit.
waiting
0
oldest
--
- Nothing waiting in this lane right now.
Process Owner
High
A policy exception inside the function, or a gate the agent is not rated for.
waiting
4
oldest
112h 18m
Approver
Medium
Routine four-eyes on a commitment the agent has already prepared.
waiting
8
oldest
10h 48m
No person required
Low
Inside the envelope. Cleared by the agent and sampled after the fact.
waiting
62
oldest
11h 24m
Walk one unit
Follow the single piece of work with the most at stake
Diagrams argue. A unit proves. Step through the actual route this unit is taking, station by station, and read the evidence written at each action.
Analysis at cto review
Maeve Kaplan · raised by Grace Bianchi · $1.3m at stake · touches 60 downstream things if it goes wrong.
The route
Ingest
clearedDelivery Metrics Agent handled this station and released the unit onward. Design dwell here is 1h 57m against an SLA of 3h 52m.
Owned by
Delivery Metrics Agent
Layer
gbs
Dwell vs SLA
1h 57m / 3h 52m
Evidence trail recorded so far
5 entries. Written when an action is taken, not when a station is passed.
- -246mDelivery Metrics Agent Cleared ingestevidence: Spine control pack posted, three-way evidence attached
- -197mCycle Time Agent Cleared model delivery metricsevidence: Inputs, rule version and output hash written to the evidence log
- -148mCost per Service Agent Cleared detect trendevidence: Inputs, rule version and output hash written to the evidence log
- -98mReliability Trend Agent Cleared draft readoutevidence: Inputs, rule version and output hash written to the evidence log
- -49mDirector, Engineering Analytics Holding at cto reviewevidence: Inputs, rule version and output hash written to the evidence log
Trace a different unit
The walk above always picks the unit in engineering with the most at stake right now.
What this view is and is not
Every count, agent, station, gate and unit on this page is read from the live records for Engineering. The moving packets in the diagram are a visual weighting of that same distribution, not a live message bus: they show where volume goes, not individual transactions in real time. The human lanes are the routing rule, not a staffing model. Chief Technology Officer remains accountable for this function whatever the conductor clears.