Trust anchor
Repository, license, contribution guide, security model, install guide, and hardware matrix.
Launch plan
Open release, sponsor funding, and paid operations move together.
The launch is blocked on public repo assets, install docs, support rules, sponsor paths, runbooks, and test evidence.
Fresh-machine path
Installer, first-run policy, recovery path, and validation checklist before the install CTA becomes final.
Support without capture
Sponsor page, support intake, appliance waitlist, and MSP pilot path with clear support boundaries.
Evidence before scale
Demo, screenshots, public test summary, recovery drill, and first runbook execution report.
Do not broad-launch until install, rollback, support redaction, and public evidence are linked.
Share with selected technical operators only after install scope, redaction rules, and recovery expectations are clear.
Successful install reports, route/DNS evidence, recovery drill results, support boundaries, and operator reports.
Keep anonymity claims bounded, avoid VPN-only framing, and tie every paid offer to operational value.