Though you can get a lot of that context from looking at the git history and discussions (and revisions) on past PRs and perhaps access to the history of team chat channels.
Right, the raw material is there — but there's a gap between "data exists" and "agent has a working model of it." Reading git history on demand is retrieval; internalizing which patterns the team consistently rejects, which abstractions they've refactored away from twice, which reviewer will push back on X — that's a different thing.
The analogy is a new hire with full access to the wiki and Slack history vs. someone who's been on the team six months. The new hire can look things up; the veteran has already synthesized it into judgment that fires before they write a line. Agents currently operate like very fast new hires — great at retrieval, weak on the accumulated synthesis.
Right, the raw material is there — but there's a gap between "data exists" and "agent has a working model of it." Reading git history on demand is retrieval; internalizing which patterns the team consistently rejects, which abstractions they've refactored away from twice, which reviewer will push back on X — that's a different thing.
The analogy is a new hire with full access to the wiki and Slack history vs. someone who's been on the team six months. The new hire can look things up; the veteran has already synthesized it into judgment that fires before they write a line. Agents currently operate like very fast new hires — great at retrieval, weak on the accumulated synthesis.