Spaces:
Running
Running
| # Contributor Covenant Code of Conduct | |
| ## 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, 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 behaviour that contributes to a positive environment: | |
| - Demonstrating empathy and kindness toward other people | |
| - Being respectful of differing opinions, viewpoints, and experiences | |
| - Giving and gracefully accepting constructive feedback | |
| - Accepting responsibility and apologising to those affected by our mistakes, and learning from them | |
| - Focusing on what is best for the overall community | |
| Examples of unacceptable behaviour: | |
| - The use of sexualised 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 | |
| ## Data-handling note | |
| This project processes clinical-note text. Even though the bundled dataset is fully synthetic, | |
| treat all note content as if it were real NHS PHI: | |
| - Never paste note text into issues, pull requests, or chat — reference file paths instead. | |
| - Never commit anything under `data/` (it is gitignored). | |
| - Never send patient text or surrogate tokens to external APIs — the `assert_clean()` guarantee | |
| and the Tavily usage policy both enforce this technically, but contributors must not work around them. | |
| - If you discover a real-data leak in any test fixture, treat it as a security incident: notify the | |
| maintainer privately rather than opening a public issue. | |
| ## Enforcement Responsibilities | |
| Community leaders are responsible for clarifying and enforcing our standards and will take | |
| appropriate and fair corrective action in response to any behaviour they deem inappropriate, | |
| threatening, offensive, or harmful. | |
| ## Scope | |
| This Code of Conduct applies within all community spaces, and also applies when an individual is | |
| officially representing the community in public spaces. | |
| ## Enforcement | |
| Instances of abusive, harassing, or otherwise unacceptable behaviour may be reported to the project | |
| maintainer by opening a confidential issue or by contacting the repository owner on GitHub | |
| (**@chaeyoonyunakim**). All complaints will be reviewed and investigated promptly and fairly. | |
| ## Attribution | |
| This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), | |
| version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html. | |