Flows

Flow class declares two @start methods. Operator calls flow.kickoff() expecting one to run.

Multiple @start methods are valid — all fire as parallel entry points. If you want one entry, declare a single @start (or parameterize selection). Verify the actual entry set by inspecting the Flow class. Document which entries exist so kickoff behavior is predictable.

Flow has @listen(method_a) on method_b. method_a returns a value. method_b expects to receive method_a's return.

@listen(target) subscribes method_b to fire when target completes; the return value of target is passed as method_b's first argument. Verify by inspecting the method's signature and the value received. To listen on multiple targets, use the documented or_ / and_ combinators.

@router method returns 'maybe' but no @listen('maybe') is registered.

Default behavior under unmatched @router label is [REQUIRES-VERIFICATION] — the operator should not rely on a silent skip. Either ensure every router label has a listener, add a catch-all listener, or assert at flow-construction time that the router's return set matches the listener set.