Release Notes

Planwright builds release notes from completed objectives. When an objective reaches Done, it joins the workspace changelog automatically — nothing to write, nothing to maintain.

Every completed objective is already a structured record: a title, a strategic classification, an initiative, an accepting human, an agent kind, and a verified diff. Planwright assembles these into a changelog entry at completion time. The engineering team doesn't write release notes — they write objectives. Planwright produces the notes as a byproduct of work they were already doing.

Each release note entry draws from the objective record — not from a commit message someone typed at 11pm.

1. TitleThe objective title, verbatim. Because objectives are written to describe an outcome — not an implementation — they read naturally in a changelog without rewriting.
2. Strategic classificationBUILD, GROW, TRUST, or SCALE. Lets readers see at a glance whether a release was heavy on infrastructure, growth-facing features, compliance work, or scaling improvements.
3. InitiativeThe initiative this objective belonged to, if any. Groups related entries across a release window without requiring manual tagging.
4. Diff summaryA brief summary of what the agent changed, drawn from the agent run record and verified against the linked PR or commit. Links directly to the audit record for teams that want full traceability.
5. Accepted byThe human who reviewed and accepted the objective. Establishes a named chain of custody — every change in the changelog has a human who signed off on it.

The workspace changelog aggregates all completed objectives across every project. Filter by project to scope what's visible.

By default, the release notes view shows everything that shipped across the workspace in reverse chronological order. For teams running multiple projects — a web app, a mobile app, an internal platform — the project filter lets you isolate one area. Filtering applies to both the board-side view and the public URL: a project-scoped public link shows only that project's entries.

Every workspace has a stable public URL for its release notes. It updates live as objectives complete.

Not every completed objective belongs in a customer-facing changelog. Suppress individual entries from the public view without touching the audit record.

By default, completed objectives are queued for publication — not published immediately. A workspace editor marks entries as published before they appear on the public URL. Suppressing an entry removes it from the public view but leaves the audit record intact. The audit chain is append-only: suppression is a publication flag, not a deletion. Internal objectives, infrastructure work, and security patches can stay off the public page while remaining fully traceable in the audit history.

The public URL is designed for everyone who cares what shipped but doesn't live in the board — product leads, design, leadership, customers.

The engineering tax of writing release notes for a non-technical audience is real: sprint summaries, Confluence pages, Slack digests summarizing what agents shipped this week. Planwright eliminates this. When an objective is written to describe an outcome — "Users can now filter the dashboard by project" — that title is already the release note. The public URL is a live artifact produced by the planning process itself. Share it with a product manager, a customer success team, or a customer. No additional writing required.