How they connect
The four layers feed into each other.
The methodology is not four parallel ideas. It is four sequential questions, each one answered by the layer below it.
The worldview defines the problem space. After They Say Yes argues that client behavior changed permanently because of AI. The post-AI client arrives pre-educated, benchmarks against AI in real time, has a shorter patience window, and expects hybrid AI-and-human delivery. That is the macro frame. Without it, the rest of the methodology reads like a series of disconnected tactics.
The diagnostic translates the worldview into structure. The Three Blocks identifies the three predictable points where the post-AI client now breaks programs designed for the pre-AI client. The Momentum Block in the first 96 hours. The Founder Block compounding through the middle of the program. The Upgrade Block hiding at the end. The diagnostic is not generic; each block is the operational consequence of one or more of the five behaviors named in the manifesto.
The metric makes the diagnostic measurable. The Client Flow Score takes what Three Blocks describes structurally and produces a number that surfaces drift in specific clients before it becomes churn. Three pillars (Execution, Direction, Belief) map to the underlying mechanisms. Five states (Flowing through Crisis) map to specific intervention pathways. Where Three Blocks is the map, the Client Flow Score is the GPS.
The system makes the metric operational. The Retention Engine is the integrated delivery architecture - Activation Path, 3-Layer Delivery Rhythm, Natural Upgrade Architecture - designed to address all three Blocks simultaneously. FlowOS is the platform that runs this engine in production. AI holds the context (BusinessDNA, Flowie, the Pulse loop). The founder shows up for the conversations that require real read. Methodology becomes infrastructure.
Each layer compounds with the one above it. You can read the manifesto and learn nothing operational. You can install Three Blocks without the manifesto and lose the conviction that makes the framework spread inside a team. You can implement the Client Flow Score without the diagnostic and end up with a number nobody knows how to act on. You can deploy FlowOS without the metric and end up with software that runs but cannot tell you whether your delivery is actually working.
Read top to bottom, the methodology answers four questions: What changed? Where is it breaking? Who is breaking right now? What do I install to fix it?
That is the map.