Release Comms

Release comms say what each audience needs to know about a release: customers, internal teams (support, security and controls, operations), and external parties (audit and regulators). Each draft is written from the release record, edited by the team, and approved before it is sent.

The five audiences

Customers — what changed, why it matters, how to use it, anything they need to do.

Support — what customers will see, likely questions, known issues, when to escalate.

Security & controls — changes to the control environment, the evidence behind them, the DPIA and the approvals.

Operations — what ships, deployment notes, what to monitor, the rollback signal.

Audit & regulators — a formal change record: scope, approvals with dates, the evidence trail, data protection.

Where the draft comes from

Each audience has its own writer. It drafts from a brief the server builds from the release: its work packages and what they are for, the Definition of Done evidence that passed them, their Delivery pages (test evidence, release notes, verification), the pull requests, the DPIA and who approved the release. Nothing is sent to the writer from your browser, and where the record does not say something the draft says so rather than guessing.

Approve, then send

Anyone in the studio can draft, redraft and edit. An owner or studio admin approves a draft once the release itself is approved; approved text is frozen, and Reopen takes it back to draft. Sending copies the approved text or downloads it as Markdown, and records who sent it and how. Sent is final.

All AI Product Studio documentation

Build v0.3.2 · deployed 2026-10-19T23:52:31Z