Module 09 Activity
Scenario
Someone has proposed splitting your graph into a supervisor and three workers. This activity is the cost-benefit case, honestly made.
What you build
A written decision on whether to add a second agent, and - if yes - a handoff contract, deliberate reducers and a hop ceiling.
Steps
- State what the second agent would do that the first cannot. If the answer is 'the prompt got long', stop and say so.
- Price both designs relative to a single agent, using the table in Unit 03 as a model.
- If proceeding, define the handoff as an explicit allowlist and name what is withheld and why - separating secrets, quotable internal text, and bulk.
- Decide the reducer for every shared field. Any field two agents write needs a deliberate choice.
- Add a hop counter with a ceiling, and record which agent wrote each field.
- Work through the five failure modes in Unit 04 and say how each is addressed or accepted.
Evidence to hand in
- The decision, with what the second agent does that the first cannot.
- The relative cost comparison.
- The handoff allowlist with withheld fields and reasons.
- The reducer choice per shared field.
- The five failure modes with a mitigation or an acceptance each.
Review checklist
- The decision would survive a colleague asking 'could one agent with two tools do this?'
- The handoff is an allowlist, not a prompt instruction.
- Every shared field has a deliberate reducer.
- A hop ceiling exists.
- Per-field attribution is recorded, so a wrong claim has an owner.
