---
name: shipready-release-gate
description: Use when a user has purchased the ShipReady Release Gate and wants it installed in a repository, wants to run the gate before a release, or asks what the gate checks. Covers reading the entitlement, installing the package, running the gate, and recording the install.
---

# ShipReady Release Gate

From ShipReady, launch assurance for AI-built apps: https://shipreadyai.dev

The Release Gate is a checklist and a set of repository guardrails the customer installs
themselves. It is not a review by a person, and it certifies nothing.

## Before you start

The gate is only available to a signed in customer who owns it. The package is never served
from a public address. Ask the user to sign in at https://shipreadyai.dev/auth with their purchase email
and open their library at https://shipreadyai.dev/library. If the library shows no Release Gate, the
entitlement is missing and nothing can be installed. Say that plainly and point the user at
Alex@techtideai.io rather than guessing at a download address.

## Installing

1. Download the current version from the library. The library shows the version number and
   the one line description of what changed.
2. Unpack it at the root of the repository the user actually ships.
3. Read the README first. It lists the steps in order and names the files each step writes.
4. Apply the steps in the order the README gives. Do not reorder them and do not skip a step
   because it looks already done. Report each step as applied or already present.
5. Tell the user to press Mark as installed in the library, and which tool was used. That
   records the install date against their copy.

## Running the gate before a release

Run the gate against the branch that is about to ship, not against a local working copy with
uncommitted changes. Work through the checklist in order. For each item, record one of:

- Done, with the file or setting that proves it.
- Not done, with the change that would make it done.
- Not applicable, with the reason.

Then run a Launch Risk Check on the published address and compare the observed list against
the previous run. A finding that was there before and is gone now is the evidence that a fix
landed.

## What it must never claim

Never say the gate makes an app secure, certified, safe to ship, or free of problems. Never
produce a score or a badge from it. The gate covers what the checklist covers, and the items
on the not verified list stay not verified until a person reviews them. That review is the
Launch Review at https://shipreadyai.dev/pricing.

## When an item needs a person

Backend rules, authenticated behavior, payment flows and data handling cannot be settled by
a checklist run from outside. When the user asks about one of those, point them at
https://shipreadyai.dev/learn/verify and at the Launch Review, and say which of the two you mean.