Publish an organization Code of Conduct and governance contacts

[Scriptception]

Problem

The public organization has no shared behavior standard or maintained escalation route for community interactions.

User outcome

Contributors know the expected conduct, reporting path, enforcement scope, and responsible maintainers.

Scope

• Adopt a recognized Code of Conduct with clear scope and attribution.
• Define a maintained reporting route that does not expose complainants publicly.
• Document enforcement responsibilities, conflict handling, and repository-specific applicability.
• Link the policy from contribution guidance.

Non-goals

• Publishing confidential reports or investigation details.
• Creating a complex governance body before there is contributor demand.

Acceptance criteria

• The Code of Conduct is visible through GitHub community health inheritance.
• Reporting and enforcement ownership is explicit and reviewable.
• The policy covers repository, issue, pull-request, discussion, and project interactions.
• Maintainers verify the reporting route before publication.

Validation

• Check inheritance on a public repository without a local Code of Conduct.
• Run a tabletop report and escalation walkthrough with maintainers.

Relationships

• Linked from default contribution guidance.
• Independent of product catalog generation.