Brief #181
Context engineering is fragmenting into two competing philosophies: protocol-based standardization (MCP) versus demonstration-based specification (Skills/Codex). Practitioners are discovering that the infrastructure bottleneck isn't model capability—it's the gap between how humans demonstrate workflows and how AI systems preserve that context across sessions.
Demonstration Beats Documentation for Implicit Workflows
EXTENDS prompt-engineering — moves beyond static prompt templates to dynamic workflow capturePractitioners are replacing written documentation with recorded demonstrations for complex workflows because autoregressive models learn better from sequential action patterns than from text descriptions of implicit preferences. This inverts traditional knowledge capture: show the work, let the model extract the rules.
Demo-as-spec pattern: workflows with implicit preferences (expense reports, issue config) are captured via demonstration + semantic extraction rather than written documentation. Codex Skills use parameterization to make demos reusable.
Scientific method applied to agent workflows: hypothesis registration before action, structured result gathering. Workflow must be 'done once' to establish clear methodology, then agents can replicate.
Context management through explicit file curation and instruction clarity improves Claude Code effectiveness. Breaking tasks into clear subproblems with explicit roles (writing vs reviewing) mirrors demonstration-based structuring.
MCP Context Poisoning is the New Supply Chain Attack
As MCP servers become context bridges with tool execution privileges, they represent high-value attack surfaces. Compromising a single MCP server poisons every downstream agent's context, making server authentication and context validation critical infrastructure concerns.
Identifies MCP servers as trust boundaries: poisoned servers compromise entire context chains. Zero-trust architecture required with server identity verification, data source validation, least-privilege permissions, and context access auditing.
Multi-Agent Coherence Requires Central Knowledge, Not Just Orchestration
Teams deploying multi-agent systems are discovering that agent-to-agent communication alone creates context drift. Coherent output requires a central knowledge base that all agents read from and write to, plus supervisory reconciliation to prevent inconsistency compounding across iterations.
Pattern: central knowledge repository plus supervisory reconciliation layer. Agents maintain local context but global consistency requires centralized shared state and arbitration. Without it, agents drift into incoherence.
Session State Checkpointing is Framework Selection Criterion
Practitioners are choosing agent frameworks based on whether they checkpoint conversation state throughout sessions, not just on speed or model compatibility. The ability to preserve and resume context mid-conversation has become more valuable than execution speed.
LangGraph's key differentiator is checkpointing session state throughout conversations (persistence/context preservation) while CrewAI optimizes for speed. Framework selection now hinges on stateful controlled systems versus autonomous fast systems.
Context Accessibility Gap Blocks AI Adoption More Than Capability
Non-technical users avoid AI tools not because models lack capability, but because integrating AI into actual workflows requires developer-level setup. The human becomes the manual context bridge, doing copy-paste integration between AI and work tools. Distribution accessibility is the actual competitive moat.
Integration Tax Pattern: easier non-developer access to intelligence without context setup equals wider adoption. Every API key, config file, or developer requirement creates context accessibility barrier. AI isolated in tabs means intelligence resets each session.
Context Inference Mismatch When Multiple Problem Frames Available
When AI has access to multiple versions of context (public repo plus internal code, generic task plus domain-specific knowledge), it may select a different problem framing than the user intended. Managing what context is available matters as much as how you phrase requests.
Model had access to desktop app source code (not just public repo). Request interpreted as reverse engineering task rather than code review because additional context reframed the problem. Clarity requires clear problem scoping given available context.
Daily intelligence brief
Get these patterns in your inbox every morning — plus MCP access to query the concept graph directly.
Subscribe free →