Skip to content

5 · Ship

Merge the approved queue in a safe order, release, and tell the story — notes for users, knowledge base for the record.

  • cpo-pr — the PR contract: linked both ways to its card, carrying the evidence.
  • cpo-ship — merges what you approved, one card at a time, then runs post-merge operations.
  • cpo-announce — release notes written for users, framed by value.
  • cpo-kb — evergreen knowledge base pages that ride the card’s own PR.

Your approval merges. Only your word sets the last gate; then the queue ships without you watching.

The project’s runbook and workflows define branch targets, tags, and deployment effects. CPO follows them; ordinary PR approval does not authorize a separate promotion, release PR, or production command. Confirm what each authorized action triggers before running it.

The release · the PR · release notes · knowledge base pages. Then the loop closes: what shipped becomes what Discover learns from.

Ops runs the machinery; Product tells the story; you hold the key.