# Understand

Source: https://flow-next.dev/understand/

Why the pipeline is shaped this way - the problem it answers, how work gets proven, how the route is chosen, and the vocabulary the rest of the docs use.

Choose the question you want answered. For a hands-on start, use [Your First 30 Minutes](https://flow-next.dev/first-30-minutes/).

[Why Flow-Next ](https://flow-next.dev/understand/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 ](https://flow-next.dev/understand/pipeline/)The end-to-end walk. Every stage, what it hands over, and which gate fires where.

[How work gets proven ](https://flow-next.dev/understand/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 ](https://flow-next.dev/understand/compose-the-pipeline/)The flexibility doctrine: the default pipeline is a menu. What holds on every route, stated once.

[Flow and the road ahead ](https://flow-next.dev/understand/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 ](https://flow-next.dev/understand/explore-first/)Use a prototype, reproduction, or experiment to settle a question, then capture the answer in the spec.

[How it compounds ](https://flow-next.dev/understand/how-it-compounds/)Memory, glossary, decision records, and strategy improve as side effects of the work you already do.

[Architecture & harnesses ](https://flow-next.dev/understand/architecture/)Skills own judgment, flowctl owns mechanics, and the same workflow runs on six host harnesses.

[Concepts ](https://flow-next.dev/understand/concepts/)Spec, task, R-ID, handover object, re-anchoring, receipt, harness. The words the rest of the docs use precisely.