> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blips.network/llms.txt
> Use this file to discover all available pages before exploring further.

# First-Release Checklist

> Final public checklist for the first BLIPS Mintlify reference and Public Test Backend Try It release.

# 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
* `demo.blips.network` should not be bound until the BLIPSmvp runtime exposure path is ready
* keep the website, docs, and demo surfaces on separate subdomains with clear ownership

## 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 bind demo.blips.network

Bind `demo.blips.network` only after:

* the BLIPSmvp runtime is available on a stable host
* Cloudflare Tunnel or another approved exposure path is ready
* any gating or safety controls for the demo surface are in place
* the docs and website entry links are ready to point to the public demo hostname