AT-301b · Module 2

Role Evolution

4 min read

Roles are not static. The team that launched on January 1 with 11 agents operates differently at 20. Roles must evolve as the system scales — what was one agent's job splits into two; what was a manual handoff becomes an automated pipeline; what was a solo task becomes a collaboration pattern.

The evolution methodology has three triggers. Volume trigger: when task volume exceeds an agent's throughput by 23% or more for two consecutive weeks, the role needs splitting. Complexity trigger: when an agent's error rate exceeds baseline by 15%, the role has grown beyond its design scope. Integration trigger: when two agents spend more than 30% of their cycles on handoff coordination, their roles need restructuring to reduce the interface surface.