diff --git a/.github/workflows/dco-merge-group.yml b/.github/workflows/dco-merge-group.yml
new file mode 100644
index 0000000..f8f4302
--- /dev/null
+++ b/.github/workflows/dco-merge-group.yml
@@ -0,0 +1,19 @@
+name: DCO merge-group shim
+
+# The org-wide DCO app (https://github.com/apps/dco) validates sign-offs on
+# pull requests but does not report on merge-queue (merge_group) commits, so
+# a required "DCO" check would stall the queue. This shim reports a passing
+# "DCO" check for merge groups only — the real validation already happened
+# on the pull request. Same pattern as onnx/onnx#5399.
+
+on:
+  merge_group:
+
+permissions: {}
+
+jobs:
+  dco:
+    name: DCO
+    runs-on: ubuntu-latest
+    steps:
+      - run: echo "DCO was validated on the pull request by the DCO app."
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2063a54..7e1247b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -65,7 +65,7 @@ contributors about the change, discuss the best way to go about implementing it.
 > pull requests from branches on your fork. To do this, run:
 >
 > ```
-> git remote add upstream https://github.com/godaddy/ans.git
+> git remote add upstream https://github.com/agentnameservice/ans.git
 > git fetch upstream
 > git branch --set-upstream-to=upstream/main main
 > ```
@@ -108,11 +108,47 @@ Generally speaking, Git handles attribution automatically.
 Ensure that your contribution follows the standards set by the project's style
 guide with respect to patterns, naming, documentation and testing.
 
+## Developer Certificate of Origin
+
+This project follows the Linux Foundation contribution model. Every commit
+must carry a `Signed-off-by:` trailer certifying the
+[Developer Certificate of Origin](https://developercertificate.org) — your
+assertion that you have the right to submit the change under the project's
+license. Sign off each commit with:
+
+```
+git commit -s
+```
+
+Missing sign-offs on an existing branch can be fixed with
+`git rebase --signoff origin/main` followed by a force-push. The `DCO`
+status check — the org-wide [DCO app](https://github.com/apps/dco), the
+same enforcement used across Linux Foundation projects — validates this
+on every pull request; bot-authored commits (Dependabot, release-please)
+and merge commits are exempt.
+
+## AI-Assisted Contributions
+
+AI-assisted contributions are welcome **with disclosure**, following the
+[Linux kernel convention](https://docs.kernel.org/process/coding-assistants.html):
+
+- Disclose the tooling in the pull request's **AI assistance** section,
+  naming the tool and model, e.g. `Assisted-by: Claude Code (claude-fable-5)`.
+- AI tools must never add `Signed-off-by:` lines. DCO certification belongs
+  to the human submitter, who remains fully responsible for the correctness
+  and licensing of the contribution.
+
+## Linking Issues
+
+Every pull request must reference an issue with a closing keyword (e.g.
+`Fixes #123`). Open the issue first — issues are where triage and
+prioritization happen.
+
 # Additional Resources
 
 - [General GitHub Documentation](https://help.github.com/)
 - [GitHub Pull Request documentation](https://help.github.com/send-pull-requests/)
 
-[issues]: https://github.com/godaddy/ans/issues
+[issues]: https://github.com/agentnameservice/ans/issues
 [coc]: ./CODE_OF_CONDUCT.md
 [fork]: https://help.github.com/en/articles/fork-a-repo
\ No newline at end of file