decision
Created: 2026-04-29
Updated: 2026-04-29

Sources:

crew-referencesubagent-pattern
decisionsLast updated 2026-04-29

2026-04-29 — Routing Rule

Established the critical routing rule: if Sofian asks about something an agent already built, re-delegate to that agent. Don't try to fix it yourself.

Summary

Established the critical routing rule: if Sofian asks about something an agent already built, re-delegate to that agent. Don't try to fix it yourself.

The Rule

> If Sofian asks about something related to a task already executed by an agent → DELEGATE TO THAT AGENT.

Examples

Issue
Delegate To
Why
"Mission Control tasks don't change state"
Blinky
He built the task system
"Inky's brief is outdated"
Inky
He wrote the brief
"Backup script is broken"
Blinky
He wrote the script
"Watchlist tracks wrong topic"
Inky
He maintains the watchlist

Rationale

1. Context preservation — The builder has full context of design decisions

2. Efficiency — No need to re-read and understand someone else's code

3. Accountability — One owner per component

4. Learning — Agents improve their own work over time

Exceptions

  • Emergency fixes when the builder agent is stuck or unavailable
  • Trivial one-line changes with obvious correctness
  • Kamon's own work (he fixes his own stuff)

Relationships

  • clyde — CEO enforces this rule during task routing
  • subagent-pattern — Native subagents make re-delegation fast and cheap
  • crew-coordination — File-based coordination preserves builder context