cross-repo-orchestration

To synchronize changes across multiple git repositories without drift, use a git-mediated coordination workflow with feature branches and PRs. You export upstream artefacts, apply them in each downstream repo, run CI verification, and open PRs referencing the upstream change.

The best way to propagate harness policy changes across ten or more repos is specification-mediated orchestration. It uses manifest-based contracts and a platform orchestrator for automated propagation, portfolio health aggregation, and policy inheritance.

Manifest-based export and import for cross-repo synchronization works by declaring exported artefacts in an upstream manifest contract. Downstream repos apply these declared artefacts on feature branches, ensuring synchronization satisfies the contract before opening PRs.

Yes, you can coordinate cross-repo changes for a small topology of two to five repositories. It uses a step-by-step git-mediated workflow to sync exported artefacts from an upstream repo into downstream repos using feature branches, PRs, and CI checks.

You do not need a platform orchestrator to sync skills and templates across a few plugin repos. Git-mediated coordination handles small topologies using feature branches and PRs, while specification-mediated orchestration is reserved for platform-level propagation across ten or more repos.

Cross-repo orchestration for aggregating enforcement and mutation testing health is a specification-mediated process. It uses a platform orchestrator and manifest-based contracts to automatically propagate policies and aggregate portfolio health reporting across an organization's repositories.