Skip to content
Daniel KliewerThe book
Computational Sovereignty — hardcover front cover
Book spineBook back cover

The book · Hardcover · $88

Computational Sovereignty

Building Local-First AI Systems

Most AI engineering in 2024–2026 was integration work: call someone else's model, parse the output, hope the weights don't change overnight. This book is about the other discipline — building the whole stack on machines you own, where every behavior is reproducible and every number is yours.

It starts by pricing the cloud as a liability and ends with a practice for shipping sovereign software. In between: 24 chapters of models, retrieval, graphs, agents, personas, and verification — each one measured, each one runnable.

The argument

Eight parts, one thesis

Each part makes a single claim and then spends three chapters proving it with working systems.

PART I — WHY SOVEREIGNTY

The cloud is a priced liability, and the stack you need to replace it is five layers tall.

PART II — INFERENCE YOU CONTROL

Tokens, sampling, and model selection are engineering decisions with measurable consequences — treat them that way.

PART III — MEMORY THAT ISN'T A PROMPT

Retrieval is only as honest as its evaluation. Build the gold set first, then believe your numbers.

PART IV — KNOWLEDGE GRAPHS

Reason once, compile the result. A knowledge graph is a decision you made ahead of time.

PART V — AGENTS THAT OBEY

An agent without a state machine is a rumor with tool access. Govern the transitions or inherit the incidents.

PART VI — PERSONAS AND ROUTING

Personalities can be quantified, and routing between specialists beats one generalist — measured, not asserted.

PART VII — VERIFICATION DISCIPLINE

Refusal is a feature, contradiction is data, and benchmarks are frozen or they are fiction.

PART VIII — PRIVACY, SECURITY, SHIPPING

Air-gapped systems have a security model, shipping has a checklist, and the practice compounds.

Table of contents

Twenty-four chapters, eight parts.

Each part builds on the one before it. Every chapter ends with something running on your own machine.

24
Chapters
214
Pages
~46,000
Words
8
Parts

I — Why Sovereignty

01The Cloud Is a Liability
02The Sovereignty Stack
03Your First Local Model

II — Inference You Control

04Tokens, Context, and Sampling
05Choosing Models Like an Engineer
06Serving Models Locally

III — Memory That Isn't a Prompt

07Embeddings and Vector Search
08Building Local RAG
09Evaluating Retrieval Honestly

IV — Knowledge Graphs

10From Documents to Graphs
11GraphRAG in Practice
12Compile-Time Intelligence

V — Agents That Obey

13Tool Use, Locally
14State Machines Over Vibes
15The Auditor Pattern

VI — Personas and Routing

16Quantified Personas
17Dynamic Routing (MoE-style)
18Persona Systems in Production

VII — Verification Discipline

19The Refusal Discipline
20Contradiction Detection at Scale
21Gold Sets and Frozen Benchmarks

VIII — Privacy, Security, Shipping

22The Local-First Security Model
23Shipping Sovereign Software
24The Sovereign Practice

Specifications

The physical facts

Title
Computational Sovereignty: Building Local-First AI Systems
Format
Hardcover · 6×9 in
Pages
214
Chapters
24 chapters · 8 parts
Words
~46,000
Price
$88
Author
Daniel Kliewer

Questions

Asked and answered

Do I need a GPU?

For the serious chapters, yes — 24GB of VRAM or a Mac with unified memory is the entry ticket, and chapter 1 says so up front. The early chapters run fine on a CPU so you can start before the hardware arrives.

Is this just anti-cloud ideology?

No. Chapter 1 lists exactly when the cloud is the right call — frontier capability, tiny bursty workloads, no operational capacity — and prices the rest as a liability. The position is default-local, not never-cloud.

What skill level does it assume?

Comfort in a terminal, working Python, and no fear of a config file. It does not assume ML training experience — it does assume you have shipped software and been paged for it.

How is this different from the blog?

The 198 research posts are the laboratory: experiments, measurements, dead ends. The book is the compiled artifact — the reasoning done once, organized so you don't have to rediscover it across three years of archives.

Ebook or paperback?

Hardcover only. 214 pages, 6×9 in, built to live on a desk next to the machine it describes. There is no DRM to strip because there is no DRM.

When does it ship?

The manuscript is complete and reviewed — 24 chapters, ~46,000 words. The hardcover is live on Amazon now, so the button below is the real listing, not a placeholder.

24 chapters · ~46,000 words · $88

Own every layer.

The cloud will still be there when you need it. After this book, you'll know exactly what each API call costs you — and you'll have the machine to replace it.

Buy the hardcover — $88 ↗

Or read chapter 1 free first →