Changelog
Release notes as an operational history, not a legacy feed.
The changelog remains public and tied to current product routes, docs, and source references.
Editorial Utility
The changelog is a release route, not a disconnected archive.
It helps the reader understand what changed and where to continue next.
Release Scope
What the public changelog communicates
Release notes stay factual, scoped, and linked to product routes or docs.
Utility surface
Current status
Summarize meaningful public changes without creating a second design language for release notes.
Source of truth
Link changes back to product pages, docs, or repo-backed evidence wherever possible.
Historical framing
Keep older milestones as history, but do not let them compete with the active product narrative.
Reading routes
Release notes connect to current public routes.
Route readers from change history into the relevant product or documentation route immediately.