Data residency: pin an agent's inference geography

Why it matters

A residency requirement belongs in the system that enforces it, not in a proxy or a runbook. This exercise puts it on the agent definition and shows how far that guarantee reaches.

What to practise

In the Claude Managed Agents beta, set inference_geo: "us" inside the agent’s model config and read the pin back from session.agent.model. Learn how the workspace’s allowed_inference_geos and default_inference_geo bound it. The pin is checked when the agent is saved, when a session starts and on every turn, so narrowing the policy stops a running session. Watch two traps: agents.update replaces model as a whole, so omitting the geography clears the pin, and agent_with_overrides can change it for one session.

How it fits

This is the inference-routing control of 5.4.5 and the inference_geo: "us" setting that 5.4.4 relies on. The pin governs only where tokens are processed, not where data is stored, which is the separate workspace_geo setting. Map the pin to its obligation and evidence as 5.4.1 asks.