CODE_OF_CONDUCT.md

Rama main · réplica de lectura del repositorio original.

# Code of Conduct

**Audience:** everyone who participates in this project — contributors, issue reporters, reviewers, maintainers.
**Scope:** all project spaces, including issues, pull requests, discussions, commit messages, code review, and any communication that identifies itself as project participation.

---

## Standard

This is a security and evidence project. The work depends on people being able to say "this claim is not supported by that artifact" and be heard. That requires a floor of professional conduct, and it also requires that technical disagreement stays welcome.

**Expected:**

- Address the argument, the code, or the evidence. Not the person.
- Accept correction. Being shown wrong about a technical claim is the mechanism working, not an attack.
- Give correction usefully: say what is wrong, what evidence shows it, and what would change your mind.
- Respect that contributors have different levels of experience, time, and context.
- Assume the other person is acting in good faith until you have specific evidence otherwise.

**Not acceptable:**

- Harassment, intimidation, or sustained disruption.
- Personal attacks, demeaning remarks, or insults — including ones framed as technical criticism.
- Discriminatory language or conduct related to age, disability, ethnicity, gender identity or expression, nationality, personal appearance, race, religion, sexual identity or orientation, or any comparable characteristic.
- Publishing another person's private information without their explicit permission.
- Sexualised language or imagery, or unwelcome sexual attention.
- Deliberately submitting content designed to mislead reviewers about what a change does. In this project that includes fabricated evidence, invented measurements, and claims presented with citations that do not support them.

## Security-specific conduct

Two rules particular to this project:

1. **Report vulnerabilities privately.** Do not open a public issue for a security finding. Follow [SECURITY.md](SECURITY.md). Disclosing a live vulnerability publicly before it is fixed puts operators at risk and is treated as a conduct violation, not only a process error.
2. **Do not test against systems you do not own.** Security research in this project is confined to your own deployments and to synthetic, local test environments.

## Scope

This applies in all project spaces and when an individual is representing the project in public. It does not extend to unrelated conduct in unaffiliated venues.

## Reporting

Report conduct concerns to the maintainer through [GitHub's private reporting](https://github.com/JuanLunaIA/aegis-latent-core/security/advisories/new) or by opening a private communication channel with `@JuanLunaIA`. Use the private path rather than a public issue.

A report should include what happened, where, when, and any links or screenshots. You do not need to prove intent.

## Enforcement

Maintainers are responsible for clarifying this standard and may take action they judge proportionate, including:

| Response | Applies to |
| --- | --- |
| Private correction | A first, isolated lapse where the behaviour is likely unintentional. |
| Public correction | Conduct visible to others where a private note would leave the record misleading. |
| Temporary restriction | Repeated behaviour after correction, or a single serious incident. |
| Permanent ban | Sustained harassment, a pattern of violations, or conduct that endangers others. |

Maintainers who do not follow this standard in good faith may face consequences determined by other maintainers.

## Boundary

This document sets expectations for participation. It is not an employment policy, a contract, or a legal instrument, and it does not create obligations on the project beyond good-faith enforcement. Enforcement is at maintainer discretion and is not subject to an appeals process with defined timelines.

## Attribution

Adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, with security-specific additions particular to this project.

---

**Related:** [Contributing](CONTRIBUTING.md) · [Security Policy](SECURITY.md) · [Governance](GOVERNANCE.md) · [Support](SUPPORT.md)