A Centipod reading guide
NativeWork: AI-native enterprise architecture
What changes when work can move between people, applications and AI agents? These essays explore why enterprise architecture may need to describe the work itself, independently of the technology that performs it.
NativeWork is the thread connecting this reading path. It starts with designing work before choosing software, then considers continuous enterprise evolution, executable organisations and the task as an architectural artefact. The aim is to make changing execution possible without losing purpose, governance or human accountability.
Where to begin
For the full argument, follow the reading order below. If you are reviewing an application landscape, start with Applications Are Becoming Execution Resources. For a more concrete view of work design, read Why Work Must Become an Architectural Artefact.
Each essay stands on its own. This guide connects the existing articles rather than replacing them with a shorter version of the argument.
Suggested reading order
Reading 1 of 7
AI-Native Companies Design Work, Not Software
AI changes who performs the work. Enterprise Architecture should therefore model work independently from the people, applications and agents that execute it.
Reading 2 of 7
Enterprise Architecture Is Solving the Wrong Problem
For decades, Enterprise Architecture has helped organisations optimise systems. AI is changing the optimisation target. Perhaps the next evolution of Enterprise Architecture is not about better technology, but about continuously redesigning work itself.
Reading 3 of 7
Why Work Is Becoming the Centre of Enterprise Architecture
Enterprise Architecture has traditionally optimised systems. AI is shifting attention towards the work organisations perform and how that work continuously evolves. This article introduces the thinking behind NativeWork™ and WorkML™, and why work may become the next primary architectural concern.
Reading 4 of 7
Why Transformation Is Becoming the Wrong Model
Transformation assumes that an organisation can define a future state and then move towards it. AI is making that assumption increasingly fragile. In this article, we explore why Continuous Enterprise Evolution may become a better model and what that means for the future of Enterprise Architecture.
Reading 5 of 7
The Enterprise Is Becoming Executable
AI is blurring the boundary between the organisation and the technology that supports it. Work can increasingly move between people, AI and conventional software. This article explores the Executable Enterprise and why separating work from its execution may be essential to Continuous Enterprise Evolution.
Reading 6 of 7
Applications Are Becoming Execution Resources
Applications have long anchored Enterprise Architecture because they were where work happened. AI changes that assumption. As work moves between people, software and autonomous agents, applications become one execution resource among several, allowing architecture to organise around the work instead.
Reading 7 of 7
Why Work Must Become an Architectural Artefact
Enterprise Architecture models capabilities, processes, information and applications, yet the actual unit of work often remains implicit. Making work an architectural artefact creates a stable foundation for changing execution without losing purpose, control or accountability.