Part two · Licence to Act · the interactive map
1 / 1
Licence to Act · Capgemini Financial Services · AI Enterprise Hub · October 2026 · witold.reichhart@capgemini.com
01
Capgemini Financial Services · AI Enterprise Hub

The control plane map

How much may an AI agent decide on its own?

Part one · the territory
Part one · what this part shows

The territory: what has to be in place before an agent acts for the firm.

Part one draws the map before any case. It starts from the question clients ask about control, shows why everyone means something else by it, and places their answers on the map, by altitude and essential. Then it places the words engineers already use on that map, lists the parts of each essential with their owners, and settles what the control plane is, a definition the rest of the set relies on.

  1. 3
    Everyone means something else by a control planeThe question clients ask about their agents, and six people who each answer it with their own part.
  2. 4
    Every firm decides inside an ecosystemThe law, supervisors, customers, and third parties around a firm that answers for every decision taken on its behalf.
  3. 5
    Every firm governs delegated work at three altitudesThe same work governed as policy, as authority for one process, and as controls in the systems.
  4. 6
    The essentials, each a question at every altitudeWho acts, what it relies on, what it may decide, may this act go ahead, what happened, should its authority change.
  5. 7
    Every box, for people and for agentsClick to turn the map: for people every box is filled today; for agents each has to be built so it can be checked.
  6. 8
    The words you already use, on the mapHarness, guardrails, gateway, policy engine, tracing: each lives in a box, and three boxes have no engineering word yet.
  7. 9
    What each essential holds, and who owns itThe parts of each essential, and its owners. Part three opens them one at a time.
  8. 10
    Everyone sees part of the mapThe six people from slide 3, each lighting the boxes they think about.
  9. 11
    The control plane instructs, and can say no before the actThe definition: platforms instruct; the mandate and the check can refuse, joined to the record and the loop.
  10. 12
    What the map does not draw yetAbove one act: delegation, cohorts, cascades, and other firms’ agents, coordinating through the traces they leave on the record.
  11. 13
    Follow one decision through the essentialsThe bridge to part two and its cases, one of them from outside financial services.
At the end you can answer
  • Why does one question about control get six different answers in the same firm?
  • What separates an entitlement from a mandate?
  • Where do the harness and the guardrails live on the map, and which three joins does a firm build itself?
Reading on your own

Read it first: parts two, three, and four assume the map it draws.

About 20 minutes. → or the space bar moves on, and through the steps first where a slide builds in steps. Click a line on the left to go straight to that slide.

M opens the contents, F finds a word, and T switches between light and dark.

Then part two follows one decision through the essentials, part three opens each essential for specialists, and part four turns the map to your firm.

The question

Everyone means something else by a control plane.

The question clients ask

“We have built dozens of agents, on three platforms and with four models. Am I in control of what they are all doing, and am I governing them properly?”

Each platform brings its own control plane, for its own agents.

Each of them is right about one part. Nobody can yet say how the parts fit together.

The ecosystem

Every firm decides inside an ecosystem.

The law sets what applies, supervisors and auditors examine, customers receive the decisions, and third parties run much of the technology. The firm answers for all of it.

The law and the regulators
conduct and consumer protectionprudential rulesdata protectionoperational resilienceAML and sanctionsthe AI Act
Supervisors and auditorsexamine what the firm decided, on what basis, and whether its controls held
Authoritycomes down: the firm reads the law and turns it into policy, limits, and controls
Evidencegoes back up: the record of what was decided, and why
The firm
Enterprise
Workflow
Platform
Customersreceive each decision, with its reasons, and can complain or challenge itdecisions go out · challenges come back
Third partiesthe cloud, model, and software providers that run much of the technology. The firm stays accountable for what they do on its behalf.

The firm answers for every decision taken on its behalf, whether a person, a system, or an agent takes it.

Three altitudes

Every firm governs delegated work at three altitudes.

The same work is governed three times: as policy for the whole firm, as authority for one process, and as controls in the systems. Each has its own rhythm, and any of them can change at once when something goes wrong.

Altitude
What is decided here
The form authority takes
How often it usually changes
Today, for example
From the law and the regulators: what applies to the firm
Enterprise
the board, the CRO, the CFO, compliance
How far the firm will go: the risk appetite, the policies, the ceilings on any delegation, and which work may be delegated at all.
Policy and ceilings
once or twice a year
The delegated authority policy: the ceiling for every role, and the four-eyes rules above it.
Workflow
the business owner, operations
Who may decide what in one process, for whom, and up to what amount.
The mandatefor a person: a role, with delegated authority and its limits
every day
A handler settles claims up to €5,000. An analyst releases held payments up to €25,000.
Platform
the CTO, the CISO, IT operations
How the rules become real where the work touches systems: access, enforcement, logs, and the ability to stop.
Entitlements and controls
at every release
The system lets each of them act within their authority, routes anything above it for approval, and logs both.

An entitlement lets someone reach a system. A mandate says what they may do there.

The essentials

The essentials, each a question at every altitude.

The three altitudes locate responsibility: the enterprise, the workflow, and the platform. The essentials say what must be governed at each of them: the agent, its knowledge, its mandate, the check, the record, and the loop. Each is a question anyone who acts for the firm has to answer; the first three are settled before the act, the fourth at the act, and the last two after it.

The first three must hold. The fourth checks them. The last two remember, and learn.

Every boxclick any box to turn it

The foothold

The words you already use, on the map.

