Skip to main content
Progression

Analytics

Three instruments for reading the book as a system, not a sequence

A book about the next ten years generates its own data: which chapters lean on which, what must be built before what, and which of its dated forecasts have already come true. These three instruments read that data back. Each one is built automatically from the text, so none of them can drift from what the chapters actually say.

The Atlas

The book as a constellation. Every chapter is a node, every cross-reference a thread, and the whole mesh hangs in three dimensions — the load-bearing arguments sink to the middle of the cluster, the self-contained ones drift to its edge. A complete text index of every relationship sits underneath for anyone who prefers a list to a galaxy.

Citation graph · every chapter’s dependencies, both directions

The Tree

What must be built before what. The wild futures in the forecasts are not free-floating — each stands on earlier, duller advances, and several of the wildest share the same few load-bearing ancestors. The Tree wires every advance into a dependency graph: pin any one of them to light its ancestry and everything it unlocks, and the keystones — the advances that open the most doors — are marked.

Dependency graph · four eras, from achieved to wild

The Ledger

Every dated forecast in the book, extracted automatically and graded as events unfold — achieved, partly true, not yet, or refuted. A book that claims the next decade should expect to be scored on it; this is the scorecard, and it is the one page that keeps changing after the book is done.

Forecast register · updated as the world catches up