Operator runbook

Pilot launch operational review

Use this before marking a reseller launch review ready in admin.

Review Order

1. Commercial gatePartner owner is attached, agreement is signed, package tier/source access is assigned, and any pilot waiver or commercial exception is documented.

2. Namespace gateAt least one namespace is approved or live, backend path is correct, pricing is set in USD, and interoperability matches the owner's intent.

3. Registrar gateWhite-label site has live or preview URL, support email, terms URL, custom-domain status, enabled namespaces, and partner dashboard access.

4. API and balance gateActive Partner API key exists, downstream env stores the key server-side, GFA Gems balance is funded, and wallet-to-partner top-up works.

5. Downstream smoke gateDownstream app can call preflight, payment/manual handoff creates the expected registration call, and one end-to-end registration is tested in demo mode before production launch.

6. Support gateAt least one support/modification request exists, admin queue updates status, and open launch blockers are documented in review notes.

Admin Record

Open Admin, use Pilot launch readiness, then open Evidence for the partner. System checks should already show partner, namespace, registrar site, API key, balance, agreement, failed provisioning, demo checklist, post-call decisions, and migration evidence.

Only check manual items after the downstream Railway/API environment has been verified, preflight works from the downstream app, a demo registration succeeds, and the operator approves launch.

Ready Definition

A pilot is ready when the admin evidence page has no unexplained system failures, downstream env and smoke test are verified, support/terms are visible to customers, and the latest launch review is saved as ready with concrete notes.