01 / The operating case
What changes in a real workflow?
Research children produce separate vendor suggestions and a coordinator combines them into a purchase order.
- 01Origin grant
- 02Parent agent
- 03Narrow child grant
- 04Action boundary
02 / Decision contract
What the executor must check
Preserve source and task scope of each contribution; authorize the final purchase independently against payee, amount and policy.
03 / Failure and evidence
What goes wrong, and what can be proven?
Several harmless recommendations are treated as approval for a harmful aggregate effect.
Contributing task IDs, final proposal, approver, decision and purchase result.
04 / Canonical scope
Why this reference stands alone
Fan-out addresses parallel spending; convergence addresses recombination into one effect.
Technical artifact
Recombination is a new action
research child A: vendor X costs USD 8,000 research child B: vendor Y costs USD 9,000 coordinator proposes purchase order USD 17,000 no child output is a purchase approval final order needs separate authority
Run the denial test
Make each child recommendation individually allowed, then submit their combined purchase through the coordinator. Reject when the aggregate exceeds the procurement grant.
Primary references