23 lines
866 B
Markdown
23 lines
866 B
Markdown
# Contributing
|
|
|
|
## Add or change an entity
|
|
|
|
1. Confirm the entity from an official source.
|
|
2. Add or update one row in `data/entities.csv`.
|
|
3. Update the appropriate human-readable address-book page.
|
|
4. Set `verified_at` to the UTC date you checked the source.
|
|
5. Run `make validate`.
|
|
6. Explain the evidence and scope in the commit message or pull request.
|
|
|
|
## Editorial rules
|
|
|
|
- Prefer concise, neutral descriptions.
|
|
- Use role-based public contact or directory links, not private personal data.
|
|
- Do not call a commercial dataset exhaustive unless its publisher establishes that claim.
|
|
- Mark uncertainty explicitly.
|
|
- Keep category names aligned with `docs/03-taxonomy.md`.
|
|
|
|
## Definition of done
|
|
|
|
A change is done when the structured record validates, the readable directory agrees with it, the source is primary where possible, and limitations are documented.
|