docs(governance): prepare public issue creation package

docs/public-issues/004-legal-rightsholder-package.md

@@ -0,0 +1,67 @@
+# Public issue template 004
+
+## Title
+
+[legal] Prepare rightsholder evidence package
+
+## Labels
+
+`legal`, `registry`, `docs`
+
+## Purpose
+
+Prepare the rightsholder and legal evidence checklist needed before any future
+Russian software registry submission.
+
+## Background
+
+Technical readiness documentation does not replace legal confirmation. The
+rightsholder package remains pending until reviewed by the responsible party.
+
+## Scope
+
+- Prepare a rightsholder evidence checklist.
+- Identify ownership and license evidence to collect.
+- Document legal review TODOs.
+- Keep public wording conservative.
+
+## Non-goals
+
+- No legal conclusion by engineering.
+- No claim that registry submission is complete.
+- No publication of confidential contracts or personal data.
+
+## Acceptance criteria
+
+- Checklist of required legal evidence exists.
+- Ownership evidence categories are documented.
+- Open legal questions are recorded.
+- Public docs avoid certification and registry-completion claims.
+
+## Evidence required
+
+- Legal checklist document.
+- Rightsholder evidence inventory in non-sensitive form.
+- Dependency/license summary reference.
+- Legal review status note.
+
+## Safety/privacy guardrails
+
+- Do not publish passport data, signatures, contracts or confidential legal
+  documents.
+- Do not expose personal data of representatives.
+- Use references to private evidence storage when needed.
+
+## Registry-positioning guardrails
+
+- Do not claim legal readiness until formal review is complete.
+- Do not claim completed Russian software registry submission.
+- GitHub issues are public tracking, not legal evidence.
+
+## Checklist
+
+- [ ] Draft rightsholder evidence checklist.
+- [ ] Map ownership evidence categories.
+- [ ] Reference dependency/license documents.
+- [ ] Record open legal questions.
+- [ ] Review public wording for forbidden claims.