Architecture as Code · Module 7 · Future & Wrap-up

Conclusion

The lesson draws the book together. It consolidates the Architecture as Code mindset as an interplay of technical craft and organisational intent, reviews how each capability builds on the previous layer, places the practice in the European regulatory context, presents the six-step adoption strategy, and ends with the unsolved challenge of governing AI-generated architecture decisions and the book's direct challenge to practitioners.

Lesson 31 of 31Chapter 2760 minutes

Read the chapterThe whitepaperThe slides

All courses / Architecture as Code / Module 7 / Chapter 27

Learning objectives

After the lesson the participant can:

Key concepts

Technical and organisational alignment
The chapter's position that cloud platforms, automation tooling and security principles form a single strategic capability, which must be matched by organisational investment in skills, culture and operating models so that new workflows can flourish.
Six-step adoption strategy
Foundational education, pilot projects on a contained low-risk service, security integration, scaling and automation, readiness and risk management before expanding to new domains, and future readiness.
Data residency as a first-class requirement
Treating data residency as a requirement from the earliest blueprints, which keeps infrastructure definitions aligned with EU data boundary commitments, sector-specific controls such as DORA for financial services, and horizontal frameworks such as the Data Governance Act and the Data Act.
Governance of AI-generated architecture decisions
The challenge the chapter calls unsolved: how to audit, attribute and enforce human accountability over machine-authored artefacts. Version control captures what changed, not whether the reasoning was sound or who held responsibility.
The constants
Declarative intent, repeatability, automated testing and continuous delivery, which the chapter says remain constant even as tooling evolves.

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

What each adoption step involves

Sort each activity into the step of the chapter's step-by-step adoption strategy to which the chapter assigns it.

Interactive exercise 2 · Scenario

Choosing the first pilot

Read the situation and choose what the chapter's reasoning leads to. Each choice gives feedback.

Teaching plan

10 minTeacher recaps the progression of the book: from declarative blueprints through platform, security and governance to organisation and future.
10 minWalk through the six-step adoption strategy and link each step to work participants produced in earlier modules.
10 minDiscussion of the closing reflection: what version control does and does not capture about a change proposed by a language model.
25 minExercise: the book's direct challenge, a retrospective decision record for an AI-assisted decision.
5 minParticipants each state one practice they will start next week. Close of the course content.

Discussion

  1. The chapter says version control cannot yet show how to roll back a conceptual mistake as opposed to a configuration error. What would a record need to contain to make that possible?
  2. Which step of the six-step strategy has your organisation skipped or done out of order, and what was the consequence?
  3. Of the four constants the chapter names, which is weakest in your current practice, and what is the smallest change that would strengthen it?

Written exercise

Exercise · 25 minutes

A retrospective decision record for an AI-assisted decision

Take up the chapter's direct challenge. Identify one decision in your own architecture estate where an AI system proposed or drafted the pattern, configuration or control, and where no traceable human rationale exists. Write an Architecture Decision Record for it retrospectively: status, context (including what the AI system proposed and on what input), the decision as it stands, the consequences, and the named person who now holds accountability for it. State what evidence shows the decision is still appropriate and when it will be reviewed. Add a short note on what your team would record at the time of the decision in future, and with whom in your community of practice you will share the approach.

Deliverable: One retrospective ADR with a named accountable person and review date, plus a half-page note on recording practice for future AI-assisted decisions.

Self-test

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

  1. Which challenge does the chapter describe as remaining genuinely unsolved?

    Show the answer

    C. The governance of AI-generated architecture decisions
    The closing reflection names the governance of AI-generated architecture decisions as unsolved: the profession must work out how to audit, attribute and enforce human accountability over machine-authored artefacts.

  2. What is the first step of the chapter's step-by-step adoption strategy?

    Show the answer

    B. Foundational education in principles and version control
    The strategy begins with foundational education: a common understanding of the principles and disciplined version control practices, followed by pilot projects.

  3. What does the fifth step of the adoption strategy ask organisations to do before expanding to new domains?

    Show the answer

    A. Validate readiness with the prerequisites framework and consult the anti-patterns
    Step five, readiness and risk management, validates organisational readiness using the framework of Chapter 26A and consults Chapter 26B to anticipate and mitigate common pitfalls.