Writing Flows

Document how one scenario behaves at runtime as a Flow file under flows/. A Flow makes the order of operations and the branching visible at a glance — the thing specs, tasks, and ADRs can't show.

Hard Rules

• Template-driven. Every Flow follows templates/flow-template.md exactly — four sections, no freestyle.
• One Flow = one scenario. A request spanning multiple scenarios becomes multiple Flow files.
• Code is the source of truth. When code exists, read it before drawing. Never draw from assumption what can be verified by exploration.
• Never auto-modify existing Flows. Propose the diff, wait for confirmation.
• No derived index files. Never create flows/README.md or flows/INDEX.md — the directory listing is the index.

Directory Rules

• Flow 루트를 먼저 정한다. 사용자 전역 규칙(work-routing 류)이 이 repo 의 2급 문서를 외부 doc-root 로 보내면 Flow 루트는 <doc-root>/<repo-name>/flows/ 이고, 아니면 프로젝트 루트의 flows/ 다. 아래 규칙(topic 디렉토리, NN- 접두어, 인덱스 금지)은 정해진 루트를 기준으로 적용한다.
• Flows live in flows/<topic>/NN-name.md under that root — a closed-root dir; the directory-structure SSOT is check-doc-structure/golden_manifest.py (shared with writing-specs, writing-tasks, scaffold-new-app, reconcile-docs). Topic = coherent feature/domain (auth, checkout), the same axis as ADR-0001 — never phase numbers.
• Match the topic against existing flows/*/ directories before creating a new one.
• NN is a 2-digit index within the topic, starting 01. Filenames are lowercase-with-hyphens.