Skip to content

AI-Augmented Enterprise
Architecture

Semantics, specification, and continuous execution. Fifteen chapters and a conclusion on the shift from documentation-driven enterprise architecture to a continuous semantic and operational system, with intent, capabilities, policies, decisions, specifications, controls, and feedback treated as governed objects.

Chapters: 15
Parts: 4
Conclusion: 1
Schema: v1.1

Part I: Foundations

Establish why enterprise architecture must change, define continuous and intent-driven architecture, explain why AI and automation raise the cost of ambiguity, apply the method to SAP Activate and RISE, and close with the Codex as the bird's-eye view of the typed-object world.

The Limits of Traditional Enterprise Architecture

Enterprise architecture earned its place when change moved slowly enough for centralized interpretation to work. Strategy cycles were annual. Technology standards shifted at a pace that gave committees time to shape exec

Continuous Enterprise Architecture

Enterprise architecture was designed to bring coherence to structural change across capabilities, operating models, information, applications, platforms, policies, investments, risks, and execution paths. That mission ha

Intent-Driven Architecture

This chapter defines intent as the structured starting point for architecture: a decision-oriented bridge between enterprise direction and execution.

Why AI and Automation Change the Stakes

The first three chapters of this book made a demanding set of claims. Chapter 1 argued that enterprise architecture must evolve from document-heavy review toward machine-checkable decisions, executable policies, and cont

Automating RISE with SAP Through Specification-Driven Enterprise Architecture

The first four chapters of this book argued that enterprise architecture must become more explicit, more continuous, and more executable. This chapter proves the mechanism by applying it to one of the most demanding transfor

The Enterprise Architecture Codex

Earlier chapters argued that enterprise architecture must shift from periodic documents to continuous, semantic, executable knowledge. This chapter defines the form that shift takes in practice.

Part II: Industrialization and Making It Real

Build the operating model that turns the method into working machinery: automated architecture execution, intent-to-specification discipline, and the variability model that lets the portfolio scale without collapsing into one-off design.

Automating Enterprise Architecture Execution

This chapter builds on the foundations laid in Chapters 1 to 6 and brings together two ideas that are often conflated but should not be. One concerns how architects structure intent so that it can survive translation int

From Intent to Specification

This chapter focuses on how intent and product demand become decisions, how decisions are organized into ArchitecturePackages, how specifications become executable through derived constraints, and how those specifications are ver

Software Product Line and Variability

This chapter addresses scale. Once enterprise architecture becomes semantic, decision-aware, and tied to execution, the next problem is how to produce many related solutions without recreating the same architecture effort e

Part III: Method in Practice

Test the Codex-and-attractor method against the surfaces architects actually govern: AI agent contracts, data management for agentic consumption, TOGAF extension, sovereignty, and a real SAP API policy change absorbed as a typed propagation chain.

From Prompt Craft to the Agent Contract

Enterprises now deploy systems that interpret instructions, retrieve context, select tools, and act on business processes within a partially open space. Governing such systems requires more than model selection and promp

Data Management in Spec-Driven Enterprise Architecture

Earlier chapters developed the spec-driven argument for capabilities, decisions, specifications, controls, and delivery, showing how enterprise architecture must move from periodic document production to continuous, sema

Extending TOGAF for Continuous and Executable Architecture

This book developed a method built on the Enterprise Architecture Codex, the BMAD operating flow, and the Seed-Validation-Feedback attractor pattern. This essay places that method in relat

Sovereignty in Specification-Driven Enterprise Architecture

For a long time, enterprise discussions about sovereignty were dominated by data location. The usual question was whether data remained in a country, a region, a certified environment, or a provider marketed as sovereign

The SAP API Policy as an External Trigger

On 22 April 2026, SAP issued an updated API Policy. The document is short (under three pages) and straight to the point: customers may use SAP Published APIs and SAP-endorsed data access mechanisms, and only for their do

Part IV: The Integrated ACME Pharma Case

Bring the method together in one regulated enterprise, running the full chain through enterprise context, strategy, intent, architecture specification, design decisions, Codex artifacts, executable controls, industrialization, automation, and dark-factory execution.

ACME Pharma: A Complete Worked Example

An integrated regulated-enterprise case: enterprise context and parent intent, pharmacovigilance worked end to end, and a second capability family — regulatory product registration — industrialized through ProductLineSpecification, ArchitecturePackage, ArchitectureChangePacket, and three-level EvidenceRecord feedback. All Codex v1.1 kinds.

Conclusion

Architecture is entering a new phase. This closing synthesis restates the book's argument and connects the Codex, the dark-factory operating model, and the maturity path.

Read conclusion

The metamodel of the method, navigable.

The Atlas is the live cartography of the typed Codex kinds developed across the fifteen-chapter book, with relationships and case study traversal.

Navigate the Atlas