product-flow
Product Flow
A concept says how the product fundamentally works; flows say what happens at 2:47pm when the estimator is halfway through, the insurer's data hasn't synced, and the phone rings. Professional software is mostly edge: the happy path is a minority of real sessions, and interruption is the norm. Agent-built software fails here more than anywhere — it ships the demo path.
Part of the product-define suite. Read design/concepts.md (selected), model.md (states, permissions, reversibility); write design/flows.md using assets/state-ledger.md; update context.md open questions. Gate 2 runs against this file.
Quick Reference
| Topic | File | Read when |
|---|---|---|
| State ledger + resumption shell | assets/state-ledger.md | Every core flow |
| Persist / return / decay patterns | assets/interruption.md | Resumption section |
| Fix / retry / report + empty + safeguards | assets/error-policy.md | Errors and empty states |
Core Principles
-
Map flows as chains:
entry point → action → system response → next action → completion. -
Mandatory state ledger — full rows or N/A with reason per assets/state-ledger.md.