[hyperpolymath]

Adds a Signed commits section to this repo's CONTRIBUTING, per owner ruling D218. The estate policy is docs/SIGNING-POLICY.adoc in hyperpolymath/standards.

This repo's default branch is covered by the zero-bypass Require-Signed-Commits ruleset, and rebase-merge is off. The section tells contributors what that requires:

• People and interactive agents sign with an SSH signing key.
• Apps, bots and workflows write through the API, so GitHub signs their commits.
• PRs are merged with squash.

If the file already had its own signing section, that section is replaced in place instead of adding a second one. Lines elsewhere that told people to sign with GPG are changed to match the policy (SSH for people).

This is a docs-only change. The commit was created through createCommitOnBranch, so GitHub signs it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01WRvDivYwLSeVCJUrfjic3f

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e35aaff1-be82-4ed3-935b-bdf2d6c4b466

📥 Commits

Reviewing files that changed from the base of the PR and between 20b044d and d172fb0.

📒 Files selected for processing (2)

• .github/CONTRIBUTING.md
• CONTRIBUTING.adoc

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details

⏰ Context from checks skipped due to timeout. (24)

• GitHub Check: governance / Debt ratchet
• GitHub Check: governance / Licence consistency
• GitHub Check: governance / Exemption ratchet
• GitHub Check: governance / Language / package anti-pattern policy
• GitHub Check: governance / Well-Known (RFC 9116 + RSR)
• GitHub Check: governance / Security policy checks
• GitHub Check: governance / Workflow security linter
• GitHub Check: governance / Allowlist Preflight
• GitHub Check: governance / Trusted-base reduction policy
• GitHub Check: governance / Code quality + docs
• GitHub Check: governance / Check Workflow Staleness
• GitHub Check: governance / Guix packaging policy (Nix retired)
• GitHub Check: governance / Live Actions policy (credentialed advisory)
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: scan / gitleaks
• GitHub Check: scan / shell-secrets
• GitHub Check: scan / rust-secrets
• GitHub Check: analyze (actions, none)
• GitHub Check: Validate DEED manifests
• GitHub Check: Validate K9 contracts
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: analyze (javascript-typescript, none)
• GitHub Check: Groove manifest check
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (2)

CONTRIBUTING.adoc (1)

70-86: LGTM!

.github/CONTRIBUTING.md (1)

122-138: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Documentation
  • Added guidance requiring signed commits for changes reaching the default branch, with instructions for people, automated tools and workflows.
  • Clarified that pull requests with unsigned commits cannot be merged and that squash merges are required.

Walkthrough

The two contribution guides now describe signed-commit requirements for people, interactive agents, apps, bots and workflows. They also state that unsigned commits block merging and that pull requests should use squash merges.

Changes

Signed commit guidance

Layer / File(s)	Summary
Signing requirements and merge rules .github/CONTRIBUTING.md, CONTRIBUTING.adoc	Both guides specify signing methods for different commit authors and state the rules for unsigned commits, squash merges and disabled rebase merges.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to d172f

This documentation-only change makes the contribution guides consistent about signing and squash merges. No concrete workflow disruption is established; the linked policy and hosting settings were not independently verified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding a Signed commits section to CONTRIBUTING.
Description check	✅ Passed	The description directly explains the documentation change, its signing requirements, and its policy basis.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit signs each commit with care,
SSH keys and verified email there.
Bots use the API to send,
Squash merges bring the branch to end.
No unsigned hops pass through the gate.}

_{Comment @coderabbitai help to get the list of available commands.}