The Transformed Role Defined: Mandate, Accountabilities and Decision Rights · The Transformed Security Architect: the course

All courses / The Transformed Security Architect / Module 1 / Chapter 4

Learning objectives

After the lesson the participant can:

Explain why the role is defined by a charter kept as code and what three properties that adds.
Distinguish accountability for a boundary from authorship of its artefacts, and name the three parts of that accountability.
Assign decide, recommend, veto or escalate to a decision class with a tier and a time limit.
Test a draft charter against past decisions and classify each result as resolved, ambiguous or too slow.

Key concepts

Role charter: A machine-readable statement of the mandate, accountabilities, decision rights with time limits, escalation paths, owned artefacts and exclusions of the role, precise enough to settle a contested decision. A job description describes a person; a charter describes what the role may decide and stop.
Accountability for the property: The charter attaches accountability to the boundary holding, in three parts: the design is adequate for the accepted risk, verification shows it holding, and risk owners have been advised in time and in plain language when a boundary cannot be held within appetite.
Decide, recommend, veto, escalate: The four verbs of decision rights. They sit on tier 1 pipeline gates, tier 2 design authority, tier 3 AI governance board and tier 4 management body, each with a time limit; a veto not exercised in time lapses to the escalation path.
Narrow veto: A veto limited to properties that are expensive to restore once a contract is signed or a system is live, such as a missing stop path or egress limit, judged against a short, testable criterion and subject to recorded override by a named higher authority.
The approval rule: The person who approved is accountable for the approval, and the person who designed the gate is accountable for what the gate lets through. An agent that drafted a change proposed it and is accountable for nothing.

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

Which right for which decision class

Sort each decision class under the right the chapter's default table gives the security architect.

Interactive exercise 2 · Scenario

The stop that waited for the architect

Use the charter's reasoning on who may stop a production agent.

Teaching plan

15 min	Lecture on why a charter and why as code, the mandate as products, and the seam between the security architect and the AI architect for agents.
15 min	The teacher walks through the decision-rights table; participants explain the two commented rows on stopping a production agent and stopping the architect's own agents.
15 min	Compare the charters ROLE-NR-SA-01 and ROLE-HM-SA-AI: what a single post needs and what a team of six needs, and who can override each veto.
35 min	Exercise: participants draft decision rights for their own role and test them against five past decisions, revising every ambiguous or too-slow case.
10 min	Debrief on the four exclusions and on Hansa's test case in which a stop took 22 minutes because the runbook treated the architect's confirmation as a precondition.

Discussion

The chapter says a right to review without a limit is a right to delay. Which of your current review rights would lapse if a time limit were attached, and what would be lost or gained?
Why does the charter deny the architect the right to accept residual risk, and what happens in a small organisation where one person both designs and operates?
Nordvik turns every right that would let one person approve their own work into a recommendation to the CISO. How would you handle the same problem in a function with a single post?

Written exercise

Exercise · 35 minutes

Draft and test charter decision rights

Collect ten decisions that your security architecture role took, influenced or was blamed for over the last year, including at least one contested decision, one slow decision and one supplier decision. Group them into decision classes. For each class assign a verb, defaulting to recommend, granting decide where the catalogue already sets the standard and veto only for properties expensive to restore, together with a tier and a time limit: working days for design decisions and minutes for anything touching a running agent. Write three exclusions under a heading of what the role does not do. Then resolve five of the past decisions against your draft and classify each as resolved, ambiguous or too slow, changing the draft for every case that fails.

Deliverable: A draft charter section listing decision classes with verb, tier, time limit and override holder, three exclusions, and a five-row test table showing resolved, ambiguous or too slow.

Your work

Self-test

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

Under the chapter's default decision rights, what is the architect's right when an agent or system in production must be stopped?
Show the answer
C. Recommend to the stop holder, never as a precondition
The stop holder is the person on the incident rota who can act at three in the morning. Making the architect a precondition would make stopping more expensive than continuing, so the architect only recommends.
Where a gate merged a delegated change class without human approval, who answers under the charter's rule?
Show the answer
D. The gate policy's author for its adequacy, and the delegating forum for the delegation
The gate policy's author answers for its adequacy and the forum that delegated the class answers for the delegation, so the chain of accountability never ends in an agent or a pipeline.
What ceiling does Nordvik's charter ROLE-NR-SA-01 place on the architect's own AI use?
Show the answer
B. Level 1 Assisted, in Modes 1 and 3 under MND-NR-01
The charter caps the architect's own AI at Level 1 Assisted for Modes 1 and 3 under MND-NR-01, stricter than the Level 2 Supervised that version 1.0.0 of the manifest allowed; the stricter ceiling governs from the charter's effective date.