Contributor Guide

Help by making the public record cleaner.

Contributions are useful when they improve source coverage, correction quality, duplicate detection, or school metadata without introducing private evidence or unsupported claims.

Ways to Contribute

Accepted Sources

Rejected Material

Submission Workflow

Use the submit page to prepare a structured packet. The packet can be copied into the appropriate GitHub issue template when the repository is public and ready for outside intake.

Review Standard

A submission does not become a public record until a reviewer confirms the source URL, school, date, category, affected community, attribution language, verification status, confidence label, and privacy risk.

Correction Standard

Corrections must identify the record ID, the disputed field, the requested change, and a public source supporting the change. Accepted corrections regenerate record hashes, dataset hashes, release notes, source audit metadata, and the public changelog.

Partner and Reviewer Path

Organizations, researchers, journalists, student groups, and civil-rights reviewers can help by reviewing methodology, identifying missing source categories, auditing classification rules, testing the dataset against a narrow research question, or checking whether the Research Guide prevents overclaiming. The Reviewer Brief gives outside reviewers the shortest entry point, and the Trust & Review Packet defines the broader review path. Acknowledgments should appear only after documented review or collaboration.

Reviewer Entry Points

Local Data Workflow

Code or data contributors should read docs/contributing.md, then run `npm run prepare:data` and `npm run check` before proposing dataset changes.

Contributor Rule

If a contribution would make the dataset less public, less neutral, less attributable, or less auditable, it does not belong in the MVP.