Brief #76
Context engineering is fragmenting into two incompatible paradigms: centralized supervisory control (optimizing for simplicity) versus distributed collaborative intelligence (optimizing for emergence). The critical question isn't which framework to choose, but whether your architecture preserves or destroys intelligence at agent handoff boundaries.
Agent Evolution Systems Outperform Static Human Design
Collaborative agent evolution—where agents share experiences and reuse innovations—produces superior outcomes to individually-engineered agents. The breakthrough isn't better models, it's architectural: shared context between agent instances compounds intelligence while isolated evolution resets it.
Research demonstrates that agents sharing experiences and innovations collectively outperform static architectures. The mechanism is context preservation: when agents can access what other agents learned, the system compounds knowledge rather than each agent rediscovering solutions independently.
Amazon's three-tier evaluation framework reveals that multi-agent success depends on measuring coordination efficiency and handoff accuracy—not just individual performance. Context degradation at handoff points is the failure mode, validating that preservation mechanisms matter more than agent capabilities.
Planner-executor-verifier architecture with explicit verification loops shows that agentic systems fail not from model limitations but from how information flows through reasoning stages. The verifier exists to catch context drift—evidence that architecture determines whether intelligence compounds or degrades.
Supervisory Control Trading Emergence for Simplicity
The LangGraph Supervisor pattern centralizes all agent coordination through a single orchestrator, reducing system complexity but creating a context bottleneck. This architectural choice reveals an implicit assumption: that coordination complexity is harder to manage than supervisor cognitive load.
The pattern forces all communication through a supervisor to reduce coordination complexity. This centralizes context routing but means the supervisor must maintain knowledge about all worker capabilities, tasks, and results—a potential single point of context failure.
MCP Elicitation Prevents Context Loss Through Clarification Loops
The MCP elicitation pattern enables tools to signal missing information and gather context without breaking conversation flow. This shifts from 'fail on incomplete input' to 'request clarification and resume'—preserving intent across turns rather than resetting.
The elicitation request enables 'tool requests missing info → client gathers context → resumes work' loops. This preserves the context chain and prevents 'lost context' resets that force users to rephrase entire requests.