# Monorepo operating modes

> Place shared and project-specific Verchestra artifacts safely in complex workspaces.

Source: https://accd.github.io/verchestra/docs/workflows/monorepo-operating-modes/
Content digest: `sha256:4f56cefad84980d5f964a459ec2ad605cbbeb26ef88d1aed4a43d7e3b1207e65`

Verchestra supports three placement modes.

## Colocated

Shared orchestration lives at the monorepo root; project-specific artifacts live inside each tracked project.

## Centralized

All AI-delivery artifacts stay under the root workspace and refer to project directories by stable identifiers. Use this when child repositories cannot contain AI files.

## Nested-aware

The root inventory may include ignored child directories that are separate GitLab or GitHub repositories. Verchestra records repository boundaries and never assumes that the outer repository owns their files.

A reconciliation command can discover new projects, preserve existing IDs, and generate only missing artifacts. Placement is policy, so a refresh cannot silently move tracked files between modes.