# Repository Readiness

The Gateway should not be promoted as a broad public open-source install until the repository can support early operators without ambiguity.

## Required Before Public Repository Launch

- License selected and committed.
- `README.md` explains product scope, pre-launch status, install path, and support boundaries.
- `SECURITY.md` explains disclosure and support evidence rules.
- `CONTRIBUTING.md` explains contribution scope and privacy boundaries.
- `SUPPORT.md` explains support scope and escalation path.
- Install guide and rollback guide exist.
- Hardware matrix exists for primary, embedded, portable, appliance, and relay scenarios.
- Public evidence checklist links to screenshots, demo, test summary, recovery drill, and install transcript.
- Privacy posture checklist and support bundle redaction guide exist.
- Known limitations, contact privacy notes, and release notes template exist.
- Issue templates exist for bug report, hardware report, install report, documentation fix, and security contact links.
- Release checklist and issue label guide exist.

## Do Not Publish Without

- A selected license.
- A working contact address.
- A fresh-machine install pass.
- A documented rollback path.
- Clear anonymity and privacy limitations.
- Redaction guidance for logs, topology, and support bundles.
- Public issue routing that blocks blank issues and redirects vulnerability reports away from public issues.

## First Issue Labels

- `install`
- `hardware`
- `dns`
- `routing`
- `privacy-posture`
- `recovery`
- `documentation`
- `good first issue`
- `needs evidence`
- `security-boundary`

## Next action

- Open the [site QA gate](./site-qa.md) after the repository launch files are in place so publication checks cover metadata, noindex rules, support paths, and browser rendering.