Make AI policy rules mechanically enforceable#33
Open
damusix wants to merge 1 commit into
Open
Conversation
"Don't waste our time" left too much to interpretation. Keep the standing expectations; add rules a maintainer can apply without debate: mandatory Assisted-by disclosure, accepted-issue gate for AI-assisted PRs, ban on repeat violations. Maintainer AI use is now stated openly. Follows the RustPython/Ghostty model.
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
1 participant
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.
The current policy boils down to "be transparent and don't waste our
time". That standard is open to interpretation, which means reviewers
end up litigating quality case by case.
This revision retains the core expectations (defend-every-line, minimal
diffs, purposeful tests, docs) and makes every rule for outside
contributions mechanically enforceable:
Assisted-by:trailer in commits. Suspected-but-undisclosed use closesthe PR, no argument required.
unreviewed. AI-assisted issues stay welcome (human in the loop).
review as everything else.
Structure follows RustPython's policy
(derived from Ghostty's). The accepted-issue gate is the substantive
change for reviewer burden: maintainers only review AI-assisted PRs for
problems the team has already accepted as real.