The Transformed Security Architect · Module 6 · Experience and Conclusions

A Year in the Role: The Transformed Architect at Nordvik Region and Hansa Mutual

The lesson follows two security architecture practices through one year, from autumn 2026 to autumn 2027, in the order things happened and with the friction, mistakes and decision records of each turn. Participants see the four shifts as a sequence, learn what went wrong at Nordvik Region and Hansa Mutual and which designed mechanism caught each failure, how the architects' week changed, and how to review a year against the shifts. They write a year timeline with a went-wrong field.

Lesson 25 of 27Chapter 2575 minutes

Read the chapterThe whitepaperThe slides

All courses / The Transformed Security Architect / Module 6 / Chapter 25

Learning objectives

After the lesson the participant can:

Key concepts

The shifts as a sequence
Shift 1 came first because the charter, catalogue and tier policy in the repository were what every later step read; Shift 2 followed through contracts and gates; Shift 3 became real when stop paths were timed and failed; Shift 4 took the form of a deferral or of review tiers and caps.
went_wrong field
The entry in the year's timeline for every failed drill, expired exception, missed seed and gate decision reversed by sampling, linked to the decision that answered it or marked open. It is what makes the timeline evidence that the practice learns.
Wrong at scale
Hansa's July failure: a tier 1 gate restored a UK logging setting to the group baseline although it had been changed under an approved exception, because the gate did not read the exception register. No agent was involved; the post-merge sample found it.
The later instrument governs
How Nordvik settled the conflict between its manifest, which allowed edits at Level 2 Supervised, and its charter, which capped the architect's own AI at Level 1 Assisted: the stricter, later charter governed until the manifest was aligned as version 3.0.0.
Human binding constraint
The year-end finding in both organisations: the limit was one person's availability at Nordvik and six people's review capacity at Hansa, where reviewing AI-drafted proposals became the largest use of the team's time.

Interactive exercises

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

Interactive exercise 1 · Put in order

Nordvik Region's year

Put these events of Nordvik Region's year in the role in the order they happened.

Interactive exercise 2 · Sort

What caught each failure

Each thing that went wrong in the year was caught by a mechanism the architects had designed. Sort each failure under the mechanism that caught it.

Teaching plan

15 minThe teacher tells the year quarter by quarter from Table 25.1; participants keep a two-column note of what went wrong and what caught it.
15 minGroups reconstruct one failure each: the expired exception, the missed seed, the two stop drills, the aborted chaos experiment, the held model update or the wrong gate rule.
10 minRead the table of the architects' week before and after; discuss why verification takes time that the agents' drafting does not save.
30 minExercise: participants write a timeline of their own practice's last year with decisions, a went-wrong entry per failure and a shift per entry.
5 minWrap-up: each participant names the shift for which their year holds no measurement.

Discussion

  1. Both first stop drills failed, and the chapter calls this what a drill exists to produce. How would such a result be received by your management body, and how would you present it?
  2. During the architect's leave at Nordvik a model update was held for three weeks because only the architect's charter named one check. What does the fix in AIDR-0542 keep, and what does it change?
  3. At Hansa consultation, not engineering, set the agent team's pace. Is that a cost or a control, and why?

Written exercise

Exercise · 30 minutes

Review your year against the four shifts

Write the timeline of your security architecture practice for the last four quarters, following the chapter's practical guide. For each quarter list the decision records produced; a turn that left no record is itself a finding. Add a went-wrong entry for every failed drill, expired exception, missed seeded error and gate decision reversed by sampling, and link each to the decision that answered it or mark it open. Place each entry against one or more of the four shifts, using their exact names. Classify each year-end claim as verified, declared or failed. List what is open at year end. Keep the plan for next year out of the timeline: it is a separate artefact.

Deliverable: A four-quarter timeline in the form of NR-SA-2026-2027 with decisions, went-wrong entries, shifts, measured values and a list of what is open at year end.

Self-test

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

  1. Why did Nordvik's first out-of-hours stop drill of the benefits-triage integration route take 26 minutes against a budget of 15?

    Show the answer

    B. The managed security service provider held the runbook but not the credentials
    The provider held the runbook but not the credentials. Annex MS-1 then gave it authority to revoke credentials out of hours, AIDR-0541 added a scoped break-glass credential, and the October re-drill took 11 minutes.

  2. What did Hansa do when agent review volume rose by about 40 per cent after consultation and the Tier 2 queue lengthened?

    Show the answer

    C. It lowered the proposal cap and recorded the decision to slow the agents as AIDR-0593
    Because the proposal cap held, the queue grew and the depth of review did not fall. The head of security architecture lowered the cap and recorded the decision to slow the agents as AIDR-0593.

  3. What caught the tier 1 gate that wrongly restored a UK logging setting to the group baseline at Hansa?

    Show the answer

    A. The post-merge sample, six days later
    The post-merge sample found the change six days later. No agent was involved: a deterministic rule did exactly what it said, which is why the sampling exists. AIDR-0591 made every tier 1 gate read the exception register.