# Assyria | Editorial release review checklist

This checklist describes standards for future release editors. It does not show that any specific article has been signed off or independently reviewed. Publication changes must also update `data/project-roadmap.json` and, for significant public-facing releases or corrections, the traceable record in `data/editorial-revisions.json`.

## Substantive evidence checks

- [ ] Exact target article, sections and changed claims have been identified.
- [ ] The Bible is cited as the primary account for statements about what Scripture reports, with exact verses.
- [ ] Biblical reports are not silently treated as independent archaeological findings, and comparison sources retain their own evidential role.
- [ ] Direct inscriptions, administrative records, object IDs and editions are cited at the most precise level available.
- [ ] Literary genre, translation, dating disagreements and plausible competing interpretations are made visible.
- [ ] Every new section citation is included in the article's bibliography; source IDs and links are valid.
- [ ] The article and claim review records contain accurate qualifications and no invented independent approval.

## Rights, consent and privacy

- [ ] New text is original or appropriately licensed.
- [ ] Every image, map, recording, manuscript image and transcript has an identified provider and reuse right.
- [ ] Any personal testimony has separately documented permissions for recording, storage, research access and public reuse.
- [ ] Third-party personal details, protected media, credentials and private correspondence are absent from public repository data.
- [ ] Changes requiring a private custodian are deferred if no authorised secure process exists.

## Editorial release decisions

- [ ] Nature of the change is stated: addition, correction, clarification or withdrawal.
- [ ] Named specialist reviewers are shown only if their identities, scope, date and assessments have been documented and publication agreed.
- [ ] The affected article, public correction notice if relevant, source trails and roadmap accurately reflect the new state.
- [ ] Public revision ID and actual merged commit or pull request are recorded, not guessed.
- [ ] The release documentation explains what remains unverified.
- [ ] The code, HTML, source and local links pass both root and GitHub Pages subpath builds.
- [ ] Significant visual changes receive a real device or browser check when available; CI alone is not a visual proof.

## Recorded result (internal planning only)

- Release and proposed ID:
- Review participants and exact roles (if any):
- Evidence issues remaining:
- Rights issues remaining:
- CI checks and browser checks:
- Approved / deferred / returned for changes (do not check without an authorised reviewer):
- Merged commit and public correction notice (only after merge):

**No automatic approval:** A checked item here is not proof of specialist verification. Keep private review notes and any identifying details outside public Git.