Brief #222
Practitioners discovered context persistence is now the primary bottleneck, not model capability. They're building shared memory layers, feedback loops, and explicit rationale documentation because intelligence compounds when context survives across sessions—and dies when it doesn't.
Agentic Feedback Loops Compound 180× Production Gains
EXTENDS multi-agent-orchestration — baseline shows coordination patterns, this reveals feedback loops as the mechanism for intelligence compoundingPractitioners achieving production-scale results by feeding agent failures back as context for next iteration, not by upgrading models. 180 merged PRs from daily maintenance loops prove intelligence compounds when context preserves what failed yesterday.
180 merged PRs across platforms from Claude running daily routines with iterative feedback—'tune its routines so it's better the next day' demonstrates context compounding
Shared persistent memory layer enables agents to 'pick up where we left off' and critique each other's work across sessions
Named sessions with directed messaging preserve context across specialized agents working on shared problem (orders endpoint migration)
Context Decay Solved by Inline Rationale Documentation
CLAUDE.md files grow unbounded because deletion requires understanding intent, not mechanism. Practitioners discovered documenting 'why this rule exists' inline prevents context decay and enables confident pruning.
Rules aren't deleted because deletion risk exceeds cost of keeping them—people forget why rules exist. Solution: document rationale inline so next person can confidently modify/remove
Custom Domain Context Depth Defeats Generic Factories
Nine practitioner teams built custom agent orchestration instead of adopting off-the-shelf solutions because generic factories can't capture company-specific intent, culture, or codebase patterns. Context depth, not model capability, determines success.
Nine custom factories in Swamp discord because aligning intent to AI output requires domain-specific context (company values, codebase structure, development philosophy)
MCP Servers as Local Context Standardization Layer
Practitioners converting heterogeneous tools to local MCP servers to give agents unified access, proving context engineering infrastructure can be self-hosted and doesn't require cloud dependencies.
Converted Spotify, Stripe, Anthropic, Twitter, Linear, Notion to local MCP servers with executor.sh routing all agent requests through standardized interfaces
Test-Time Training Enables Within-Session Intelligence Compounding
Models can improve on novel problems by adapting weights during inference via gradient updates at test time, shifting bottleneck from training data coverage to real-time context utilization.
TTT enables models to generalize on unseen problems by updating weights during inference based on test-time context—compounds intelligence within session without retraining
Plan-as-Context Bridges Agent Capability Gaps
When agents hit tool boundary limitations (UI navigation, non-automatable steps), generating structured plans as explicit context artifacts enables humans or specialized tools to execute, preserving intelligence across the gap.
Created structured plan for Computer Use plugin to automate Google Cloud Console setup steps that fall outside agent terminal capabilities—plan preserves intent across tool boundary
Verification Loop Bottleneck Determines Delegation Success
Task delegation effectiveness depends on output verifiability, not model capability. Tasks where AI can self-check (visual QA, code execution, self-review) become trivial; judgment-requiring tasks remain human-bottlenecked.
Cursor team member found tasks with easy verification (visual check, code execution) became delegatable; judgment tasks remained bottlenecked—problem isn't capability but verifiability
Daily intelligence brief
Get these patterns in your inbox every morning — plus MCP access to query the concept graph directly.
Subscribe free →