Flowchart · Agent reasoning under /build-flow

How the system generates a flow

From JTBD + persona contracts through idiomatic tokens and catalog resolution into connected screens — with one hard halt (token gap) and one soft path (provisional components).

Flow generation reasoning flowchart Top-down flowchart: load contracts, pick JTBD and persona, per-stage catalog check, compose or provisionalize, bind tokens with halt on gap, then trace-flow and register in FLOWS. YES · use NO GAP · HALT OK /build-flow start Load contracts personas · DESIGN_SPEC · gate Select JTBD + persona lifecycle span owned For each stage / surface profile · fidelity · 3-pane layout In catalog & on disk? Provisional + ledger SPECIFIED / PROPOSED compose-surface + bind-tokens anti-dashboard · Convoy voice Token covered? L2 → L1 via var() DEVIATION REQUEST halt · wait for human trace-flow → register FLOWS[] → ship route hand-off · profile switch · non-applicable path

Hard halt

Token / styling gap

bind-tokens cannot invent values. Missing color, type role, or data-viz spectrum → DEVIATION REQUEST, then stop until approval.

Soft path

Missing component

  • SPECIFIED-UNBUILT — compose against DESIGN_SPEC contract
  • PROPOSED-NEW — mark PROPOSED: name placeholder
  • Both append ds-ledger with flow-context + FACTORY-ID
Convoy · /build-flow reasoning diagram-design · flowchart · dark brand skin