Frame deployment designs as "Deploying <service provider> from <CI/CD platform>"

Rename the design to "Deploying Azure from GitHub" and adopt the service
provider / CI/CD platform vocabulary across the deployment spec, index, and
design so the two axes of each combination are unambiguous; rename the design
file to azure-from-github.md to match.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

…ities/deployment/designs/github-azure.md …/deployment/designs/azure-from-github.mdsrc/docs/Capabilities/deployment/designs/github-azure.md renamed to src/docs/Capabilities/deployment/designs/azure-from-github.md src/docs/Capabilities/deployment/designs/github-azure.md renamed to src/docs/Capabilities/deployment/designs/azure-from-github.md

@@ -1,18 +1,19 @@
 ---
-title: GitHub + Azure design
-description: How the deployment spec is delivered with GitHub as the deployment platform and Azure as the service provider, using Terraform to compute and apply the approved effect.
+title: Deploying Azure from GitHub
+description: How the deployment spec is delivered with Azure as the service provider and GitHub as the CI/CD platform, using Terraform to compute and apply the approved effect.
 ---
 
-# Deployment — GitHub + Azure design
+# Deploying Azure from GitHub
 
 This design delivers the [Deployment spec](../spec.md) for one combination:
-**GitHub** as the deployment platform and **Azure** (including Microsoft Entra
-ID) as the service provider, with **Terraform (open source)** as the change
+**Azure** (including Microsoft Entra ID) as the service provider and **GitHub**
+as the CI/CD platform, with **Terraform (open source)** as the change
 engine. The computed effect the spec speaks of is a **saved Terraform plan**;
 the record of state is a remote Terraform state per environment.
 
-Another design covers another combination — Azure DevOps with Azure, GitHub with
-AWS, GitHub with GitHub — without changing the spec.
+Another design covers another combination — deploying Azure from Azure DevOps,
+deploying AWS from GitHub, deploying GitHub from GitHub — without changing the
+spec.
 
 ## Approach
 
@@ -166,7 +167,7 @@ on:
 ```
 
 The core is provider-agnostic; the Azure sign-in is the single service-provider
-step. A different service provider (AWS) or deployment platform (Azure DevOps)
+step. A different service provider (AWS) or CI/CD platform (Azure DevOps)
 reuses this design's shape with its own identity step and is documented as its
 own design under [Deployment](../index.md).
 

src/docs/Capabilities/deployment/index.md

@@ -1,6 +1,6 @@
 ---
 title: Deployment
-description: How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, one design per deployment platform and service provider.
+description: How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, and one design for each combination of deploying a service provider from a CI/CD platform.
 ---
 
 # Deployment
@@ -11,10 +11,13 @@ change together with that effect across every environment it will pass through,
 and the approved effect is exactly what is deployed — with every action recorded.
 
 The **spec** is the durable contract and is deliberately free of any technology.
-Each **design** delivers that contract for one combination of **deployment
-platform** and **service provider** (for example GitHub with Azure, Azure DevOps
-with Azure, GitHub with AWS, or GitHub with GitHub). Adding a combination adds a
-design; it never changes the spec.
+Each **design** delivers that contract for one combination, named **"deploying
+<service provider> from <CI/CD platform>"** so the two parts are
+clear: the **service provider** is where the resources live (Azure, AWS,
+GitHub), and the **CI/CD platform** is what runs the deployment (GitHub, Azure
+DevOps) — for example deploying Azure from GitHub, deploying Azure from Azure
+DevOps, deploying AWS from GitHub, or deploying GitHub from GitHub. Adding a
+combination adds a design; it never changes the spec.
 
 ## Spec
 
@@ -24,6 +27,6 @@ design; it never changes the spec.
 
 ## Designs
 
-| Design | Deployment platform | Service provider | Description |
+| Design | Service provider | CI/CD platform | Description |
 | --- | --- | --- | --- |
-| [GitHub + Azure](designs/github-azure.md) | GitHub | Azure | GitHub Actions and Terraform deploy Azure and Entra resources with passwordless identity, approving the code change together with its per-environment effect. |
+| [Deploying Azure from GitHub](designs/azure-from-github.md) | Azure | GitHub | GitHub Actions and Terraform deploy Azure and Entra resources with passwordless identity, approving the code change together with its per-environment effect. |

src/docs/Capabilities/deployment/spec.md

@@ -60,7 +60,7 @@ of deployments whose deployed effect equals their approved effect (target 100%).
 
 Out of scope:
 
-- The choice of deployment platform, service provider, and change engine — each
+- The choice of CI/CD platform, service provider, and change engine — each
   combination is a **[design](index.md)**, not part of this contract.
 - Application or runtime release — this capability governs managed resources.
 - Provisioning of the state, identity, and trust the deployment relies on, which
@@ -220,13 +220,13 @@ Feature: Deployment approves and applies the effect, not just the code
   effect.
 - A **record of state** for each environment exists, against which an effect is
   computed and whose change can invalidate a previously approved effect.
-- The specifics of **how** — the deployment platform, the service provider, the
+- The specifics of **how** — the CI/CD platform, the service provider, the
   change engine, and the identity mechanism — are supplied by a
   [design](index.md), not this spec.
 
 ## Where this connects
 
 - [Designs](index.md) — how these requirements are delivered for a specific
-  deployment platform and service provider.
+  service provider and CI/CD platform.
 - [Documentation Model](../../Ways-of-Working/Documentation-Model.md) — why this spec holds only the why and the what.
 - [PR Format](../../Ways-of-Working/PR-Format.md) — the review that approves the change and its effect.

src/docs/Capabilities/index.md

@@ -25,7 +25,7 @@ the same spec-and-design shape as any other capability; the standalone
 | [Dependency Updates](dependency-updates/index.md) | How a repository's pinned dependencies are kept current and secure through automated, labelled update pull requests. |
 | [Merge Automation](merge-automation/index.md) | How a pull request's required status checks become the machine-readable signal that drives automated approval and merge — green merges, red holds, nothing bypasses the gate. |
 | [Downstream Release Propagation](downstream-release-propagation/index.md) | How a release in one repository propagates to the repositories that depend on it, via a delegated agent pull request. |
-| [Deployment](deployment/index.md) | How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, one design per deployment platform and service provider. |
+| [Deployment](deployment/index.md) | How a change to managed resources is approved together with its effect and deployed exactly as approved — one spec, and one design for each combination of deploying a service provider from a CI/CD platform. |
 | [VS Code Extension Framework](vscode-extension-framework/index.md) | How a VS Code extension is built, tested, versioned, packaged, and published — one GitHub-native pipeline, opt-in from a template and a single settings file. |
 | [PowerShell on GitHub](powershell-on-github/index.md) | How we make GitHub a first-class platform for PowerShell through reusable modules, actions, and capability gaps we close over time. |
 

src/zensical.toml

@@ -136,7 +136,7 @@ nav = [
     {"Deployment" = [
       "Capabilities/deployment/index.md",
       {"Spec" = "Capabilities/deployment/spec.md"},
-      {"GitHub + Azure design" = "Capabilities/deployment/designs/github-azure.md"},
+      {"Deploying Azure from GitHub" = "Capabilities/deployment/designs/azure-from-github.md"},
     ]},
     {"VS Code Extension Framework" = [
       "Capabilities/vscode-extension-framework/index.md",