[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

[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: 56a4903f-5e3a-4a81-b43a-dc06b6785c5c

📥 Commits

Reviewing files that changed from the base of the PR and between 3c9fa05 and 7b4f372.

📒 Files selected for processing (1)

• .github/CONTRIBUTING.md

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. (27)

• GitHub Check: governance / Debt ratchet
• GitHub Check: governance / Trusted-base reduction policy
• GitHub Check: governance / Allowlist Preflight
• GitHub Check: governance / Exemption ratchet
• GitHub Check: governance / Licence consistency
• GitHub Check: governance / Actions lockfile verify
• GitHub Check: governance / Check Workflow Staleness
• 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 / Code quality + docs
• GitHub Check: governance / Live Actions policy (credentialed advisory)
• GitHub Check: governance / Guix packaging policy (Nix retired)
• GitHub Check: rust-ci / Detect Cargo.toml
• GitHub Check: scan / shell-secrets
• GitHub Check: scan / rust-secrets
• GitHub Check: scan / gitleaks
• GitHub Check: hypatia / Hypatia Neurosymbolic Analysis
• GitHub Check: analyze (actions, none)
• GitHub Check: analyze (rust, none)
• GitHub Check: Groove manifest check
• GitHub Check: Validate K9 contracts
• GitHub Check: Validate eclexiaiser manifest
• GitHub Check: Empty-linter (invisible characters)
• GitHub Check: Validate DEED manifests
• GitHub Check: semgrep-cloud-platform/scan

🔇 Additional comments (1)

.github/CONTRIBUTING.md (1)

123-138: LGTM!

---

📝 Summary

Summary by CodeRabbit

• Documentation
  • Added guidance requiring signed commits for changes reaching the default branch, including signing requirements and approved commit and merge workflows.

Walkthrough

The contribution guide now describes signed-commit requirements for the default branch. It covers signing methods for people, interactive agents, apps, bots and workflows. It also specifies squash merges and notes that unsigned pull request commits block merging.

Changes

Signed commit guidance

Layer / File(s)	Summary
Commit signing and merge guidance .github/CONTRIBUTING.md	Added guidance on SSH signing and verified committer email for people and interactive agents. Apps, bots and workflows are directed to create signed commits through the API or estate action. The guide specifies squash merges and states that unsigned pull request commits block merging and rebase-merge is disabled.

Priority: ⬇️ Low

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

Change: Other

Suggested reviewers: metadatastician

Merge Risk: ⚪ Minimal · up to 7b4f3

No concrete issue in the documentation change was established. The linked policy and repository-specific enforcement settings could not be verified.

Architecture Summary

Architecture risk: 🔵 Low · up to 7b4f3

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/CONTRIBUTING.md: Added guidance requiring signed commits on the default branch, specifying SSH signing and verified committer-email settings for people and interactive agents, API-based signed commits for apps, bots and workflows, and squash merges; unsigned PR-branch commits block merging, and rebase-merge is disabled.

🚥 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 explains the signing-policy documentation change and its requirements, so it is relevant to the changeset.
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 tucked beneath one ear.
Squash the branch, then hop along,
The guide now keeps the rules in song.
One verified email, bright and clear!}

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

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Commit to this branch
• Create a new PR