Domain 1: Agents & workflows

An observability platform team runs an orchestrator agent that breaks a codebase-wide dependency upgrade into per-service subtasks. The dependency-pinning policy was agreed in the orchestrator's own conversation, yet the subagents keep choosing versions that violate it. What is the cause, and the fix?