Project Shadow depends on disciplined disagreement. Participants may challenge the project, its evidence, its methods, its maintainers, and one another. Such criticism should be treated as evidence to examine, not hostility to punish.
- Be specific about the claim, artifact, path, test, or decision at issue.
- Separate observed facts, interpretations, uncertainty, and recommendations.
- Correct mistakes openly and preserve the evidence needed to understand them.
- Protect personal data, private evidence, credentials, and exploit details.
- Respect different experience levels and make technical reasoning inspectable.
- Stop escalation when harm, coercion, harassment, or unsafe disclosure appears.
Harassment, threats, stalking, discriminatory abuse, sexualized attention, doxxing, deliberate exposure of private information, knowingly fabricated evidence, retaliation for good-faith criticism, and publishing exploit details after being directed to the private security channel are not acceptable.
For sensitive conduct reports, email projectshadowqa@protonmail.com with the
subject prefix [CONDUCT]. Do not place private evidence in a public issue.
Maintainers may remove content, limit participation, or refer a security matter
to the process in SECURITY.md. Decisions should be proportionate, documented
where privacy permits, and open to correction when new evidence appears.
The broader contact and correction policy is in
CONTACT_AND_CORRECTIONS.md.
This code governs participation only. It does not certify the project or authorize production or operational deployment.