CSE Roadmap

Core tier · about 4 hours · 12 parts

Part 9 of 12 · 2 min read

Mistakes that pick the wrong shape

Common mistakes, and what the example does not do.

Mistakes that pick the wrong shape

  • Choosing the shape from a framework's name rather than from the task's structure.
  • Using a router for tasks that need several domains.
  • No hop or round limit on handoffs, critics and group chats.
  • A critic with no measured detection rate.
  • Letting the orchestrator be a weak model, since it caps the whole system.
  • Counting only the number of agents, not the calls on the critical path.
  • Giving every agent the full history on every handoff, which grows the context at each hop.

What the example does not do

About this example What the example does not do
  • No models. Accuracies are assumptions; the example measures how shapes transform them.
  • No shared state, no tools, no failures of tools or networks. Those come in the next modules.
  • Independent critic draws. A real critic reviewing the same model's output has correlated errors, which makes it less useful than this model suggests.
  • No group chat. Conversation-driven shapes need a model of turn selection, which this module does not build.
  • Optional real-model experiment: label 100 real tickets by domain count, run the single agent, a router, an orchestrator and a handoff design on them, and record accuracy, calls and tokens.

Check yourself

A routing agent sends every ticket to one specialist. A ticket needs both billing and legal. What happens?

Show answer

It cannot be completed correctly: a route picks one specialist. With every ticket needing two domains, routing scored 0.00 against 0.49 for a single agent.

For the curious A critic is only as good as its detection

A critic that never rejects adds calls and changes nothing (accuracy stays 0.71). A critic that rejects 30 percent of correct answers and catches none of the wrong ones made accuracy fall to 0.65. Measure how often the critic catches real errors and how often it rejects good work before you pay for it.

What you will use daily at work

Practice What it looks like
A hop limit on handoffs Control can bounce between agents; a cap guarantees it stops.
Typed results from workers The orchestrator context grows with every brief and result.
Pick by task mix One domain per request suits a route; mixed requests need decomposition.