workspace-maintenance

Workspace consistency across local repositories is maintained by applying a documented governance workflow that enforces shared conventions for docs, scripts, and caches. This prevents drift and cross-repo dependency contamination during setup and upgrades.

Workspace drift happens when documentation, scripts, caches, and repo conventions become misaligned across local repositories. It creates unpredictable environments, requiring governance workflows and automation to realign shared resources and maintain stability.

Prevent cross-repo dependency contamination by enforcing a documented workflow with guardrails and utilizing optional resource directories like scripts/, references/, and assets/. This structure guides automation while preserving strict repository locality and preventing shared tooling conflicts.

Governing workspace-level conventions is best achieved by running a default maintenance workflow that verifies alignment and applies local adjustments. This governs shared caches and tooling to avoid duplication and misalignment across repos.

Workspace governance works for adding new repositories and refreshing caches by applying a documented workflow with guardrails. This ensures onboarding and maintenance scenarios preserve locality, keep environments aligned, and prevent drift.

Use a workspace maintenance workflow when coordinating many local repos, handling shared caches, or adjusting tooling during upgrades. It enforces repo-level conventions to keep the environment predictable for agents and users.