The Transformed Security Architect · Module 4 · The Role in the Organisation

Design Authority, Decision Forums and Gates Instead of Meetings

The lesson shows how the architect delegates routine decisions without losing accountability for them. Participants learn why forums fail, what a gate does that a meeting does badly, the tier policy as data with its three design rules, the properties of a working gate, the design authority, exceptions as expiring records, and the five rules that answer when an AI may change the architecture. They classify decisions into tiers and write an expiring exception.

Lesson 17 of 27Chapter 1790 minutes

Read the chapterThe whitepaperThe slides

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

Learning objectives

After the lesson the participant can:

Key concepts

Tier policy as data
A list of decision classes in version control, each with a tier, a decider, required evidence, a time limit and an owner, read by gates and forums. A class qualifies for tier 1 only if a machine can check its evidence.
Direction decides the ceiling
A class that loosens a boundary is never delegated as far as one that tightens it. For AI proposers, tightening or restoring changes may reach Level 3 Bounded behind an external gate; loosening changes stay at Level 2 Supervised or below.
Working gate
A gate whose rule is versioned and tested, whose rule is not owned by the author of the change it gates, whose bypass is possible, visible and reviewed, and which is itself reviewed for staleness. The override rate measures its health.
Design authority
The tier 2 forum for exceptions, deviations, precedent and contested items. It works asynchronously first on pull requests, has a written mandate and a quorum by role, and an objection from the security architect escalates to the next tier and is not outvoted.
Expiring exception
A record of a decision to live with a control gap for a stated time, with an owner, a tested compensating control and an expiry enforced by a gate. Renewal is a new decision that requires new evidence, not an extension.

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 tier decides

Sort each decision under the tier that takes it in the chapter's tier policy.

Interactive exercise 2 · Scenario

An agent proposes to widen an allow-list

Apply the chapter's five rules for AI-proposed changes to the architecture.

Teaching plan

15 minLecture on forums and gates and on the four tiers; participants name a decision in their organisation that waits for a session although a rule could take it.
15 minRead Hansa's tier policy: why C3 is a standing approval, and why C7 and C8 sit at Level 0 Advisory for any AI proposer.
10 minWalk through EXC-NR-0007: the compensating control, the expiry at the tier 2 maximum, the renewal requirements and the two fields specific to a public authority.
35 minExercise: participants classify ten recent decisions into tiers with the delegation test, set the autonomy ceiling per class and write one expiring exception.
15 minDebrief on delegation without abdication: sampling tier 1 decisions, measuring approval quality at forum level and reporting upwards.

Discussion

  1. The chapter says a design authority that approves every pull request in seconds is a gate with a delay. How would you tell the difference in your own forum?
  2. Gates that cannot be bypassed will be bypassed unseen. What would a break-glass path need to record in your pipeline for you to trust it?
  3. Hansa measures and delegates; Nordvik designs a route and writes down who answers at the end of it. What does a tier policy offer an organisation with no standing board?

Written exercise

Exercise · 35 minutes

Tier ten decisions and write an exception

Take ten security architecture decisions from the last two quarters of your review board or equivalent, recording each item's class, wait and outcome. Apply the delegation test: a class moves to a gate only if it recurs, is reversible or low in blast radius, can be decided from machine-checkable evidence, and has a policy and an owner, with a stricter test for loosening classes. Assign each class a tier from 1 to 4, a decider, a time limit and the maximum autonomy level for an AI that proposes a change in that class. Then write one exception from your own estate as an expiring record with control, scope, reason, risk, owner, compensating control and its test, approver and tier, expiry and what renewal requires.

Deliverable: A tier policy table for the classes found, in the form of Hansa's policy, and one exception record in the form of EXC-NR-0007.

Self-test

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

  1. Before a class of decisions is delegated from the board to a gate, what does the chapter's practical guide require of shadow running?

    Show the answer

    C. Gate and board agree on at least 95 per cent of at least 20 decisions, every disagreement explained
    The class runs in shadow for four weeks and is delegated only when gate and board agree on at least 95 per cent of at least 20 decisions and every disagreement is explained.

  2. In Hansa's tier policy, at what maximum level may an AI propose a change to the tier policy itself or to a stop path?

    Show the answer

    A. Level 0 Advisory: an agent must never change the rule that governs it or the path that stops it
    Classes C7 and C8 are at Level 0 Advisory for any AI proposer, because an agent must never change the rule that governs it or the path that stops it. Both are tier 3 decisions.

  3. What does the chapter say about renewing an exception?

    Show the answer

    D. It is a new decision that requires new evidence; a renewal attaching nothing new is declined
    Renewal is a new decision, not an extension, and requires new evidence such as a supplier's committed date or a fresh test result. A renewal attaching nothing new is declined.