{"id":"ops/launch-review","relativePath":"ops/launch-review.md","title":"Launch Review Packet","markdown":"# Launch Review Packet\n\n`pnpm launch:review` builds a machine-readable launch packet from the latest artifacts. It does not rerun heavy gates; it verifies that the evidence already collected is fresh, internally consistent, and safe to use for a launch decision.\n\n## Commands\n\nStaging / controlled beta review:\n\n```bash\npnpm launch:review\n```\n\nControlled beta go/no-go summary:\n\n```bash\npnpm launch:beta:readiness\n```\n\nFail-fast staging check:\n\n```bash\npnpm launch:review:check\n```\n\nProduction launch review:\n\n```bash\npnpm launch:review:production\n```\n\n## Artifacts\n\n- latest packet: `artifacts/launch/launch-review-latest.json`\n- latest controlled beta packet: `artifacts/launch/beta-readiness-latest.json`\n- per-run packet: `artifacts/launch/runs/launch-review-.json`\n- per-run controlled beta packet: `artifacts/launch/runs/beta-readiness-.json`\n\n## Inputs\n\nThe launch packet reads:\n\n- `artifacts/launch/deployment-preflight-latest.json`\n- `artifacts/exit-gate/era-c-exit-gate-latest.json`\n- `artifacts/security/pnpm-audit-summary.json`\n- `config/security-audit-baseline.json`\n- `artifacts/dr-drill/latest.json`\n- `artifacts/smoke/public-trust/summary.json`\n- a11y evidence: `artifacts/launch/a11y-latest.json` from `pnpm a11y:check`\n- explore smoke evidence: `artifacts/launch/explore-smoke-latest.json` from `pnpm smoke:explore:matrix`\n\nThe evidence paths can be overridden with:\n\n- `METAMUSEUM_A11Y_EVIDENCE_PATH`\n- `METAMUSEUM_EXPLORE_SMOKE_EVIDENCE_PATH`\n\nIf an operator needs to supply a manual evidence file, use this minimal shape:\n\n```json\n{\n \"generatedAt\": \"2026-06-10T00:00:00.000Z\",\n \"status\": \"pass\",\n \"summary\": \"Operator pasted the passing command output here.\"\n}\n```\n\nCommand evidence may use `status: \"warn\"` for staging-only blockers, such as a missing researcher smoke token. Use `pnpm launch:smoke-token` to generate/update the staging token without printing it, then copy `METAMUSEUM_TEST_ROLE_OVERRIDE_TOKEN` into both the staging server and smoke runner. Production launch review treats warning evidence as not passing.\n\n## Production Rules\n\nProduction launch review fails when:\n\n- deployment preflight is missing, stale, wrong-target, warning, or failing\n- Era C exit gate is missing, stale, or failed\n- security audit exceeds the committed baseline\n- DR drill is missing, stale, failing, or lacks verified Postgres restore proof\n- public-trust smoke screenshots are missing or have pixel-diff failures\n- a11y or explore smoke evidence is missing or not passing\n\nStaging review can warn on production-only blockers so controlled beta can proceed only to collect the missing evidence.\n\n## Controlled Beta Readiness\n\n`pnpm launch:beta:readiness` reads the latest launch review and deployment preflight artifacts, then classifies the staging decision as:\n\n- `blocked`: launch-review blockers or deployment-preflight failures remain.\n- `rehearsal-ready`: deployment and hardening are not blocked, but live beta still needs required smoke/deployment evidence.\n- `live-beta-ready`: deployment, hardening, public-trust, a11y, and explore smoke evidence are green; remaining warnings are accepted controlled-beta evidence collection limits.\n\nEra C 30-day SLO, uptime, activity-adoption, and KPI gaps are accepted warnings only for controlled beta. They remain production blockers.\n","sections":[{"level":2,"heading":"Commands","anchor":"commands"},{"level":2,"heading":"Artifacts","anchor":"artifacts"},{"level":2,"heading":"Inputs","anchor":"inputs"},{"level":2,"heading":"Production Rules","anchor":"production-rules"},{"level":2,"heading":"Controlled Beta Readiness","anchor":"controlled-beta-readiness"}],"html":"

Launch Review Packet

\n

`pnpm launch:review` builds a machine-readable launch packet from the latest artifacts. It does not rerun heavy gates; it verifies that the evidence already collected is fresh, internally consistent, and safe to use for a launch decision.

\n

Commands

\n

Staging / controlled beta review:

\n
\npnpm launch:review\n
\n

Controlled beta go/no-go summary:

\n
\npnpm launch:beta:readiness\n
\n

Fail-fast staging check:

\n
\npnpm launch:review:check\n
\n

Production launch review:

\n
\npnpm launch:review:production\n
\n

Artifacts

\n\n

Inputs

\n

The launch packet reads:

\n\n

The evidence paths can be overridden with:

\n\n

If an operator needs to supply a manual evidence file, use this minimal shape:

\n
\n{\n  "generatedAt": "2026-06-10T00:00:00.000Z",\n  "status": "pass",\n  "summary": "Operator pasted the passing command output here."\n}\n
\n

Command evidence may use `status: "warn"` for staging-only blockers, such as a missing researcher smoke token. Use `pnpm launch:smoke-token` to generate/update the staging token without printing it, then copy `METAMUSEUM_TEST_ROLE_OVERRIDE_TOKEN` into both the staging server and smoke runner. Production launch review treats warning evidence as not passing.

\n

Production Rules

\n

Production launch review fails when:

\n\n

Staging review can warn on production-only blockers so controlled beta can proceed only to collect the missing evidence.

\n

Controlled Beta Readiness

\n

`pnpm launch:beta:readiness` reads the latest launch review and deployment preflight artifacts, then classifies the staging decision as:

\n\n

Era C 30-day SLO, uptime, activity-adoption, and KPI gaps are accepted warnings only for controlled beta. They remain production blockers.

","updatedAt":"2018-10-20T01:46:40.000Z","checksum":"880e41ebcbe31c0c2bee075a4f8182ceccdcabeb71aacf9c62dc98729bcee417","checksumPrefix":"880e41ebcbe3","anchorCount":5,"lineCount":90,"rawUrl":"/api/docs/content?path=ops%2Flaunch-review.md","htmlUrl":"/docs?doc=ops%2Flaunch-review.md","apiUrl":"/api/docs/content?path=ops%2Flaunch-review.md"}