{"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\nRefresh evidence and review in one ordered run:\n\n```bash\npnpm launch:evidence -- --base-url=https:// --iiif-tile-url=https://\npnpm launch:evidence:production -- --base-url=https:// --public-read-base-url=https:// --iiif-tile-url=https://\n```\n\nThe evidence runner starts with `pnpm hardening:pen-dr` so security-audit and\nPostgres DR artifacts are fresh before deployment preflight and launch review\nread them. It continues after individual failures, writes\n`artifacts/launch/launch-evidence-latest.json`, and then runs the launch review\nso operators can see every red step in one packet.\nUse `--step-timeout-ms=` for bounded evidence runs that should\nrecord a failed step and still write the launch evidence packet when a nested\ncommand runs too long.\nEvery failed or skipped step in `launch-evidence-latest.json` includes\n`nextEvidenceNeeded` plus a `remediation` object naming the command to rerun and\nthe artifact that must turn green. Skipped k6 samples are therefore preserved as\noperator-visible launch evidence debt instead of being silently treated as a\nproduction-ready SLO proof.\nWhen `--fail-fast` stops after the first failed step, the remaining planned\nsteps are still written as `skipped` records with their remediation fields so the\npacket preserves the full launch-readiness checklist instead of leaving later\nchecks missing.\n\n## Artifacts\n\n- latest packet: `artifacts/launch/launch-review-latest.json`\n- latest evidence runner packet: `artifacts/launch/launch-evidence-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 evidence runner packet: `artifacts/launch/runs/launch-evidence-.json`\n- per-run controlled beta packet: `artifacts/launch/runs/beta-readiness-.json`\n\nFor launch evidence runner packets, inspect the per-step remediation fields when\n`status` is `fail` or `skipped`:\n\n- `nextEvidenceNeeded`: the exact proof still required for that launch lane.\n- `remediation.command`: the command an operator should rerun after fixing the\n blocker.\n- `remediation.artifact`: the artifact path that should show the new evidence.\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- crawler preview smoke evidence: `artifacts/launch/crawler-preview-latest.json` from `pnpm smoke:crawler-preview`\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- crawler-preview smoke is missing or fails Open Graph, Twitter, canonical URL, or preview image fetchability checks\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, crawler-preview, 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

Refresh evidence and review in one ordered run:

\n
\npnpm launch:evidence -- --base-url=https://<deploy-host> --iiif-tile-url=https://<iiif-tile>\npnpm launch:evidence:production -- --base-url=https://<shareable-url> --public-read-base-url=https://<shareable-url> --iiif-tile-url=https://<iiif-tile>\n
\n

The evidence runner starts with `pnpm hardening:pen-dr` so security-audit and

\n

Postgres DR artifacts are fresh before deployment preflight and launch review

\n

read them. It continues after individual failures, writes

\n

`artifacts/launch/launch-evidence-latest.json`, and then runs the launch review

\n

so operators can see every red step in one packet.

\n

Use `--step-timeout-ms=<milliseconds>` for bounded evidence runs that should

\n

record a failed step and still write the launch evidence packet when a nested

\n

command runs too long.

\n

Every failed or skipped step in `launch-evidence-latest.json` includes

\n

`nextEvidenceNeeded` plus a `remediation` object naming the command to rerun and

\n

the artifact that must turn green. Skipped k6 samples are therefore preserved as

\n

operator-visible launch evidence debt instead of being silently treated as a

\n

production-ready SLO proof.

\n

When `--fail-fast` stops after the first failed step, the remaining planned

\n

steps are still written as `skipped` records with their remediation fields so the

\n

packet preserves the full launch-readiness checklist instead of leaving later

\n

checks missing.

\n

Artifacts

\n
  • latest packet: `artifacts/launch/launch-review-latest.json`
  • latest evidence runner packet: `artifacts/launch/launch-evidence-latest.json`
  • latest controlled beta packet: `artifacts/launch/beta-readiness-latest.json`
  • per-run packet: `artifacts/launch/runs/launch-review-<timestamp>.json`
  • per-run evidence runner packet: `artifacts/launch/runs/launch-evidence-<timestamp>.json`
  • per-run controlled beta packet: `artifacts/launch/runs/beta-readiness-<timestamp>.json`
\n

For launch evidence runner packets, inspect the per-step remediation fields when

\n

`status` is `fail` or `skipped`:

\n

blocker.

\n
  • `nextEvidenceNeeded`: the exact proof still required for that launch lane.
  • `remediation.command`: the command an operator should rerun after fixing the
  • `remediation.artifact`: the artifact path that should show the new evidence.
\n

Inputs

\n

The launch packet reads:

\n
  • `artifacts/launch/deployment-preflight-latest.json`
  • `artifacts/exit-gate/era-c-exit-gate-latest.json`
  • `artifacts/security/pnpm-audit-summary.json`
  • `config/security-audit-baseline.json`
  • `artifacts/dr-drill/latest.json`
  • `artifacts/smoke/public-trust/summary.json`
  • crawler preview smoke evidence: `artifacts/launch/crawler-preview-latest.json` from `pnpm smoke:crawler-preview`
  • a11y evidence: `artifacts/launch/a11y-latest.json` from `pnpm a11y:check`
  • explore smoke evidence: `artifacts/launch/explore-smoke-latest.json` from `pnpm smoke:explore:matrix`
\n

The evidence paths can be overridden with:

\n
  • `METAMUSEUM_A11Y_EVIDENCE_PATH`
  • `METAMUSEUM_EXPLORE_SMOKE_EVIDENCE_PATH`
\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
  • deployment preflight is missing, stale, wrong-target, warning, or failing
  • Era C exit gate is missing, stale, or failed
  • security audit exceeds the committed baseline
  • DR drill is missing, stale, failing, or lacks verified Postgres restore proof
  • public-trust smoke screenshots are missing or have pixel-diff failures
  • crawler-preview smoke is missing or fails Open Graph, Twitter, canonical URL, or preview image fetchability checks
  • a11y or explore smoke evidence is missing or not passing
\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
  • `blocked`: launch-review blockers or deployment-preflight failures remain.
  • `rehearsal-ready`: deployment and hardening are not blocked, but live beta still needs required smoke/deployment evidence.
  • `live-beta-ready`: deployment, hardening, public-trust, crawler-preview, a11y, and explore smoke evidence are green; remaining warnings are accepted controlled-beta evidence collection limits.
\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":"1d414c314ee3957084a8768d57ca0098d0c504bd4335ded9d73d9a8072820611","checksumPrefix":"1d414c314ee3","anchorCount":5,"lineCount":127,"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"}