Add shared community governance contracts

CODE_OF_CONDUCT.md

@@ -0,0 +1,23 @@
+# Code of Conduct
+
+## Our Standard
+
+GitMoneyOS contributors, maintainers, and agents treat one another with respect. We keep feedback specific, evidence-based, and focused on the work.
+
+## Expected Behavior
+
+- Use clear, professional language.
+- Respect privacy, consent, and stated data boundaries.
+- Challenge claims and decisions without attacking people.
+- Give maintainers enough context to review a change safely.
+
+## Unacceptable Behavior
+
+- Harassment, discrimination, threats, or personal attacks.
+- Sharing private data, credentials, or sensitive material without authorization.
+- Misrepresenting outcomes, affiliations, ownership, or approval.
+- Using a public issue to disclose a security vulnerability.
+
+## Reporting and Enforcement
+
+For a safety or conduct concern, contact a GitMoneyOS maintainer through the private reporting path used by the relevant repository. Security vulnerabilities follow [SECURITY.md](SECURITY.md). Maintainers may remove content, limit participation, or take other proportionate action to protect people and repository integrity.

CONTRIBUTING.md

@@ -15,3 +15,10 @@ Thank you for contributing to the GitMoney OS framework and ecosystem.
 2. Ensure all changes follow the copy and security guidelines in SECURITY.md.
 3. Submit a Pull Request using the official pull request template.
 4. Obtain codeowner approval from @HitsuyoAkuWeb3 before merging.
+
+## Shared Community Contracts
+
+- [Code of Conduct](CODE_OF_CONDUCT.md)
+- [Governance](GOVERNANCE.md)
+- [Support](SUPPORT.md)
+- [Security](SECURITY.md)

GOVERNANCE.md

@@ -0,0 +1,20 @@
+# GitMoneyOS Governance
+
+## Purpose
+
+This repository provides the shared public governance contract for GitMoneyOS repositories. It does not replace repository-specific instructions or owner decisions.
+
+## Authority
+
+GitMoneyOS owners retain final decision authority. [CODEOWNERS](CODEOWNERS) identifies the default review owner for shared organization files.
+
+## Official Change Path
+
+1. Prepare a focused branch and pull request.
+2. State the business reason, owner, evidence, approval path, reuse path, and lifecycle.
+3. Keep secrets, client data, and unsupported claims out of the change.
+4. Obtain code-owner review before merge.
+
+## Boundaries
+
+A pull request does not authorize a merge, public release, deployment, billing change, permission change, visibility change, or destructive Git action. Those actions require explicit owner approval.

SUPPORT.md

@@ -0,0 +1,13 @@
+# Support
+
+## Product and Documentation Questions
+
+Use the relevant repository's issue tracker for non-sensitive questions, reproducible defects, and documentation corrections. Search existing issues before opening a new one.
+
+## Security and Sensitive Matters
+
+Do not include vulnerabilities, credentials, client data, or other sensitive details in a public issue. Follow [SECURITY.md](SECURITY.md) instead.
+
+## Contributions
+
+Read [CONTRIBUTING.md](CONTRIBUTING.md), [GOVERNANCE.md](GOVERNANCE.md), and the repository-specific `AGENTS.md` before proposing agent-assisted work.