Graphs, Nodes, and Transitions

A workflow can be represented as a graph:

START
  |
  v
Verify customer ---- not verified ---> Ask for verification
  |
 verified
  v
Identify transaction ---- missing ---> Ask for transaction details
  |
 identified
  v
Determine dispute reason
  |
  v
Check policy and eligibility
  |
  v
Request required confirmation
  |
 confirmed
  v
Execute permitted action
  |
  v
Record result and respond
  |
  v
 END

Each node has a defined responsibility, and each transition has an explicit condition. This makes the process easier to inspect and test than an unconstrained conversation.

A node might collect information, evaluate a rule, invoke an approved connector, or generate a response from a controlled template. The graph decides when that node is allowed to run.