Public policy release gate
Human confirmations required before preview policies can become Public Beta service commitments.
link to this sectionPublic policy release gate
Public policy pages are live preview notices, not evidence that legal, governance, or support operations are complete. The Release Lead owns this gate before changing the release channel to Public Beta.
link to this sectionRequired confirmations
| Area | Required decision | Accountable review |
|---|---|---|
| Service identity | Legal operator name, address, contact details, and any registration disclosures | Release Lead and legal reviewer |
| Applicable law | Governing law, jurisdiction, age or capacity rules, consumer rights, and mandatory liability language | Legal reviewer |
| Privacy | Processing purposes, legal bases, processor list, international transfers, cookies, analytics, retention schedule, access, export, and deletion workflow | Privacy and operations reviewers |
| Copyright | Statutory agent or notice role if applicable, notice fields, counter-notice rules, repeat infringement approach, and jurisdiction coverage | Legal reviewer |
| Security | Named security owner, receipt route, severity handling, disclosure policy, responder coverage, and any safe-harbor or bounty statement | Security owner |
| Support | Named owner, staffed channels, hours or coverage, response targets, escalation, and status page | Operations owner |
| Governance | At least three named stewards, conflicts process, ordinary quorum, recusal, appeals, transparency format, and emergency review | Community and Release Lead |
| Content | License expectations, sensitive data rules, jurisdiction-specific illegal content duties, moderation overlays, and Artifact tombstone procedure | Content, legal, and protocol reviewers |
| Accessibility | Keyboard, mobile, dark mode, language clarity, and WCAG review of every public policy route | Web and accessibility reviewers |
Unknown values must remain unstated. A placeholder, personal assumption, or planned service cannot be converted into a public commitment merely to clear a release date.
link to this sectionEvidence bundle
Before approval, attach:
- The reviewed policy commit and rendered page captures at 390, 768, and 1440 pixels in light and dark themes.
- A route and sitemap check for all public policy pages.
- The responsible person's acceptance for each row above.
- Evidence that report, appeal, export, deletion, and security routes reach a real owner.
- The steward list and conflict declarations.
- The published status page and incident escalation route.
- A record of copy changes made after legal, security, privacy, community, and accessibility review.
link to this sectionRelease decision
The Release Lead records one of three outcomes: approved for Public Beta, approved with a dated and explicitly accepted limitation, or blocked. A blocked area cannot be hidden by changing page copy. The underlying service or ownership gap must be resolved.
After any material policy change, update the effective date, preserve the prior version in repository history, and decide whether users must accept the new Terms before contributing again.