Support and contribute
Use the route that protects the person.
Public-safe work belongs in the open ledger. Personal, security, conduct, and protected evidence does not.
GitHub issues are the current public-safe work ledger. This page helps route public questions, contributions, challenges, vulnerabilities, conduct concerns, and private information without turning the website into an account-support, provider-intake, research, or clinical system.
Public-safe routes
Problems, challenges, and contributions.
Use only public repository records and synthetic evidence. Do not disclose a diagnosis, disability, account identity, private experience, or another person’s information to establish affectedness.
Report a public-safe problem
Use a GitHub issue for public-safe product, documentation, accessibility, content, contributor, or governance work. Separate the problem from a preferred implementation and use synthetic evidence only.
Choose an issue form (opens in a new tab)Challenge an assumption or mechanism
Use the system-challenge form to dispute a public assumption, metric, incentive, architecture, policy, authority structure, or public claim. A complete replacement solution is not required.
Open a system challenge (opens in a new tab)Contribute implementation or validation
Read the contribution guide, select an issue, make the smallest coherent public-or-synthetic change, and preserve the Product Constitution and module boundaries.
Read the contribution guide (opens in a new tab)Review active work before asking
Check the integrated status and active issues first. Existing evidence, scope limits, or unresolved gates may already answer the question or identify the correct workstream.
Inspect current project status (opens in a new tab)Protected routes
Do not make private evidence public.
A deleted issue, edited comment, closed pull request, or rewritten branch may remain copied, cached, emailed, mirrored, or archived.
Security vulnerability or accidental disclosure
Do not open a public issue or reproduce protected material. Follow the private security policy using synthetic reproduction steps and the minimum necessary evidence.
Read private security reporting rules (opens in a new tab)Conduct or harassment concern
Conduct concerns and witness evidence belong in a private maintainer route. Do not place personal, health, correspondence, or moderation evidence in a public issue.
Read the Code of Conduct (opens in a new tab)Personal health, account, or private support matter
No account or private product-support system is live. Never publish person-specific health information, account details, support transcripts, screenshots, exports, or another person’s information.
Review the information boundary (opens in a new tab)This is not a private support desk.
- No account-specific customer-support system is operating.
- No health-advice, diagnosis, clinical triage, provider-intake, or research-enrollment service is operating.
- No private evidence should be pasted into public issues, pull requests, branches, logs, or previews.
- Issue reactions and comment volume are advisory signals, not votes or automatic roadmap authority.