AI tooling must be disclosed for contributions (#3372)

README.md

@@ -86,8 +86,41 @@ There's a few things you can do right now to help out:
    instance, you may need to read up on p2p and more complex operations like
    muxing to be able to help technically.
 
+## AI Assistance Notice
 
-## Supported Go Versions
+> [!IMPORTANT]
+>
+> If you are using **any kind of AI assistance** to contribute to libp2p,
+> it must be disclosed in the pull request.
+
+If you are using any kind of AI assistance while contributing to libp2p,
+**this must be disclosed in the pull request**, along with the extent to
+which AI assistance was used (e.g. docs only vs. code generation).
+If PR responses are being generated by an AI, disclose that as well.
+As a small exception, trivial tab-completion doesn't need to be disclosed,
+so long as it is limited to single keywords or short phrases.
+
+An example disclosure:
+
+> This PR was written primarily by Claude Code.
+
+Or a more detailed disclosure:
+
+> I consulted ChatGPT to understand the codebase but the solution
+> was fully authored manually by myself.
+
+Failure to disclose this is first and foremost rude to the human operators
+on the other end of the pull request, but it also makes it difficult to
+determine how much scrutiny to apply to the contribution.
+
+In a perfect world, AI assistance would produce equal or higher quality
+work than any human. That isn't the world we live in today, and in most cases
+it's generating slop. I say this despite being a fan of and using them
+successfully myself (with heavy supervision)!
+
+Please be respectful to maintainers and disclose AI assistance.
+
+# Supported Go Versions
 
 We test against and support the two most recent major releases of Go. This is
 informed by Go's own [security policy](https://go.dev/doc/security/policy).