# Code of Conduct

## Our Standards

n-dx is a technical project. Contributions and community participation are expected to be:

- **Constructive** — feedback on code, architecture, and documentation should be specific and actionable
- **Accurate** — claims about behavior, performance, or design should be verifiable
- **Direct** — disagreements are fine; personal attacks are not
- **Inclusive** — contributors at all experience levels are welcome; condescension isn't

Behavior that won't be tolerated:

- Harassment, intimidation, or sustained hostility toward any contributor
- Discriminatory language or conduct based on identity, background, or experience level
- Bad-faith engagement — filing spurious issues, derailing discussions, or misrepresenting others' positions
- Publishing private information about others without consent

## Scope

This code of conduct applies to all project spaces: GitHub Issues, Pull Requests, Discussions, and any affiliated communication channels. It also applies when someone is representing the project publicly.

## Contributing

Before opening a PR or issue:

- Check existing issues and PRs to avoid duplication
- For significant changes, open an issue first to discuss the approach
- Follow the existing code style and package conventions documented in `PACKAGE_GUIDELINES.md`
- Include tests for new functionality; don't break existing ones
- Keep PRs focused — one logical change per PR makes review tractable

Commit messages should describe what changed and why, not just what files were touched.

## Reporting

If you observe conduct that violates this policy, report it by emailing the maintainers directly. Reports are handled confidentially. Include:

- A description of what happened
- Where and when it occurred
- Any relevant context or documentation

Reports made in bad faith — to retaliate against contributors or suppress legitimate criticism — are themselves a violation of this policy.

## Enforcement

Maintainers are responsible for clarifying and enforcing these standards. Responses to confirmed violations may include:

1. **Warning** — written notice with an explanation of what was unacceptable
2. **Temporary restriction** — limited participation in project spaces for a defined period
3. **Permanent ban** — removal from all project spaces for repeated or severe violations

Enforcement decisions are made at maintainer discretion. The severity and context of the violation inform the response.

## Attribution

This Code of Conduct is maintained by the n-dx project maintainers.