Conversation
Generalizes an AI usage policy so other moby/docker repositories can link to or sync a shared version instead of maintaining their own. Covers disclosure in PR/issue descriptions only, no AI Co-Authored-By trailers in commits, human-in-the-loop review for any AI-generated content that gets posted, concision via a short summary plus a collapsible details section, scope discipline, no contribution farming, and an adoptable approved-issue requirement for AI-assisted PRs. Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
vvoland
reviewed
Sep 18, 2026
AI_POLICY.md should contain only the policy itself, so repos can link to it or keep a synced copy without carrying instructions meant for consumers of the document. Moves the guidance on linking, syncing, and tightening rules into README.md instead. Signed-off-by: Guillaume Lours <glours@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As more contributions across moby/docker repos are AI-assisted, each project would otherwise end up writing its own version of the same disclosure and quality rules. This adds a single, project-agnostic
AI_POLICY.mdtomoby/.githubthat repos can reference instead of reinventing it.It covers:
Co-Authored-Bytrailers for AI tools in commits (disclosure belongs in the description, not the commit)<details>section)This generalizes a draft policy first proposed for a single repo in docker/compose#13550; that PR's review thread is where most of these requirements were worked out, and is a useful reference for the reasoning behind each rule. This PR doesn't touch docker/compose — that repo should switch to referencing this doc separately, once it lands.
How should consuming repos reference this?
Two options came up in that discussion:
CONTRIBUTING.md/AGENTS.mdto this document, similar to how containerd links out to itsdocs/securitydocs. Zero maintenance, always up to date, but a link can go unread, and a repo can't easily layer project-specific additions onto it without duplicating text.<!-- do not edit between these lines -->markers so repo-specific additions can sit alongside it). Content lives in the repo itself and is more likely to be read, at the cost of sync tooling and the risk of copies drifting if the job breaks or gets ignored.Each repo can pick whichever fits its own workflow; this PR doesn't build the sync tooling for option 2, just documents the tradeoff.