Owned by Support

Release notes should translate engineering change records into user outcomes: what changed, who is affected, what an administrator must enable, and which limitations remain.

Documentation baseline · 30 July 2026

  • SOCK: Survey, Plan, Extract, and cited Ask documented as current; later canonical lifecycle stages remain unavailable.
  • Cockpit: native transcript rehydration documented; Codex remains disabled by default.
  • Command Center: lifecycle, four gates, Jira read-only behaviour, and beta placeholder pages documented.
  • Administration: enterprise auto-provisioning, Pending SSO activation, eager invitations, and feature inheritance documented.
  • SOCI: end-user capability remains coming soon; first-bundle project-admin workflow documented separately.

Release-note template

  1. 01

    Outcome

    State the user-visible result in one sentence.

  2. 02

    Availability

    Name desktop/web surface, role, feature flag, and rollout qualification.

  3. 03

    What changed

    Describe behaviour, not implementation internals.

  4. 04

    What to do

    Give the smallest action needed from users or administrators.

  5. 05

    Known limits

    Name important boundaries and recovery guidance.