Repository context for coding agents

Question

What minimum architectural context does a coding agent need to make changes consistent with an existing system?

Background

The question is where context stops being useful and starts becoming noisy for coding agents.

I want to identify a minimal set of architectural signals that consistently improves change quality.

The output should be practical enough for teams to maintain as systems evolve.