# Contribution Compass

> Evidence-first project updates and contribution discovery. Collection performs no LLM inference.

## Start here

- [Contribution leads](https://amk9978.github.io/contribution-compass/api/v1/opportunities.json)
- [Project news](https://amk9978.github.io/contribution-compass/api/v1/news.json)
- [Project news JSON Feed](https://amk9978.github.io/contribution-compass/news/feed.json)
- [Project news RSS](https://amk9978.github.io/contribution-compass/news/feed.xml)
- [Versioned catalog](https://amk9978.github.io/contribution-compass/api/v1/index.json)
- [JSON Feed](https://amk9978.github.io/contribution-compass/feed.json)
- [RSS Feed](https://amk9978.github.io/contribution-compass/feed.xml)
- [MCP setup](https://github.com/amk9978/contribution-compass/blob/main/docs/MCP.md)
- [Human contribution view](https://amk9978.github.io/contribution-compass/contribute/)

## Interpretation rules

- Signal URLs are primary GitHub evidence.
- Observation Events form the factual trail of discovered and changed Signals.
- Release highlights are extracted from original notes; public upcoming items are not commitments.
- Hacker News entries are community discussions, not maintainer evidence or endorsement.
- Maintainer-Invited Leads have explicit invitation labels.
- Triage Leads are lower-confidence and are not maintainer-approved work.
- Re-check the live issue for state, assignment, scope, and contribution policy.
- Never invent maintainer intent, project importance, or contribution acceptance.