First-Release Checklist

Use this checklist for the current public BLIPS docs and Public Test Backend Try It release.

1. Mintlify preview validation

import or connect the repo in Mintlify
confirm a .mintlify.app preview URL is created
confirm docs.json navigation matches the intended first-release structure
confirm generated OpenAPI pages appear only for the approved first-release endpoint set
confirm authentication, webhooks, reference/overview, reference/playground, and demo/* pages render in the expected locations

2. docs.blips.network binding

confirm docs.blips.network remains connected in Mintlify
confirm the Cloudflare docs CNAME still points at Mintlify
confirm SSL provisioning is healthy
confirm the public docs open on the custom domain before announcing changes

3. Cloudflare DNS expectations

docs.blips.network should point to Mintlify using the DNS target Mintlify provides
keep the public product demo on blips.network/demo
keep the public admin bootstrap on blips.network/admin/
keep the docs and website responsibilities clearly separated

4. When to enable real Try it

Real public Try It is enabled only when all of the following remain true:

the OpenAPI servers value points at https://public-test.blips.network
the public ingress target is stable
auth rendering is verified in Mintlify
request routing expectations are confirmed for the retained public boundary
public docs do not advertise /platforms, /internal/*, /payments/*, or legacy-only routes

This checklist does not describe the Public Test Environment as production-ready.

5. When to expose the guided demo

The guided demo should be considered ready for public use only after:

the website-owned /demo surface is healthy
the linked admin/bootstrap flow is healthy
any gating or safety controls for the demo surface are in place
docs and website navigation point to the current public demo route rather than the retired legacy hosts