> ## Documentation Index > Fetch the complete documentation index at: https://prism.ntecdev.ai/llms.txt > Use this file to discover all available pages before exploring further. # SPEC-027 v0.1: Release coordination — versioned manifest, pinned images, upgrade verb > Release coordination — versioned manifest, pinned images, upgrade verb **Status:** `draft` · **Version** `0.1` · Filed 2026-04-22 Turns Prism's four moving parts (backend image, postgres, neo4j, mcp/server) into one coordinated release bundle. Architecture: release.yaml at repo root pins every component to exact tag + content digest. Backend image published to ghcr.io/franktewksbury/prism-backend on tag push. postgres/neo4j move from floating tags (pg16, 5.18-community) to exact (pg16.3.1, 5.18.0-community). New `prism upgrade` verb fetches manifest, diffs against running install, pulls pinned images, runs migrations, rolls back on failure. Major-version runbooks for pg + neo4j as ADRs. 5-PR arc: PR1 manifest schema + compose refactor, PR2 GHCR publishing pipeline, PR3 prism upgrade verb, PR4 pinned upstream migration, PR5 major-version runbooks. See docs/specs/spec-027-v0-1-release-coordination-manifest.mdx. Encloses Wave B template baking (TODO #23) — baked templates ride the backend image, methodology version pinned in manifest. Pairs with SPEC-028 (MCP server TS rewrite) — SPEC-028's npm package fills the mcp\_server block. 7 open questions: registry choice, cadence, versioning scheme, signing, multi-tenant blast radius, offline installs, repo ownership. Status: draft