# Contributor Covenant Code of Conduct

> **Version**: Contributor Covenant v2.1 (adopted 2026-05-20)
> **Project**: PROJECT JAMES (`hashevolution/james-rag-evol`)
> **Scope**: all PROJECT JAMES community spaces (GitHub repo, Discussions,
> issues, pull requests, related Discord / Slack if any are created, and
> any public communication where an individual represents the project)

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
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, socio-economic
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.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes,
  and learning from the experience
- Focusing on what is best not just for us as individuals, but for the
  overall community

Examples of unacceptable behavior include:

- The use of sexualized language or imagery, and sexual attention or advances
  of any kind
- Trolling, insulting or derogatory comments, and personal or political
  attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email
  address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
  professional setting

## Project-Specific Norms

In addition to the general Contributor Covenant standards, PROJECT JAMES
contributors agree to:

- **Disagree with ideas, not people.** Technical pushback on a PR is welcome
  and expected; ad hominem framing is not.
- **Assume good intent on first read.** Maintainers and contributors are
  bilingual (KO ↔ EN), often working asynchronously across time zones —
  terse phrasing rarely means hostility.
- **Help newcomers calibrate the mother-platform constraint** (CLAUDE.md
  rule 1: no domain-specific features until v1.0) without making them feel
  unwelcome. The constraint is non-obvious; reviewers should explain it,
  not just reject.
- **Keep security-disclosure traffic out of public channels.** Use the
  process in [`SECURITY.md`](SECURITY.md). Public CoC reports of a security
  incident are themselves a CoC issue (they expose the disclosure surface).

## Enforcement Responsibilities

Community leaders (currently: the project maintainer, Hashevolution) are
responsible for clarifying and enforcing our standards of acceptable behavior
and will take appropriate and fair corrective action in response to any
behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or
reject comments, commits, code, wiki edits, issues, and other contributions
that are not aligned with this Code of Conduct, and will communicate reasons
for moderation decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies
when an individual is officially representing the community in public
spaces. Examples of representing our community include using an official
e-mail address, posting via an official social media account, or acting as
an appointed representative at an online or offline event.

## Reporting

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the project maintainer at **karu-7@hanmail.net**.

All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of
the reporter of any incident.

### What to include in a report

If you are comfortable doing so, include:

- A description of the incident (links to comments / PRs / issues if public)
- The approximate date and time
- Whether the incident is ongoing
- Whether you have already attempted to address it directly

You do not need to include all of the above to file a report. A brief note
is enough to start the process.

### Confidentiality

Reports are handled confidentially by the maintainer. The reporter's
identity is not shared with the subject of the report without the
reporter's explicit consent.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in
determining the consequences for any action they deem in violation of this
Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series of
actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external
channels like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public
or private interaction with the people involved, including unsolicited
interaction with those enforcing the Code of Conduct, is allowed during
this period. Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].

Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].

For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
at [https://www.contributor-covenant.org/translations][translations].

[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[Mozilla CoC]: https://github.com/mozilla/diversity
[FAQ]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
