Doesn't suit? No problem! You can return items for up to 30 days
You won't go wrong with a gift voucher. The gift recipient can choose anything from our offer.
Up to 30 days for returns
The blueprint everybody approved last quarter no longer matches what is being built. Requirements shift, evidence arrives late, and the diagrams turn into fossils while the real system evolves without them. Modern engineering teams are drowning in data and starving for direction: terabytes of schematics, thousands of diagrams, endless simulation results, and still nobody can answer the only question that matters. Why did we make this choice, and can we prove it works?
The Continuum names the flaw: we practise architecture as archaeology, logging decisions after the fact and building graveyards of past choices. James Wolstencroft proposes Decision-Centric Architecting, in which the system model becomes the project's navigation system and every decision, requirement, and piece of evidence stays findable, traceable, and connected from concept to operation. He calls the destination the Digital Continuum: rationale living in the same connected fabric as geometry, code, and test results. The conviction beneath it all is simple. Connectivity outranks form.
The framework rests on a four-part model: a Contextual Layer that holds intent, a Behavioural Layer that holds logic, a Realisation Layer that holds the physical design, and, surrounding and penetrating all three, the Decision Layer, the system's DNA and central memory. The other layers define the system in space. The Decision Layer defines it in time. And as generative AI begins to compose designs at machine speed, that layer becomes the thing that keeps a human able to understand, defend, and ultimately sign for what the machine produces.
The argument is grounded in forensic case studies (Ariane 5, the Boeing 737 MAX, the NHS National Programme for IT, Heathrow Terminal 5) and lands in practice: every chapter closes with a step-by-step playbook you can run on Monday morning, and a running example thread follows 2 contrasting systems from first context scan to delivery.
CTOs and engineering directors, chief and lead systems architects, programme and project managers, senior engineers, regulators, and anyone who has watched a beautiful diagram diverge from the thing being built. The vocabulary comes from systems engineering; the method applies anywhere decisions outrun evidence, in business and policy as much as hardware and code.
The Continuum is Book 1 of the Tekmerium series. A tekmerium is a house of proofs. This book builds its first wing.
Hi! I'm Libroamiko, your book advisor.
How can I help you?