policy-catalogue: add Bevy Organization entry - #23
Merged
Conversation
Closes the Bevy catalogue-entry issue. Source pinned to cd91a95 in bevy-website so the verbatim excerpts survive link rot.
5 tasks
ecogetaway
pushed a commit
that referenced
this pull request
Jul 31, 2026
…ntries (#30) The single follow-up promised once #21, #23-#29 were in. Count 13 to 20, seven rows added, and the closing line from twelve adopted policies to nineteen plus the one proposal. Each row's distinctive feature is the axis that entry adds to the catalogue rather than a summary of the policy, matching the existing rows: - Home Assistant — the only policy disclosing the project's own AI use, and template bypass as the observable proxy for autonomy - Mesa — the only graduated disclosure vocabulary, and incompatible with both Fedora and Kubernetes on the same mechanism - OpenStreetMap — the only permissive policy asking for no disclosure at all, enforcing on absence of understanding - FreeBSD — the only policy protecting the project as training data; its AI clause is a routing rule rather than a stance - Bevy — the only policy reasoning about its own enforceability - Zig — the strictest, and the only one reaching upstream of the artifact - Asahi Linux — the only stance derived from a pre-existing rule rather than written fresh Every link in the table resolves to a file, and every file in policy-catalogue/ except README and TEMPLATE appears in the table.
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.
Summary
Adds
policy-catalogue/bevy.mdfor the Bevy Organization, closing #16. Source pinned tocd91a95inbevy-website; the policy lives on the website (added in bevyengine/bevy-website#2204, 2025-10-14) andbevy/CONTRIBUTING.mdlinks to it.The thing I'd point you at: Bevy is the only policy in the catalogue that reasons explicitly about its own enforceability. The
[^1]footnote exempts trivial LLM completions on the stated ground that they are "by definition not detectable" — the ban is drawn at the limit of what anyone can observe, and the policy says so. Every other prohibition in the corpus is silent about that gap. Three more v0.2 signals in the entry's notes: a prohibition that ships its own detection heuristics, a two-stepS-Nominated-to-Closeenforcement workflow, and retroactive removal as a sanction (no other entry has one).I left
policy-catalogue/README.mduntouched deliberately — #21 and the Home Assistant PR also touch that table, and three PRs editing the same rows would conflict. Happy to send a single follow-up updating the count and rows once you've decided the merge order, or to add it here if you'd rather each PR carry its own.AI disclosure (required — we dogfood our own standard)
cd91a95) before submission — 7 of 7 string checks passed.Attestations (required)
Type of contribution
policy-catalogue/)Sources
cd91a95— https://github.com/bevyengine/bevy-website/blob/cd91a9582dd368a7712b66f86e8669722315c13a/content/learn/contribute/policies/ai.mdMaintainership disclosure: I maintain MergeWarden, a checker in the layer-3 space discussed in #20/#22. This entry documents Bevy's policy only and makes no claim about any tool.