Five teams in one company are each building a multi-step agent. Every team has separately written its own tool-call loop, retry handling, state passing and tracing, and a platform review finds the five implementations diverge in how they resume an interrupted run. The platform group must give all five a common orchestration substrate with shared tracing, without prescribing the business logic of any one agent. Which approach fits that requirement?
- AAsk each team to copy the loop, retry and tracing code from whichever of the five implementations the review judged the most complete, then maintain that copy inside its own service.
- BHave the platform group write a company system prompt describing the required loop, retry and resume behaviour, and require every team to include that prompt block in its agent's instructions.
- CAdd a coordinating agent above the five agents that receives each request, decides which team's agent should handle it, and supervises that agent through to completion on every single run.
- DStandardise on an established agentic abstraction framework such as Strands, LangGraph or PydanticAI, so the loop, state passing and tracing are shared while each team writes only its own steps and tools. Correct
Why A is wrong: Tempting because it spreads the best current implementation quickly, but five copies drift the moment one team patches its own, which reproduces the divergence the review was called in to fix.
Why B is wrong: Tempting because a shared prompt is quick to distribute, but orchestration and resumption are properties of the code that drives the loop, so a prompt cannot make an interrupted run resume consistently.
Why C is wrong: Tempting because coordination sounds like the shared layer, but routing between five unrelated agents is not the duplicated concern, and it buys a supervisory hop the requirement does not ask for.
Why D is correct: Correct, because these frameworks exist to supply the orchestration layer being duplicated, giving one shared substrate with common tracing while leaving each agent's business logic to its own team.