Run graph
Definition topology plus overlay — taken exits, fork arms, wait nodes.
The run graph is the catalog IR snapshotted at start, overlaid with per-node status. It is not the designer, and it is not Camel choice.
Nodes and edges
Nodes: call, wait, fork, join, switch, end.
| Edge | Shape | Rule |
|---|---|---|
| sequence | solid | Linear next |
| fork | split → lane | AND: every arm must become terminal |
| join | lanes → bar | Open until every arm is success, skip, or failed-isolated |
| switch / wait XOR | labeled exclusive | Exactly one taken; others ghost |
While listening, outbound XOR edges are dashed. After a decision, the taken edge is solid and the rest ghost. Labels come from the catalog (approve, reject, timeout).
Situation bar
- Waiting + operator wait → Review / Send data from
prompt.kind - Fork: “Matrix running” chip next to Review
- Hop inspector does not mention Temporal. A wait node is not a Camel route.
Isolated failure
On contact-lead, Matrix HTTP 500 records the arm failed-isolated. The Review wait continues. Join waits until every arm is terminal.
If this fails
| Symptom | Cause |
|---|---|
| Graph looks empty | Job run — jobs have no wait graph |
| Both approve and reject look taken | Overlay bug; only one XOR edge may be taken |
| Cannot restart mid-fork | v1 restart is linear arm only |
Next: Waiting and review