AI Operations · Module 1 · The Operations in Question

The Operations Loop Defined: Five Functions, Autonomy Budget and Observer Principle

The lesson defines the frame the rest of the course uses. Participants learn what each of the five functions takes in, produces and where it ends; the eleven action classes and how a ceiling is set; the autonomy budget and what counts as an autonomy error; the four prohibitions on Level 4 Autonomous; the three tests of the observer principle; and resilience as a claim. They write a delegation profile for one agent and one service.

Lesson 4 of 31Chapter 4120 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Operations / Module 1 / Chapter 4

Learning objectives

After the lesson the participant can:

Key concepts

Action class
A kind of effect on the estate, not a tool. The book names eleven, from read and annotate to delete and restore-overwrite; a runbook step belongs to exactly one, and any class not listed in a delegation profile is undelegated.
Autonomy budget
A tolerance for faulty actions that each Level 3 class carries per window, 28 days by default. Errors counted by the observer consume it; a review is held at 70 per cent, and at 100 per cent the class falls to Level 2 until a named authority decides otherwise.
Autonomy error
An action that had to be reversed, whose intended effect the independent observer did not find or found with the service worse, that the policy decision point refused as outside the mandate, or that had a customer-visible or regulator-visible effect, which consumes the whole tolerance at once.
Observer principle
Three tests: the verification does not share its failure modes with the action (independence in model, data, authorship, vendor and time), the observer does not depend on the system it observes, and the stop path works when the platform does not.
Resilience as a claim
A statement of recoverability with a scope, an objective, a measurement, a date and a result. Its status is derived by rule, only a verified claim may be called recoverable, and evidence expires by clock, 180 days by default for a Tier 1 restore or failover test, or on substantive change.

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

Where Level 4 Autonomous is never used

Sort each action by whether the chapter forbids Level 4 Autonomous for it or keeps Level 4 for it as a default ceiling.

Interactive exercise 2 · Scenario

A budget spent in one night

Apply the chapter's rules on the autonomy budget and on who may raise or lower a level.

Teaching plan

20 minThe teacher draws the loop: five functions handing work through records, with the policy decision point, the independent observer and stop path, and the resilience register outside it, and explains why they sit outside.
25 minWalk through the table of eleven action classes and their default ceilings; participants explain for three classes why the ceiling is what it is, using the four answers.
20 minWorked calculation of budget consumption with the Hansa Mutual tolerance for restarts, followed by the four Level 4 prohibitions and the mechanism behind each.
10 minShort input on the three observer tests, the six statuses of a resilience claim and the partial mappings to NIST CSF 2.0 and DORA Articles 8 to 13.
35 minExercise: participants write a delegation profile for one agent and one service.
10 minPeer review of profiles against the definition of done, and comparison with DLG-HM-OPS-001.

Discussion

  1. The chapter says raising a level is a recorded decision by a named authority while lowering one is immediate and needs no approval. What does that asymmetry protect, and who in your organisation would hold each right?
  2. A budget never touched in a year is called a signal. What are the two explanations the chapter offers, and how would you tell them apart?
  3. Why does the book treat a Level 3 runbook that deletes production data by a catalogued step as breaking the same rule as Level 4, in a weaker costume?

Written exercise

Exercise · 35 minutes

A delegation profile for one agent and one service

Write a delegation profile for an operations agent on one service, either your own or a profile DLG-NR-OPS-001 for Nordvik Region's portal. Copy the tier, objectives, recovery time and recovery point from the service record. List the agent's technical permissions and strike every action class the profile will not name. For each remaining class set a ceiling as the lowest of reversibility, blast radius, evidence and window, with a condition. Add the budget tolerance and window, the location of the policy decision point, what independently verifies each Level 2 or Level 3 action, the stop holders, and the date of the next review.

Deliverable: A delegation profile of one page with a ceiling and condition per action class, a budget, a named observer, stop holders outside the agent's platform and a review date.

Self-test

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

  1. What is the book's default ceiling for the action class restore-overwrite?

    Show the answer

    D. Level 1, with a named person executing after a restore into a separate target is compared
    Restore-overwrite is irreversible for what is overwritten, so the table caps it at Level 1: a named person executes after a restore into a separate target has been compared.

  2. An agent's request is refused by the policy decision point as outside its mandate, and nothing happens in production. How does the autonomy budget treat this?

    Show the answer

    A. It counts as an autonomy error, because an attempt costs even though nothing happened
    A refused attempt is one of the four conditions of an autonomy error and counts once. Only a customer-visible or regulator-visible effect consumes the whole tolerance, and the observer counts the errors, not the agent.

  3. Which of these does the dependence test of the observer principle ask?

    Show the answer

    B. Whether the observer depends on the system it observes and so goes silent when it fails
    The dependence test asks whether the observer can still report when the platform it watches has failed; a monitoring stack on the cluster it monitors goes silent, and silence reads as health. The other options describe the independence test, the stop test and evidence expiry.