docs: say the rule about understanding what you submit - #95
Merged
Conversation
Agents wrote a lot of this and pretending otherwise would be dishonest, so the rule worth stating is not about tooling. It is that you have to be able to explain what your change does, with the agent closed, before you open the pull request. Reviewing a change nobody can explain costs more than writing it did. No gate here. The vouch check going into the implementation repositories is deliberately not proposed for this one, since a vendor-run gate on work heading for neutral governance is the wrong shape. The rule applies everywhere; the enforcement does not. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uc16CsknaQ9PTLxGj8TXXj
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.
Agents wrote a lot of this and pretending otherwise would be dishonest, so the rule worth stating is not about tooling. It is that you have to be able to explain what your change does, with the agent closed, before opening the pull request. Reviewing a change nobody can explain costs more than writing it did.
This is a direct answer to feedback already on the public record from the AAIF Technical Committee, that much of the code across these projects "feels vibe coded."
No gate here. The vouch check going into cmcp, ca2a and agent-manifest is deliberately not proposed for this repository. A vendor-run gate on work heading for neutral governance is the wrong shape. The rule applies everywhere; the enforcement does not.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Uc16CsknaQ9PTLxGj8TXXj