Skip to content

Blog

Your org chart is the context architecture

An agent asking a question routes through the same knowledge layers a new hire would. Federated context follows the org chart, with a neutral mediator for the deadlocks.

Written by

Organization and roles

Published: 7 July 2026 Updated: 2 min read

A new hire on day one does not know who owns what. So they ask, and the question routes. The global rule goes to the enterprise architect. The domain decision goes to the domain owner. The detail of how this service actually behaves goes to the team that runs it. No one designed that routing. It is just where the knowledge lives.

An agent asking a question routes the same way. And once you see that, the obvious move stops working.

One big context file does not scale

The obvious move is one big context file. Every rule, every convention, every decision, in one place the agent reads. It does not scale. The enterprise architect cannot keep a repository’s conventions current. The team cannot keep the enterprise rules straight. One file means one owner for knowledge that has many owners, and it goes stale the day it is written.

So the single context file is solved by not having one. The constraint is now routing: which layer answers which question, and who keeps that layer true.

Layers that follow the org chart

One mature client runs context in five federated layers: enterprise, domain, product line, product, repository. Each layer owns its own context, and the people who already own that knowledge maintain it. An agent’s question resolves at the layer that holds the answer. That is Conway’s Law, pointed at the agents. The context architecture mirrors the communication structure of the org, because it has to.

A mediator for when layers disagree

Which leaves one real question. What happens when two layers disagree?

One large engineering org answers it with a pattern worth stealing. A neutral mediator sits in the architecture guild and casts the tipping vote when a community deadlocks. The mediator gets no new authority. It is just a way to break a tie. I think an agent can play that mediator: a neutral architecture buddy that resolves a cross-layer conflict without anyone having to win the org-chart argument.

Layers from the org chart, a mediator for the deadlocks. That is federated context governance.

If you mapped your context to your org chart today, which layer has no owner?

Further reading

  1. When engineering speeds up, the bottleneck moves to product A workshop mapped a full SDLC against agents. Almost every step compressed, except deciding what to build next, and most organizations are not staffed for that shift. 1 min readShort post
  2. When the factory dispatches the work, the manager runs the line When the factory handles assignment and status, the engineering manager's job moves from dispatcher to line operator. Five responsibilities now define the role. 2 min readShort post
  3. Delegate, review, own: the operating model of AI-native teams A model lab's playbook for AI-native engineering teams repeats one pattern across seven SDLC phases. The hard part is the review, where the engineer decides which agent findings matter. 2 min readShort post

All 15 posts on Organization and roles

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 Engineering and Product Leaders
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