Before a pilot begins, the architect must understand the workflows being enabled, the associated security boundaries, and the correct ownership of each configuration decision. Option D establishes this foundation. Organization-wide, non-overridable controls belong in managed configuration, whereas repository-specific MCP servers, shared permissions, and team subagents generally belong in project scope.
Option A then converts those decisions into an initial project baseline that the pilot group can use. The baseline should identify approved MCP endpoints, minimum permission rules, denied operations, subagent responsibilities, configuration ownership, and observable success criteria. Anthropic distinguishes managed, user, project, and local scopes according to who they affect and whether they are shared with the team. Claude Code Configuration Scopes
Options B and C are broad-rollout activities and should not occur before pilot evidence is available. Option E is explicitly post-pilot: findings must first be collected before the configuration can be iterated and stabilized.
The correct lifecycle is discovery, boundary definition, baseline design, limited pilot, evidence review, baseline refinement, documentation and training, followed by controlled expansion with a support and rollback process.
Study Guide references/topics: Claude Code rollout planning; scope ownership; MCP baselines; permission design; pilot strategy; operational enablement.
===============
