• The whole-repo agent is a cross-context bulldozer. Given free rein, the agent's incentive is uniformity. Uniformity across bounded contexts is not cleanup; it is the collapse of the domain distinctions the contexts existed to preserve.
• The same word means two things and that is correct. Customer in Billing is a party with a payment method. Customer in Support is a party with an issue history. Same word, two concepts, two owners. Merging them is a domain regression.
• The agent's scope should be a context, not a repository. One context at a time, with its own vocabulary, its own builders, its own tests, its own bounded surface. The scope is the constraint that keeps the agent from doing damage across the seam.
• Cross-context changes belong to a human. A rename, a shared concept, a promoted invariant: those are architecture decisions. The agent can propose them. The human owns the decision to unify or keep separate.

Read the argument: The Bounded Context Is the Scope the Agent Actually Needs