# Release Checklist

The Gateway should not cut a broad public release until the repository, website, and operator evidence tell the same story.

## Required Gates

- License is selected and committed.
- `README.md` states pre-launch scope and current install expectations.
- `SECURITY.md`, `CONTRIBUTING.md`, and `SUPPORT.md` are present.
- Issue templates and PR template are present.
- Security reports are routed through contact links, not public vulnerability issues.
- Install guide is tested on a fresh machine.
- Rollback and recovery guide exists.
- Hardware matrix lists supported, partially supported, and untested modes.
- Public evidence page links to demo, screenshots, install transcript, route/DNS checks, fallback checks, and recovery drill.
- Support intake explains redaction, access, and retention boundaries.
- Privacy posture checklist exists.
- Support bundle redaction guide exists.
- Contact and intake privacy notes exist.
- Known limitations are public.
- Release notes template exists.

## Copy Gates

- No internal development terms in public product copy.
- No internal launch targets, private channel plans, or exact price ranges in public repo docs.
- No claims that The Gateway guarantees anonymity by itself.
- No mature proof wording unless the evidence page links to actual proof.
- No unsupported hardware or install claims.

## Operator Evidence Gates

- Route ownership behavior documented.
- DNS ownership behavior documented.
- Fallback behavior documented.
- Recovery path documented.
- Privacy posture check documented.
- Known failure modes documented.
- Redacted example support bundle documented.

## Release Notes Should Include

- Current supported deployment modes.
- Known limitations.
- Evidence links.
- Upgrade or rollback notes.
- Security/support contact path.
- Any breaking changes.