Codex Limits Code of Conduct
Community standards for a respectful, inclusive, and constructive project.
## Contents
- [Our pledge](#our-pledge)
- [Expected behavior](#expected-behavior)
- [Unacceptable behavior](#unacceptable-behavior)
- [Scope](#scope)
- [Reporting a conduct issue](#reporting-a-conduct-issue)
- [Enforcement responsibilities](#enforcement-responsibilities)
- [Enforcement guidelines](#enforcement-guidelines)
- [Attribution](#attribution)
- [Related documentation](#related-documentation)
## Our pledge
We pledge to make participation in the Codex Limits community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
## Expected behavior
Examples of behavior that contributes to a positive community include:
| Behavior | What it means |
| -------------------------- | ------------------------------------------------------------------------------------------ |
| Be respectful | Treat contributors, users, and maintainers with patience and consideration. |
| Be constructive | Give actionable feedback and focus criticism on ideas, code, and outcomes. |
| Be collaborative | Share relevant context, listen to other viewpoints, and work toward consensus. |
| Be accountable | Accept responsibility, apologize when appropriate, and learn from mistakes. |
| Protect privacy and safety | Use sanitized examples and respect the project's security and redaction rules. |
| Respect project boundaries | Respect documented decisions about scope, compatibility, safety, and contribution process. |
## Unacceptable behavior
The following behavior is not acceptable:
- harassment, intimidation, stalking, threats, or discriminatory language or imagery;
- sexualized language, imagery, or attention, including unwelcome advances;
- trolling, insulting or derogatory comments, personal attacks, or sustained disruption;
- publishing another person's private information without explicit permission;
- exposing credentials, private Codex data, private paths, or other sensitive information;
- pressuring anyone to disclose personal, employment, account, or security information;
- deliberately disrupting issues, Pull Requests, reviews, releases, or other project work;
- retaliation against anyone who reports a concern or participates in an investigation;
- other conduct that would reasonably be considered inappropriate in a professional setting.
## Scope
This Code of Conduct applies in all project spaces, including:
- GitHub issues, Pull Requests, reviews, discussions, and repository content;
- project-related email and other direct communication;
- community events or conversations where someone is representing Codex Limits;
- public spaces when an individual is acting as an official project representative.
Representation includes using an official project account, posting from an official channel, or acting with delegated project authority.
## Reporting a conduct issue
Report abusive, harassing, or otherwise unacceptable behavior privately by emailing [simonesiega1@gmail.com](mailto:simonesiega1@gmail.com) with the subject `Codex Limits conduct report`. Do not open a public issue for a private conduct report.
Include only the information needed to understand and review the concern:
| Field | What to include |
| ------------------ | -------------------------------------------------------------------- |
| Summary | A concise description of what happened. |
| Location and date | Where and approximately when the behavior occurred. |
| Supporting context | Relevant links, quotations, or sanitized screenshots when available. |
| Requested outcome | Any immediate safety concern or resolution you want considered. |
All reports will be reviewed as promptly and fairly as reasonably possible. The maintainer will respect the privacy and security of the reporter and affected parties, sharing information only when necessary to investigate or respond.
If the report concerns the project maintainer or cannot safely be reported by email, use GitHub's [Report Abuse form](https://support.github.com/contact/report-abuse). Security vulnerabilities should instead follow the private process in [`SECURITY.md`](SECURITY.md#reporting-a-vulnerability).
## Enforcement responsibilities
Project maintainers are responsible for clarifying and enforcing these standards. They may remove, edit, or reject comments, commits, code, issues, Pull Requests, and other contributions that do not align with this Code of Conduct.
Maintainers will communicate moderation decisions when appropriate and will not publicly identify a reporter without permission unless required by law or necessary to address an immediate safety risk.
## Enforcement guidelines
Maintainers will use these guidelines when determining consequences for behavior that violates this Code of Conduct:
| Level | Consequence | Community impact | Response |
| ----- | ------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| 1 | Correction | Inappropriate language or behavior with limited impact. | A private explanation of the violation and a request for correction; a public apology may be requested. |
| 2 | Warning | A single serious incident or repeated behavior after correction. | A formal warning with conditions against further contact or specified behavior for a defined period. |
| 3 | Temporary ban | Sustained or serious violations, including continued inappropriate behavior. | Temporary exclusion from project interaction and public or private communication with involved participants. |
| 4 | Permanent ban | A pattern of violations, harassment, threats, or aggression toward individuals. | Permanent exclusion from project spaces and community interaction. |
Enforcement decisions will consider context, severity, impact, prior behavior, and the safety of the community.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html), available under the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0/).
The enforcement guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
## Related documentation
- Read [`CONTRIBUTING.md`](CONTRIBUTING.md) for contribution workflow and review expectations.
- Read [`SECURITY.md`](SECURITY.md) for private vulnerability reporting and project safety boundaries.
- Use the [documentation hub](docs/README.md) to find product, automation, agent, and development guides.