Permea is an open scientific OSS project. The community should support rigorous, respectful, evidence-bounded collaboration across dry-lab contributors, reviewers, maintainers, wet-lab collaborators, and partner organizations.
This code of conduct applies to project repositories, issues, pull requests, discussions, review threads, and other Permea-managed community spaces.
Participants are expected to:
- communicate respectfully
- assume good faith while still reviewing claims rigorously
- keep technical and scientific disagreement focused on evidence, methods, assumptions, and repository artifacts
- separate ambition from demonstrated evidence
- respect contributor time and review boundaries
- respect data, license, confidentiality, and partner constraints
- disclose uncertainty rather than overstating conclusions
Good-faith technical and scientific disagreement is welcome. Unsupported certainty is not.
Unacceptable behavior includes:
- harassment, intimidation, discrimination, or personal attacks
- sexualized language or imagery
- trolling, repeated disruption, or bad-faith argument
- publishing private communications without consent
- exposing secrets, credentials, private data, restricted row-level datasets, or unlicensed biological datasets
- using project channels to promote unsupported medical, therapeutic, or clinical claims
- representing benchmark evidence as completed biological or clinical validation
- implying Permea has achieved AlphaFold-level performance, adoption, or standardization
- claiming universal delivery prediction from limited evidence
Permea may use "AlphaFold for Delivery" as an ambition or positioning phrase only. It must not be presented as achieved maturity, standardization, adoption, or performance.
Permea must not claim:
- completed wet-lab validation unless documented
- clinical efficacy
- therapeutic efficacy
- universal delivery prediction
- production-grade drug delivery platform status
- dataset redistribution permission without source/license approval
Benchmark claims must remain scoped to dataset, split, metric, evidence level, and provenance state.
To report conduct concerns, use the project maintainers or the reporting channel named by the current repository maintainers.
Until a dedicated reporting address is published, open a minimal issue only if it can be done without exposing private, sensitive, or confidential information. For sensitive matters, contact a maintainer directly through an appropriate private channel.
Maintainers may take action to protect the community and project integrity, including:
- asking for wording or behavior changes
- editing or removing unsupported claims from project-managed spaces
- limiting participation in a thread
- closing issues or pull requests
- escalating to repository or organization administrators
Enforcement should be proportionate, documented where appropriate, and focused on maintaining a respectful open scientific environment.