Understand

Nine pages, in the order they build on each other. Read the first two and you can use Flow-Next; read the rest when a specific question comes up.

Why Flow-Next The measured problem: agent code quality decays under iteration, and better prompts do not fix it. Plus the verification gap and the thinking this system comes from.

The Pipeline The end-to-end walk. Every stage, what it hands over, and which gate fires where.

How work gets proven One system with one bias. In-loop verification, the six proof artifacts, and the two principles that hold them together.

Skipping and composing stages The flexibility doctrine: the default pipeline is a menu. What holds on every route, stated once.

Specs without waterfall The objection the most experienced person in the room raises, answered. The spec is a ratchet, not a gate.

What each layer costs Every optional layer priced: what it automates away, what it costs, when it earns its keep, and how to get the capability without the standing cost.

How it compounds Memory, glossary, decision records, and strategy improve as side effects of the work you already do.

Architecture & harnesses Skills own judgment, flowctl owns mechanics, and the same workflow runs on six host harnesses.

Concepts Spec, task, R-ID, handover object, re-anchoring, receipt, harness. The words the rest of the docs use precisely.