From bfd1e2d30331b931fc13165996f3ea8e5d8b1341 Mon Sep 17 00:00:00 2001 From: Imran Siddique Date: Wed, 2 Sep 2026 20:43:50 -0700 Subject: [PATCH] docs: say the rule about understanding what you submit 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) Claude-Session: https://claude.ai/code/session_01Uc16CsknaQ9PTLxGj8TXXj --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8b96cb5..ccaad7e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -9,6 +9,14 @@ Thank you for your interest in contributing to the TRACE test suite. 3. Commit using [Conventional Commits](https://www.conventionalcommits.org) 4. Open a pull request against `main` +## Using AI to contribute + +Use agents. A lot of this was built with them and saying otherwise would be dishonest. + +The rule is that you have to understand what you submit. If you cannot explain what your change does and how it interacts with the rest of the system, with the agent closed, do not open the pull request. Reviewing a change nobody can explain costs more than writing it did, and it becomes someone else's problem the moment it merges. + +That is a rule about understanding, not about tooling. + ## Reporting Security Issues Use [GitHub Security Advisories](https://github.com/agentrust-io/trace-tests/security/advisories/new) rather than public issues.