Shared organizational context is the real limit

Teams run on shared context accreted by osmosis: being in the room, reading the same Slack, debugging the same outage. Agents cannot do osmosis. Whatever you fail to pack into the prompt, the files, or the instructions, they do not reliably have. The opportunity: agents are good at reading exhaust (PRs, issues, commits) to externalize the implicit knowledge an organization never writes down.

The opportunity is asymmetric. Agents are unreasonably good at reading exhaust: every PR comment, every closed issue, every commit message, every stale design doc. They can extract patterns and decisions that nobody bothered to write down because nobody was going to read them. If you build the loop (agents that produce context for agents that consume it), the organization gains a written substrate it would never have produced on its own. The constraint that was rate-limiting becomes a thing you can manufacture.