From 04ca29ca4a3343039ae020fc65d3990855903d9f Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:07:50 +0200 Subject: [PATCH 1/6] State enterprise-wide default scope and same-altitude initiative layering in Repository Standard intro Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index d11cb4d..9f17b6c 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -7,6 +7,10 @@ description: The baseline files and behaviours every repository must expose so i A repository is the smallest unit of ownership in the MSX ecosystem. It must explain what it is, how to contribute, how security is handled, how dependencies are kept current, and which standards govern its automation. +The Repository Standard is the default for every repository across the MSX Enterprise, regardless of initiative, organization, or technology. It defines the baseline contract a repository must meet to be understandable, secure, and maintainable on its own. + +Initiative standards operate at the same altitude as this standard, not beneath it. An initiative such as PSModule adds to and adjusts these defaults for its repository types rather than merely implementing them. A repository inherits every rule this standard sets unless its initiative explicitly changes it; where an initiative standard adds or overrides a rule, the initiative standard governs that initiative's repositories. + This page defines the repository-level contract. Initiative documentation defines implementation details such as exact file templates, managed-file source paths, and rollout automation. ## Required files From 833ee7ec96cb31988abc5106fdede22d834cebc7 Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:08:46 +0200 Subject: [PATCH 2/6] Add AGENTS.md and CLAUDE.md to the required files baseline Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index 9f17b6c..7cdd613 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -25,6 +25,8 @@ Every repository must carry the files that make it understandable and governable | `SECURITY.md` | Explains supported versions and private vulnerability reporting. | | `SUPPORT.md` | Explains where users ask for help. | | `CODE_OF_CONDUCT.md` | Defines expected community behaviour. | +| `AGENTS.md` | Cross-tool agent onboarding entry point that points to the initiative's canonical agent guidance. | +| `CLAUDE.md` | Claude Code entry point that imports `AGENTS.md` so Claude reads the same guidance. | | `.github/dependabot.yml` | Configures dependency and supply-chain update pull requests. | | `.github/CODEOWNERS` | Routes reviews to responsible owners. | | `.github/pull_request_template.md` | Guides contributors to provide change type, impact, validation, and links. | From 960f2455020150c89230fbe70ebf06d0dff07639 Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:08:58 +0200 Subject: [PATCH 3/6] Drop release.yml and linters config from the required files baseline These apply only when a repository generates releases or runs those linters, so they are not part of the enterprise-wide baseline. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index 7cdd613..2cd9be6 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -30,8 +30,6 @@ Every repository must carry the files that make it understandable and governable | `.github/dependabot.yml` | Configures dependency and supply-chain update pull requests. | | `.github/CODEOWNERS` | Routes reviews to responsible owners. | | `.github/pull_request_template.md` | Guides contributors to provide change type, impact, validation, and links. | -| `.github/release.yml` | Defines release-note categories where GitHub releases are generated. | -| `.github/linters/*` | Stores linter configuration derived from the written standards. | | `.gitattributes` | Defines Git file handling defaults. | | `.gitignore` | Defines files that should not enter version control. | From dd924809879d1e10e10362fa79e80f0a8b32dfcf Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:09:24 +0200 Subject: [PATCH 4/6] Reword dependabot, pull request template, gitattributes, and gitignore descriptions to be ecosystem-aware and PR Format aligned Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index 2cd9be6..cc7642a 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -27,11 +27,11 @@ Every repository must carry the files that make it understandable and governable | `CODE_OF_CONDUCT.md` | Defines expected community behaviour. | | `AGENTS.md` | Cross-tool agent onboarding entry point that points to the initiative's canonical agent guidance. | | `CLAUDE.md` | Claude Code entry point that imports `AGENTS.md` so Claude reads the same guidance. | -| `.github/dependabot.yml` | Configures dependency and supply-chain update pull requests. | +| `.github/dependabot.yml` | Configures ecosystem-appropriate dependency-update pull requests. The `github-actions` ecosystem is expected in virtually every repository; add the language, package, container, or infrastructure ecosystems the repository actually develops in. | | `.github/CODEOWNERS` | Routes reviews to responsible owners. | -| `.github/pull_request_template.md` | Guides contributors to provide change type, impact, validation, and links. | -| `.gitattributes` | Defines Git file handling defaults. | -| `.gitignore` | Defines files that should not enter version control. | +| `.github/pull_request_template.md` | Scaffolds pull requests in the MSX [PR Format](PR-Format.md) (PR Manager) style — an icon + change-type + user-facing-outcome title, user-facing description sections, an optional technical-details block, and a related-issues block. | +| `.gitattributes` | Normalizes line endings and declares text/binary handling so the repository can be developed and built consistently on Linux, macOS, and Windows. | +| `.gitignore` | Ignores files that must never be committed, tailored to the repository's ecosystem: operating-system files, editor and developer-tooling files, language and test-harness artifacts, and all local build outputs and files created during build and test. | Repository types may require additional files. For example, a PowerShell module may require `.github/PSModule.yml`, while a GitHub Action may require `action.yml`. From ec5ae4267a332282f06ec1aeb420d1d6388e856a Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:09:57 +0200 Subject: [PATCH 5/6] Reinforce same-altitude initiative layering in the Initiative implementation guidance section Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index cc7642a..627c516 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -133,7 +133,7 @@ Managed-file pull requests should clearly say: ## Initiative implementation guidance -The central standard deliberately stops at the requirement level. Initiative repositories own implementation design. +The central standard deliberately stops at the requirement level, and initiative standards operate at the same altitude rather than beneath it: an initiative adds to and adjusts these defaults for its repository types, and a repository inherits every rule this standard sets unless its initiative explicitly changes it. Where an initiative standard adds or overrides a rule, the initiative standard governs that initiative's repositories. Within that relationship, initiative repositories own implementation design. An initiative should document: From 09125c3f630660dc9717c2b067730b56ddca2e0a Mon Sep 17 00:00:00 2001 From: Marius Storhaug Date: Sun, 26 Jul 2026 21:10:07 +0200 Subject: [PATCH 6/6] Frame linter configuration defaults as applies-when-used guidance rather than a mandatory baseline file Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --- src/docs/Ways-of-Working/Repository-Standard.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/docs/Ways-of-Working/Repository-Standard.md b/src/docs/Ways-of-Working/Repository-Standard.md index 627c516..787b862 100644 --- a/src/docs/Ways-of-Working/Repository-Standard.md +++ b/src/docs/Ways-of-Working/Repository-Standard.md @@ -89,7 +89,7 @@ See [Dependency Updates](../Capabilities/dependency-updates/spec.md) for the cen ## Linter configuration defaults -Linter configuration must be repository-local when the CI job reads it from the repository. Most shared linter configs live under `.github/linters/`. +Linter configuration is applied only when the repository actually uses the linter; it is not a mandatory baseline file. Where a linter is used and its CI job reads configuration from the repository, that configuration must be repository-local. Most shared linter configs live under `.github/linters/`. Examples: