# Collaboration and reviews

## How to contribute

See [CONTRIBUTING.md](../CONTRIBUTING.md) for mechanics (fork, branch, PR, checks).

**Anti-sloppiness playbook:** [QUALITY_BAR.md](QUALITY_BAR.md) — CI gates, review lanes, definition of done, exemplars.

## Review expectations

- **Substantive changes to methods or findings:** require at least one reviewer familiar with the domain thread (or explicit maintainer review if the team is small).
- **Docs-only:** may be fast-tracked; still run CI.
- **Data or ethics-sensitive paths:** require explicit review before merge.

## Communication

- Prefer issues for public discussion tied to a decision record.
- Use PR descriptions to link issues, hypotheses, and prior artifacts.

## Labels (suggested)

Maintain GitHub labels aligned to methodology. Full palette, colors, and milestone ideas: [LABELS_AND_MILESTONES.md](LABELS_AND_MILESTONES.md). Core set: `hypothesis`, `methods`, `finding`, `docs`, `tooling`, `blocked`, `needs-evidence`.