Code of Conduct

Our commitment

We pledge to make participation in Agent Hooks Protocol 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, sexual identity and orientation, or other protected characteristic.

We commit to acting and interacting 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:

• showing empathy and respect for different viewpoints and experiences;
• giving and accepting constructive feedback;
• focusing criticism on ideas and behavior, not people;
• taking responsibility, apologizing, and learning from mistakes; and
• prioritizing the health of the overall community.

Unacceptable behavior includes:

• sexualized language, imagery, or attention;
• trolling, insulting or derogatory comments, and personal or political attacks;
• public or private harassment;
• publishing another person’s private information without explicit permission;
• threats, intimidation, stalking, or sustained disruption; and
• other conduct that could reasonably be considered inappropriate in a professional setting.

Scope

This Code applies in project spaces and when a person officially represents the project in public spaces. Project spaces include repository activity, review, community forums, meetings, and project-related private communication.

Reporting

Report conduct concerns privately to an active maintainer listed in MAINTAINERS.md. Use a private contact method shown on that maintainer’s GitHub profile. If no suitable private method is available, open a public issue that only asks a maintainer to establish a private channel; do not include names, evidence, or incident details in that issue.

Do not use the security vulnerability channel for a conduct report unless the report also concerns a vulnerability and the Security policy says that channel is appropriate.

Maintainers handling a report should disclose any conflict and recuse themselves. If the report concerns all active maintainers, request a private channel without details and ask that a neutral community member handle it. Reports should be handled as confidentially as reasonably possible, but the project cannot promise absolute confidentiality or a particular outcome or response time.

Enforcement

Maintainers are responsible for clarifying and enforcing standards of acceptable behavior. They can remove, edit, or reject comments, commits, code, issues, and other contributions that violate this Code, and can take proportionate temporary or permanent action.

Depending on context, impact, and pattern, responses can include a private correction, warning, temporary restriction, or permanent ban. Good-faith reports must not be retaliated against. Knowingly false or malicious reports can themselves violate this Code.

When safe and appropriate, the project should publish a redacted record of an enforcement outcome that affects project participation. It must not expose a reporter, affected person, private evidence, or sensitive personal information.

Attribution

This Code is adapted from the Contributor Covenant, version 2.1. Its enforcement approach is informed by the Contributor Covenant enforcement guidelines.