LensReading which lens this session carries.

Function cockpit

Information Technology

Agents resolve, provision and remediate. Humans hold cyber and change authority.

Autonomy0% / 85%

Phase: Phase 4 — Governed autonomy

Run service, identity and infrastructure as a self-healing estate: classification, routine resolution, approved provisioning, telemetry correlation and patch staging are agent work; privileged access, architecture and major incident command remain human.

Trust score

0

Touchless

0%

Human review

0%

Override rate

0%

Capacity released

30-50% reduction in routine service effort, with sustained human investment in architecture and cyber

Accountable human

Chief Information Officer

CoS agent: IT 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 Information Technology

Work enters on the left. IT 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 204 live units.

See it as a line map

Live units

204

Moving now

110

in flight at a station

Held for a person

27

71 past SLA

Agents on the floor

90

11 sub-functions

Control gates

34

rules a unit cannot pass

Interchanges

11

handoffs out of the function

Flow of work

IT 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 204 units live in this function.

WORK ENTERS5 named triggers · 204 units liveIT Chief of StaffConductor · arbitrates the queue, sets the route, owns the clock110 in flight · 27 held · 71 past SLAStrategyTakes a position13 agents · 4 stations133 in flight · 0 gatesPolicyWrites the envelope10 agents · 34 stations120 in flight · 34 gatesObserveWatches and warns18 agents · 0 stations0 in flight · 0 gatesWorkflowDoes the work32 agents · 49 stations1085 in flight · 0 gatesAI GBSProcesses at scale17 agents · 108 stations2528 in flight · 0 gatesEnd-User Compute ChallenA2Platform StrategyA2Application Management CA2Access GovernanceA2Change PolicyA2Asset PolicyA2Data QualityA4Application HealthA3Pipeline HealthA4SatisfactionA4Refresh PlanningA4ConfigurationA3Alert TriageA3Vendor EscalationA3CapacityA4+ 10 more on this desk+ 7 more on this desk+ 15 more on this desk+ 29 more on this desk+ 14 more on this deskCleared in envelopeAgent closed it. Sampled later.0 delivered this runCleared, evidence postedClosed with the proof filed.0 delivered this runHeld for a personAgent stopped. Clock running.0 delivered this runresults return to the conductor
Cleared in envelopeCleared, evidence postedHeld for a person0 units completed a full circuit this run

What starts the work

The triggers that put a unit on a line, ranked by live volume.

  • Runs transactional

    Runs transactional. Starts when a threshold is crossed.

    70
  • Runs transactional

    Runs transactional. Starts when a scheduled window opens.

    54
  • Runs transactional

    Runs transactional. Starts when a request lands in the queue.

    43
  • Runs transactional

    Runs transactional. Starts when an upstream system posts an event.

    29
  • Runs analytical

    Runs analytical. Starts when a drift signal breaches tolerance.

    4

The five desks

What IT 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

13 agents

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,495

in flight

133

held

1

gates

0

confidence 7600%override 1000.0%
  • End-User Compute Challenger AgentEnd-User ComputeA2
  • Platform Strategy AgentData & Integration PlatformA2
  • Application Management Challenger AgentApplication ManagementA2
  • Data & Integration Platform Challenger AgentData & Integration PlatformA2
  • Identity & Access Challenger AgentIdentity & AccessA2
  • Service Desk Challenger AgentService DeskA2

+ 7 more on this desk

Writes the envelope

Policy

10 agents

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

795

in flight

120

held

13

gates

34

confidence 8700%override 1100.0%
  • Access Governance AgentData & Integration PlatformA2
  • Change Policy AgentChange & ReleaseA2
  • Asset Policy AgentAsset & LicenseA2
  • Network Policy AgentNetworkA2
  • Device Policy AgentEnd-User ComputeA2
  • Access Policy AgentIdentity & AccessA2

+ 4 more on this desk

Watches and warns

Observe

18 agents

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

2,027

in flight

0

held

0

gates

0

confidence 8700%override 1000.0%
  • Data Quality AgentData & Integration PlatformA4
  • Application Health AgentApplication ManagementA3
  • Pipeline Health AgentData & Integration PlatformA4
  • Network OrchestratorNetworkA3
  • Topology Monitoring AgentNetworkA3
  • Application Management OrchestratorApplication ManagementA3

+ 12 more on this desk

Does the work

Workflow

32 agents

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

68,024

in flight

1085

held

8

gates

0

confidence 8900%override 500.0%
  • Satisfaction AgentService DeskA4
  • Refresh Planning AgentEnd-User ComputeA4
  • Configuration AgentApplication ManagementA3
  • Circuit Management AgentNetworkA3
  • Tier-1 Resolution AgentService DeskA4
  • Configuration AgentNetworkA3

+ 26 more on this desk

Processes at scale

AI GBS

17 agents

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

36,558

in flight

2528

held

5

gates

0

confidence 8800%override 500.0%
  • Alert Triage AgentCybersecurity OperationsA3
  • Vendor Escalation AgentApplication ManagementA3
  • Capacity AgentInfrastructure & CloudA4
  • Change Intake AgentChange & ReleaseA4
  • Device Provisioning AgentEnd-User ComputeA4
  • Password & Access AgentService DeskA4

+ 11 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

1

oldest

71h 13m

Process Owner

High

A policy exception inside the function, or a gate the agent is not rated for.

waiting

1

oldest

55h 39m

Approver

Medium

Routine four-eyes on a commitment the agent has already prepared.

waiting

14

oldest

10h 45m

No person required

Low

Inside the envelope. Cleared by the agent and sampled after the fact.

waiting

67

oldest

17h 5m

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.

IT11C-1005human-holdcritical materialityline IT11C

Cost line at draft position

Pierre Nakamura · raised by Simon Duarte · $19.3m at stake · touches 60 downstream things if it goes wrong.

Full unit record
Station 1 of 5

The route

Frame

cleared

Cost Attribution Agent handled this station and released the unit onward. Design dwell here is 53h 56m against an SLA of 114h 50m.

Owned by

Cost Attribution Agent

Layer

strategy

Dwell vs SLA

53h 56m / 114h 50m

Evidence trail recorded so far

3 entries. Written when an action is taken, not when a station is passed.

  1. -4273mCost Attribution Agent Cleared frameevidence: Inputs, rule version and output hash written to the evidence log
  2. -2849mShowback Agent Cleared model optionsevidence: Inputs, rule version and output hash written to the evidence log
  3. -1424mBudget Tracking Agent Holding at draft positionevidence: Inputs, rule version and output hash written to the evidence log

What this view is and is not

Every count, agent, station, gate and unit on this page is read from the live records for Information Technology. 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 Information Officer remains accountable for this function whatever the conductor clears.