Back to The Gateway

Release checklist

Release only when install reality, evidence, and public copy agree.

This checklist keeps The Gateway from launching with placeholder contacts, unsupported claims, or unclear operator boundaries.

Repository gate

License, README, security policy, contribution guide, support policy, issue templates, PR template, install guide, and release notes are ready.

Evidence gate

Demo, screenshots, install transcript, route/DNS checks, fallback checks, privacy posture check, and recovery drill are linked.

Copy gate

No internal targets, exact price ranges, unsupported maturity claims, or internal development terms appear in public docs. Known limitations stay visible.

Security gate

Security reports route through contact links and `SECURITY.md`; public issues should not collect vulnerability details.

Support gate

Support intake explains redaction, remote access, retention, credential custody boundaries, and operator approval.

Next action

Close the release gates in dependency order.

Start with license, contact endpoints, fresh-machine install evidence, rollback documentation, hardware matrix, and site QA checks before broad release.