Manage a monorepo through explicit contracts

Accept a repository and a concrete outcome. Inspect before prescribing a layout or tool. A monorepo shares a Git history; it does not require one language, one dependency version, one build system, or synchronized releases.

Use only the phases relevant to the request. Investigation permits inspection; implementation requires edit authorization. Installing dependencies, migrating tools, importing repositories, publishing packages, and deploying services must fit the explicitly authorized scope.

1. Discover the workspace and requested change