Technical people arrive with a vocabulary of their own: the harness, the guardrails, the gateway, the policy engine. Each word lives in one box of the map.

The parts

What each essential holds, and who owns it.

Every essential is a set of parts, and every essential has owners who answer for it before the agent acts. Most of the parts can be bought. A few have to be joined.

1The agent itself
  • the model
  • the harness
  • guardrails
  • identity
  • the release
Owned bythe CTO and the platform team, with the CISO
2Its knowledge
  • the law, as read
  • policy
  • contract terms
  • the case
  • assertions
Owned bythe source owners, compliance, and the data teams
3Its mandate
  • an owner
  • a limit
  • a level
  • a review trigger
  • a version
Owned bythe business owner; the CRO challenges
4The check
  • six inputs
  • permit
  • refer
  • block
  • no other route
Owned bythe CTO and the CISO run it; the business sets its rules
5The record
  • who acted
  • on what basis
  • under which mandate
  • the receipt
  • the cost
Owned bythe CTO keeps it; risk, compliance, and audit read it
6The loop
  • signals
  • rules
  • return paths
  • narrow
  • widen
Owned bythe business owner, the CRO, and the source owners

Part three opens the essentials one at a time, for specialists.

The perspectives

Everyone sees part of the map.

The answers from the start, placed on the map. Each lights the boxes its owner thinks about.

Each of them is right about their part. The map is every box, and the links between them.

The control plane, strictly

The control plane instructs, and can say no before the act.

A control plane instructs and can refuse; a management plane watches and reports. Platforms already instruct: they route each call to a model, enforce guardrails, and grant access. For delegated decisions the plane also needs the part that can refuse an act: the mandate and the check, joined to the record and the loop.

Instructs

Identity, routing, guardrails, access

What the platforms already do, for their own agents: who the agent is, which model answers, what may go in and out, which systems it may reach.

Can refuse

The mandate and the check

w3 holds what the agent may decide, as data. w4 and p4 read it before every act, in the path of the act, and permit, refer, or block.

Three joins, built by the firm
  1. A versioned mandate the check can query: an object with an owner, a version, and an expiry.
  2. A record keyed to the mandate version and the build, so a decision can be rebuilt by someone who did not run it.
  3. A return path from the record to the mandate: narrow on a rule, widen on evidence and a signature.

Most of the boxes on the map can be bought or already exist. The three joins that make them a control plane have to be built, on the stack the firm already runs.

Above one act

One agent, one act, one mandate: what the map does not draw yet.

Every box on the map is drawn for one agent taking one act under one mandate. Above or beyond that are delegation, cohorts, cascades, other firms’ agents, and the agent’s own foresight: a firm that runs more than a handful of agents meets the first four, and the last is where the agents themselves are being taken.

1 · Delegation

One agent hands work to another

Whose mandate does the second act under, which check reads it, and does the record of the first name the second? The seventh case shows it: a credit agent with two delegates, under one mandate and its two sub-mandates.

2 · Cohorts

Several agents on one process, each inside its limit

Three elections on one issuer, each permitted, together over the concentration limit: locally correct, globally non-compliant, which the papers call dynamics blindness. The limit is a ceiling at e3, written so the check can read it; the check needs the sum of the permits in flight against it, which no single mandate holds. Situation card 5 plays it for one issuer; the limit no ceiling names in advance is what the map does not draw.

3 · Cascades

One agent changes the state another reasons over

A acts, B reads the changed state, C’s act now conflicts with both. Nothing any one of them did was wrong, and the firm’s position is. The failure sits in the dynamics between acts, where no box looks.

4 · Other firms’ agents

Your agent meets a counterparty’s, a client’s, a supplier’s

Two control planes, two mandates, two records, and nobody who can see both. What one firm permits is an input the other never declared.

5 · The agent’s own foresight

An agent that predicts the consequences of its own acts

Today’s agents infer the next token. The next ones are being built to carry a world model, like JEPA, and to plan an act by predicting what it will do. The map does not move: the predicted consequence enters the check as one more claim, one statement the agent relies on, with a standing, and the record keeps what the agent expected beside what happened.

How they coordinate: traces

No agent sees the whole picture, and none needs to. Each reads what the others left behind: a permit in flight, a state another changed, a claim another relied on. Those traces live on the map already: the record, w5, is where an agent leaves one; the estate, e2, and the knowledge that applies, w2, are the medium the traces share; the current state the check reads, w4, is their sum. So governing a cohort starts with governing the traces: who may leave one, with what standing, and who reads it before the next act.

Regulation governs the constraints and the control plane governs the act. What emerges when many agents coordinate is a territory of its own, and the set signals it here without drawing it: the reference model holds the question, and the seventh case draws the first step, one chain of three.

Part two

Follow one decision through the essentials.

Part two takes one decision through the map, essential by essential: the agent itself, what it knows, what it may decide, the check at the act, the record, and the loop. Then the demonstration. The case is chosen for the audience; the sixth shows the same map at work outside financial services, and the seventh shows one agent delegating to two.

Insurance

A motor claim of €3,400

Banking · payments

A payment of €18,500, held on a sanctions-screening hit

Banking · lending

The renewal of a €180,000 SME credit line

Capital markets

An election on an optional dividend, for 60,000 shares

Banking · collections

A repayment offer to a customer in arrears, in a conversation

Outside finance · a city

The renewal of a housing allowance

Banking · a chain of agents

A €220,000 SME renewal by a credit agent and two delegates