Skip to content

Blog

Context engineering is the standardization you could never sell

Preparing context for AI agents forces the documentation and standardization architecture teams have pushed for years. The agent does not need it more than the organization did. It removes the resistance.

Written by

Context engineering

Published: 16 June 2026 Updated: 1 min read

Architecture teams have wanted the same things for two decades. Documented systems. Standardized patterns. Implicit knowledge written down. The undertaking was always sound, and it almost never got funded. “Process improvement” is a hard thing to sell when the roadmap is full.

Then the agents arrive, and the constraint flips.

An agent cannot read a senior developer’s memory

An agent works from what the context gives it: the architecture, the conventions, the decisions, the state of the system, written down where it can be retrieved. A team feeding a factory has no choice but to make the implicit explicit. The line will not run otherwise.

The context work was never overhead

So context-as-overhead is solved by stating the obvious: it was never overhead. From our experience: on one client’s line, developers now spend the larger share of their time, somewhere around two thirds, creating and maintaining context, and the smaller share implementing against it.

Read that as a tax and it looks alarming. It is not a tax. That two thirds is the documentation the organization needed for twenty years and never produced. The agent did not add the work. It made the work unavoidable.

The structure that comes out is the architecture

One client’s context is federated in layers, from the enterprise down to the repository, each layer owning its own rules and conventions. Building that for the agents is building the standardization the architecture team could never get prioritized.

What the budget actually bought

The budget tells the real story. One CIO signed off on a budget line labelled “AI training”. What it actually funded was context engineering practices across 220 developers. The documentation was the deliverable. The AI excitement was what finally got it approved.

The reframe for any engineering leader: stop selling standardization. Sell the AI factory, and the standardization arrives with it.

What would you finally get funded if it shipped under the agent’s name instead of its own?

Further reading

  1. Your coding agent is a free audit of your documentation Code generation is solved, so the constraint is now context. Every wrong answer an agent gives points at a standard the team knows and never wrote down. 2 min readShort post
  2. One AGENTS.md for four AI tools is harness debt A single context file behaves differently in every harness and every model. The four kinds of harness debt we keep finding in teams, and what a Dark Factory does instead. 2 min readShort post
  3. A study says context files hurt agents. It tested the wrong thing ETH Zurich found that auto-generated context files make agents worse. That shows auto-generation is useless, not context files. A useful context file records where the model fails your project. 2 min readShort post

All 16 posts on Context engineering

ClientsCase study: A large DIY retailer in Germany

Test the constraint in your system

The Factory Readiness Assessment connects this research to your value stream, your data, and the next decision.

Training on this topic: Agentic Engineering for Developers and QA
See the assessment

Want to check one team first? The self-check: twelve yes or no questions, three minutes, instant result, no account. Take the self-check