The Pressure on Operations: Complexity, Dependency, Cost and Machine-Speed Change

All courses / AI Operations / Module 1 / Chapter 3

Learning objectives

After the lesson the participant can:

Name the six pressures and the operations functions on which each lands
Grade a claim about operations as measured, surveyed or argued and say how far it carries
Explain the common mechanism in the three provider outage reports of 2025
Draft a dependency-and-blast-radius map for one Tier 1 service with recovery evidence and unknowns

Key concepts

Three grades of evidence: Measured evidence rests on the issuer's telemetry, records or the text of an instrument; surveyed evidence on self-reported answers from a stated, often self-selected group; argued evidence on reasoning from mechanism, and is only as strong as its stated premises.
Shared fate: The pattern in the provider reports: a small first fault, such as a record, a policy row or a permission, propagates through a mechanism built for efficiency, such as global replication, a shared regional endpoint or automated distribution of a configuration file.
The review-capacity argument: The book's argued conclusion: review by people scales with competent readers and their time, authoring by agents scales with compute, so the gap closes through shallower reviews, a growing queue, or a machine reviewing the machine's change, acceptable only if independent.
The cost of seeing: Telemetry volume grows with the number of services while the people who can read it do not, so the share of signal anyone reads falls and O1 Observe risks becoming a store and not a sense.
Dependency-and-blast-radius map: A record for one Tier 1 service of what it depends on, what depends on it, what it would take down, and what evidence exists that recovery works, with each recoverability claim carrying a test, a date and a result, and unknowns listed with owners.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Interactive exercise 1 · Sort

Observable, expected or speculation

Sort each statement about the pressures on operations by the label the chapter gives it.

Interactive exercise 2 · Scenario

What goes on the map

Apply the chapter's practical guide on the dependency-and-blast-radius map.

Teaching plan

15 min	The teacher presents the six pressures with the table of where each lands and introduces the three grades of evidence with the chapter's examples.
15 min	Groups each read one of the three provider reports of 2025 as summarised in the chapter and report the first fault and the mechanism that propagated it.
15 min	Presentation of the review-capacity argument, the telemetry and skills surveys with their limits, and the regulatory clocks named in the chapter.
35 min	Exercise: participants draw a dependency-and-blast-radius map for one service.
10 min	Debrief on the unknowns each group wrote down and on the difference between Nordvik Region's and Hansa Mutual's concentration.

Discussion

The chapter warns that a measured incident report is a measurement of one failure chosen by its visibility. How should that limit what you conclude from a well-known outage?
If machine-authored change keeps rising, which of the three ways of closing the review gap is your organisation taking today, and what does it hide?
Nordvik Region's own monitoring saw the SamDrift DNS fault 22 minutes after the provider's status page. What does that say about where its observation depends on what it observes?

Written exercise

Exercise · 35 minutes

A dependency-and-blast-radius map in an afternoon

For one Tier 1 service of your own, or Hansa Mutual's claims core system SVC-HM-001, write the availability objective, recovery time and recovery point; if one is missing, record it as the first unknown. List what the service calls, using traces, infrastructure code and network flow data where you have them and not memory, including shared services such as identity, DNS, certificates, time and the observability pipeline. State the blast radius and the degraded mode. For each recoverability claim, give the test, its date and its result, or mark it untested. Finish with a list of unknowns, each with an owner.

Deliverable: A one-page service record with dependencies, blast radius, recovery evidence with dates and results, and at least two owned unknowns.

Your work

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

Which grade of evidence does the chapter assign to the claim that review capacity does not scale with AI-authored change?
Show the answer
C. Argued, from mechanism with stated premises
The chapter calls this its own conclusion, argued and not measured: it follows from premises about how review and authoring scale, and is only as strong as those premises.
What did Mandiant report as the average time to exploit for the 138 vulnerabilities disclosed in 2023 and exploited in the wild?
Show the answer
B. 5 days, against 32 days in 2021 and 2022
The chapter cites an average of 5 days for the 2023 sample, down from 32 days in 2021 and 2022 and 63 days in 2018 and 2019, as the most direct expression of adversary pressure on O3 Change.
Why can neither organisation write recoverable for the service whose test is cited in the chapter?
Show the answer
D. The last recorded test failed on time and has no re-test
RST-NR-2027-002 measured 5 hours 20 minutes against 2 hours, and RST-HM-2027-004 measured 5 hours 40 minutes against 4 hours; both failed and neither has been re-tested, so the claim cannot be made.