Select and commit the license, publish release notes, and make pre-launch status visible anywhere install expectations are set.
Repository readiness
Open-source launch should give early operators enough context to act safely.
This is the public repository gate for The Gateway: license, support scope, install evidence, contribution boundaries, and privacy claims must be clear before broad distribution.
Publish install, rollback and recovery, hardware matrix, route/DNS verification, fallback checks, and first-run evidence.
Keep support access explicit, time-limited, revocable, and logged. Document what support will not do.
Use templates for bugs, installs, hardware reports, documentation fixes, PRs, and security contact links.
Explain how The Gateway helps verify routing, DNS, fallback, and leak behavior without promising anonymity by itself. Use the posture checklist.
Require redaction for logs, screenshots, support bundles, topology, private hostnames, and account identifiers before public submission.
License, security policy, contribution guide, support policy, install guide, rollback guide, hardware matrix, issue templates, release checklist, and proof artifacts are present.
Contact addresses are placeholders, install has not passed on a fresh machine, rollback is undocumented, or anonymity/privacy limits are vague.