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 change summary are ready.

Evidence gate

Demo, screenshots, install transcript, route/DNS checks, fallback checks, privacy posture check, and recovery drill are linked. Screenshot handling is explicit: screenshots use realistic synthetic values and note the claim each image supports.

Copy gate

No internal targets, exact price ranges, unsupported maturity claims, private paths, temporary hosts, or unsupported promises appear in public docs. Known limitations stay visible.

Artifact gate

Published assets avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions before release.

Security audit

Security checks report no unresolved high-severity issues before broad release.

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.

Host routing gate

Confirm public host routing, redirects, canonical metadata, and support paths all point visitors to https://thegateway.pro/ before broad launch.

Release proof

Attach screenshots that prove the release gates are observable.

Redacted Gateway dashboard showing route, DNS, tunnel, device, and backup status cards
Evidence gate Posture is visible.

Shows the summary surface that should back route, DNS, tunnel, device, backup, and readiness claims.

Redacted Gateway routing policies screen
Install gate Traffic intent is named.

Shows the route and fallback policy surface that should be captured before release approval.

Redacted Gateway backup and recovery screen
Recovery gate Rollback has a surface.

Shows the backup and recovery view that should support release rollback evidence.

Next action

Close the release gates in dependency order.

Start with license, evidence, contact endpoints, fresh-machine install proof, rollback documentation, hardware matrix, publication checks, and public host routing before broad release.