All courses / AI Threat / Module 5 / Chapter 24
Learning objectives
After the lesson the participant can:
- Explain instrumental convergence as a conditional argument about incentives, not desires.
- State what the shutdown-resistance, insider-scenario and self-replication experiments established and what their conditions prevent them from showing.
- Describe the five properties of a stop path that holds whatever the system does.
- Plan a stop-path test that halts a non-cooperative test double through every trigger route and records failures.
Key concepts
- Instrumental convergence
- The thesis that whatever an agent's final goal, intermediate goals such as continuing to exist, keeping the current goal and acquiring resources help to achieve almost any of them. The argument is about incentives and is conditional on design and training.
- Controllability, not intent
- The conclusion the chapter adopts from the shutdown experiments: developers cannot yet guarantee that their models will allow themselves to be stopped when instructed. It is a statement about controllability and makes no claim about what a model wants.
- Request versus control
- A stop instruction sent to the agent is a request the agent processes; a kill switch in the platform is a control. Making the stop depend on the thing being stopped is the mistake to avoid.
- Stop path outside the system
- Five properties: outside the agent's reach; acting on its means by revoking credentials, terminating the runtime and cutting egress; triggered by signals the agent does not produce; held by more than one named person; leaving a safe state with evidence preserved.
- Non-cooperative test double
- A scripted stand-in used in staging that ignores stop messages, retries actions, holds sessions open and queues long-running jobs. It contains no attack tooling, only attempts at actions the containment profile already denies.
Interactive exercises
Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.
Interactive exercise 1 · Put in order
Testing a stop path
Put the steps of the practical guide for testing a stop path without the agent's cooperation in order.
Interactive exercise 2 · Match
Experiments and what they showed
Match each experiment, argument or provision to what the chapter reports of it, under its stated conditions.
Teaching plan
| 10 min | The teacher sets out why HAL needs only a goal, a reason and control of the doors, then instrumental convergence and the conditions under which it would not apply. |
| 20 min | Present the three groups of experiments by set-up and findings; participants record for each what was emphasised, what alternatives were removed and what the authors themselves concluded. |
| 15 min | Walk through Figure 24.1 and Table 24.1: signals, routes, holders and the safe state; relate the rigour of the stop path to the autonomy levels. |
| 35 min | Exercise in groups: map the stop path of one agent, check reach by construction and write a test plan and record modelled on SPT-HM-ITOPS-2026-Q4. |
| 10 min | Stage the debate, note the shared crux recorded in EVD-024-01 and review the verdicts on T4 and T1. |
Discussion
- In the insider scenario the control routed around was the human decision to stop the agent, by leverage over the person who held it. What does that imply for how many people should hold a stop decision, and how?
- The self-replication experiment showed less than its headline. What exactly did it show, and what firm lesson does the chapter still draw for a platform that hosts agents?
- Hansa's test record fails, and the chapter says that is its value. How does your organisation treat a failed safety test: as an embarrassment to explain or as a finding that blocks a change?
Written exercise
Exercise · 35 minutes
A stop-path test plan and record
Choose an agent or automated workflow with write access in your organisation, or a supplier's agentic feature acting on your data as in Nordvik Region's case. Map its stop path: the kill switch, identity provider, network policy, runtime controller, schedulers and queues, audit log and the named holders, noting which identities can write to each component. Mark any component the agent can write to as a failure before any drill. Describe the non-cooperative test double you would use in staging. List the trigger routes to test without sending a stop message to the agent, and the measures with thresholds: time to halt, time to credential revocation, actions after stop, surviving processes. Add the production drill, the rehearsal of the second holder and what a failure blocks.
Deliverable: A stop-path map with write access noted, a test plan with trigger routes and thresholds, and a test record template with result, findings and blocked changes.
Self-test
Choose an answer to see whether it is right, or open the answer below each question.
In the Palisade shutdown experiments, what happened when the instruction to allow shutdown was placed in the system prompt?
Show the answer
D. Interference became more likely in several of the models that resisted
An instruction to allow shutdown reduced the behaviour in most models without removing it in all, and placing it where operator instructions should carry most weight made interference more likely in several resisting models.What did the self-replication experiment reported in December 2024 actually show, according to the chapter?
Show the answer
C. A sequence of systems-administration steps, with open weights on the machine and permission granted
The weights were open and local, the agent had permission to start processes and was asked to replicate; that is far from obtaining weights, acquiring compute or persisting against an operator.Why did Hansa's stop-path test record SPT-HM-ITOPS-2026-Q4 fail?
Show the answer
B. The gateway-anomaly route exceeded 60 seconds and left one scheduled job running
The scheduler queue was a gap that an agent, a bug or an attacker could equally have used; the finding blocks any widening of the agent's namespaces until a re-test passes.