service-scoping

To find the correct service context in a monorepo, you need scoped context discovery that walks upward from a target file to locate the nearest AGENTS.md and service manifest while staying within the git worktree boundary. This prevents loading unrelated sibling project rules during file modification.

Service ownership detection identifies the owning service by locating supported manifests such as package.json, pyproject.toml, Cargo.toml, go.mod, or Dockerfile. It applies bounded filesystem traversal to validate local project context and avoid loading unrelated configuration from nested repositories.

Scoping technology stack discovery requires walking upward from your target file to find the nearest tech-stack.md and service manifest within the git worktree. This ensures only relevant technology information and service conventions apply to your code editing scenario.

Incorrect project configuration loads when filesystem traversal is unbounded. You need service scoping to validate local project context and restrict traversal to the git worktree boundary, preventing unrelated sibling project rules and manifests from applying to your target file.

Service scoping supports Python, Rust, and Go monorepos by detecting service ownership through pyproject.toml, Cargo.toml, and go.mod manifests. It applies to nested project structures requiring scoped AGENTS.md rules and technology stack discovery across these platforms.

You need bounded filesystem traversal for service context discovery when modifying files inside a large monorepo with nested repositories. It ensures you determine which service conventions apply without loading unrelated configuration from sibling projects outside the git worktree boundary.