AI Operations · Module 5 · Operations in the Organisation

Decision Rights, Change Authority and the Incident Commander

The lesson concerns O2 Diagnose, O3 Change and O4 Restore at the decisions no runbook takes: declaring an incident, commanding it, approving an emergency change, authorising a failover, restoring over data, breaking a freeze and stopping an agent. Participants learn the six fields of a decision right, four rules about position, the incident commander's pre-assigned authority, change authority after the weekly board, and the stop right.

Lesson 22 of 31Chapter 2290 minutes

Read the chapterThe whitepaperThe slides

All courses / AI Operations / Module 5 / Chapter 22

Learning objectives

After the lesson the participant can:

Key concepts

Decision right
The authority to take a defined decision and to be obeyed, written as a requirement with six fields: a holder role filled from a rota, two deputies, a response time, an evidence standard, a record and a ceiling for AI.
Position governs
Four rules: the authoriser does not run, the requester does not approve, the acceptor of a risk neither authors nor closes, and a conflicted holder passes the decision to a deputy and says so in the record.
Incident commander
The role that holds the incident by a written, pre-assigned authority, decides class and severity, hands over by a recorded briefing and has deputies who are as qualified. An assistant files what the commander approves and never classifies or speaks externally.
Change authority
The decision rights over what enters production: a standard change approved once as a class, a normal change approved by a peer and a gate, a small forum for exceptions, and an emergency change declared by a person and approved by the commander, never the requester.
Stop right
The right to stop an agent or hold a pipeline, held by listed roles including one reachable out of hours, without approval, through a mechanism outside the platform, drilled within 90 days. Restart is a separate decision by the agent owner at a lower level.

Interactive exercises

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

Interactive exercise 1 · Match

What AI does in the decisions of a bad night

Match each decision with what the AI does in it, as the chapter's table of ten decisions states.

Interactive exercise 2 · Scenario

The commander approved the suspect change

Apply the chapter's rules about the position of the decider.

Teaching plan

15 minThe teacher lists the decisions of a bad night that no runbook takes and introduces the six fields and the four rules about position.
15 minTabletop: an incident is running, the commander approved the change now under suspicion and is also the agent operator. Participants resolve who decides what and what goes in the record.
15 minPresentation of the failover table by claim status, the restore over existing data, risk acceptance, and the five things a supervisor should receive.
35 minExercise: participants build a decision-right matrix.
10 minDebrief on Nordvik Region's short file with a standing acceptance and Hansa Mutual's profile enforced by its policy decision point.

Discussion

  1. The chapter does not forbid a failover on a failed claim. What does it require instead, and why is forbidding it the worse design?
  2. A prohibition of Chapter 4 is not a risk to be weighed and cannot be accepted by anyone. What is the difference between that and a risk a named person may accept with an expiry?
  3. At Hansa Mutual the night commander is also the agent operator. Which decisions become conflicted in that arrangement, and how should the profile resolve them?

Written exercise

Exercise · 35 minutes

The first ten decisions of a bad night

Replay the last three Tier 1 incidents of your organisation from their records, or use Nordvik Region's incidents on the portal, and list every decision taken, by whom, and how long it waited. Reduce the list to ten decisions, including declare and classify, hand over command, stop an agent, approve an emergency change, authorise failover, restore over existing data and break a freeze. For each write the holder role, two deputies, the response time, the evidence standard, the record, and the highest level at which AI takes part and what it does. Mark any right with a single holder or none reachable out of hours.

Deliverable: A decision-rights file of ten rows with six fields each, with single-holder and out-of-hours gaps flagged and an owner for closing each gap.

Self-test

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

  1. The failover claim for a service is expired. Under the chapter's table, what does the incident commander need before authorising the failover?

    Show the answer

    D. Concurrence by the head of SRE or deputy, by telephone, with the status stated
    For an expired or implemented but unverified claim the commander decides with the status stated and concurrence from the head of SRE or deputy, recorded with a time-boxed acceptance that ends with the incident.

  2. What is the highest level at which AI takes part in breaking a freeze, according to the table of ten decisions?

    Show the answer

    A. Level 0 Advisory: it reads and flags the conflict; never an agent
    Breaking a freeze is held by the commander and the head of SRE with a recorded exception. AI only reads and flags the conflict at Level 0 Advisory, in line with the Level 4 prohibition on acting inside a freeze.

  3. Who approves an emergency change under the chapter's change authority?

    Show the answer

    C. The incident commander, who is never the requester
    An emergency change is declared by a person and approved by the commander, and the requester does not approve. An agent may draft the change at Level 2 but never chooses emergency or approves it.