Understand

Choose the question you want answered. For a hands-on start, use Your First 30 Minutes.

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.

Compose the pipeline The flexibility doctrine: the default pipeline is a menu. What holds on every route, stated once.

Flow and the road ahead Why Flow chooses the route for you, what the attended conductor refuses to do, and the one driver that now serves attended and unattended work.

Explore first, then capture Use a prototype, reproduction, or experiment to settle a question, then capture the answer in the spec.

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.