---
name: release-notes-enduser-voice
description: "BINDING release-notes voice standard: end-user UX effects only, impersonal voice, user-facing nouns — codified in RELEASE-RUNBOOK.md step-2 + deployah role"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: 89cc9038-e5d9-429e-b4a9-40fba8af71ee
---

Operator-directed 2026-07-17 (revising the v0.36.0 notes): CHANGELOG / release-note
entries are for END USERS and must read succinctly for them.

**Why:** the first v0.36.0 notes leaked implementation vocabulary (`replay`,
`subscriber`, `serve lease`, `stream lock`, `DISPATCH_EV`), addressed the reader as
"you", and sold an internal-diagnostics change as an **Added** feature — all foreign
/ wrong-audience for a public changelog.

**How to apply:**
- State the **observable UX effect**, never the mechanism. No mechanism nouns from
  the fix's own vocabulary.
- **Impersonal voice** — avoid "you"/"your"; describe the software's behavior; use
  "users" only if a subject is unavoidable. Pattern: *"Improved the stability of X.
  Previously, Y."*
- **Product's user-facing nouns** — "attached sessions" (reached over `spt rc`), not
  "remote sessions"; match the CLI vocabulary (controller, viewer, attach, daemon).
- **Internal-diagnostics → one line under Internal** (e.g. "Improved logging
  granularity for attached endpoints"); never an Added feature.

Codified durably in `docs/RELEASE-RUNBOOK.md` step-2 (checked-in, dual-audience,
CI-gated) AND the deployah endpoint role (renders first at start-transition). The
v0.36.0 CHANGELOG + published GitHub Release body were rewritten to match (PR #21,
body-only edit — no re-tag/re-sign). Kin: [[changelog-scope-vs-commit-range]],
[[public-docs-version-not-milestone]], [[v0360-published]].