From 8282a2ba9b31b3ecfd349e361ce7afcda4ffa333 Mon Sep 17 00:00:00 2001 From: Joshua Temple Date: Thu, 18 Jun 2026 14:35:39 -0400 Subject: [PATCH] docs: clarify external scope in configuration reference Signed-off-by: Joshua Temple --- docs/src/content/docs/configuration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/src/content/docs/configuration.md b/docs/src/content/docs/configuration.md index 08877ca9..891c354f 100644 --- a/docs/src/content/docs/configuration.md +++ b/docs/src/content/docs/configuration.md @@ -295,7 +295,9 @@ The framework only carries metadata. The publish workflow performs the registry ### external Section (Multi-Repo Orchestration) -For repositories that coordinate deployments owned by satellite repos: +For repositories that coordinate deployments owned by satellite repos. + +`external:` is designed for the **satellite/sibling-repo artifact coordination** pattern: a separate repo (the satellite) owns its own build and deploys to its first environment, then notifies the primary via `workflow_dispatch`. The primary records the satellite's SHA and version in the shared manifest and includes the satellite's deploys in every subsequent promotion. `external:` is **not** a GitOps mirror mechanism - it does not push rendered manifests to a target repo or track a pushed commit in a foreign repo. For GitOps-style deploys where the primary generates and pushes manifests to a dedicated config repo, use a callback workflow instead (see [Deploy Workflow Contract](./callback-contract#deploy-workflow-contract)). ```yaml ci: