Use case
Planned
Release notes
Turn a run's approved artifacts into release notes — drawn from what actually shipped, not written from memory.
The stage, and what it produces
What it is
Because each stage of a run produces a reviewed artifact, the raw material for release notes already exists. Drafting them from those artifacts, for a human to approve, is a natural fit — and one we mark honestly as not yet shipped.
Release notes · v1.4 From shipped artifacts
- Checkout: idempotent payments
- Fix: expired-card retry path
- Perf: 120ms faster settlement
- Docs: payments API updated
Illustrative — produced, reviewed and approved before the next step.
In a run
What the stage runs through
- Draw from the approved artifacts of the run
- Draft notes grouped by what changed
- A human edits and approves
- Publish, with the source traceable
Works with
The parts of the platform it leans on
Where it stands. Exploratory — it depends on the run producing the artifact chain, which is Planned.
Turn this stage into a governed output
Start with what ships today, and grow into the full run as it lands.