Betat Code of Conduct

Betat exists to preserve the record of human beings for other human beings. A project with that purpose must treat the humans who build it accordingly.


Scope

This Code of Conduct applies to all spaces of the Betat open-source project: this repository, its issues and pull requests, and any official project communication channel. It governs Contributors participating in the codebase. Provenancier communities are self-governed and set their own conduct standards within their domains, as defined in ARCHITECTURE.md.


Our Standard

Participants in this project commit to:

  • Respect the person. Critique ideas, designs, and code — never the human being behind them. Disagreement is expected; disrespect is not.
  • Assume good faith. Contributors join from every continent, language, and level of experience. Unclear communication is an opportunity to clarify, not to attack.
  • Welcome newcomers. A first pull request deserves patience. No contribution is too small, and no question is too basic.
  • Keep it about the work. Harassment, discrimination, personal attacks, sexualized language, doxxing, and sustained disruption have no place here, in any form.
  • Honor the mission’s humility. Betat verifies human origin — not correctness, not quality, not worth. Contributors extend the same restraint to each other: we do not judge who is worthy of participating, only whether contributions serve the project.

Enforcement

Violations may be reported to the project maintainer by opening a confidential contact through the repository’s listed maintainer profile, or via the contact published at betat.org.

The maintainer will review reports promptly and in confidence. Responses are proportionate and may include a private warning, a public correction, temporary restriction from project spaces, or permanent removal for severe or repeated violations. Reporters will not face retaliation for good-faith reports.


Evolution

Like the project’s Foundational Guidelines, this document is a seed. The Contributor community may refine it through the standard issue and pull request process. Projects preferring an established standard may propose adopting the Contributor Covenant (contributor-covenant.org) — the widely used open-source code of conduct — as a replacement or supplement.


Betat. The human record, for the other person.


Comments & ideas

This site uses Just the Docs, a documentation theme for Jekyll.