---
name: feature_release_docs_policy
description: "Standing rule: every feature we build needs customer-facing release notes AND a docs page; where/how to author both"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: bca80928-e9c5-44f0-9efe-65e2971ea8e4
---

Every feature built in evolution requires **(1) customer-facing release notes** and **(2) an end-user documentation page**. Treat both as part of finishing the feature, not optional extras — produce them without being asked again.

**Why:** Shane confirmed this is a standing expectation for all feature work, so these shouldn't need re-exploring or re-prompting each time.

**How to apply:**

*Release notes* — managed in-app via the **Release Notes** screen (master `evolution` DB, `releasenotes` table, accessed with `EVO::`). Files: `support_releasenotes_add.inc` (form), `support_releasenotes.php` (handler, action `?addrelease`), `releasenotes_customers.inc` (customer-facing display). The notes are normally entered through the UI tied to a ticket — **do NOT INSERT into `releasenotes` directly unless explicitly asked**. Instead deliver copy shaped to the form fields so it can be pasted in:
- `feature_name` (text)
- `type` — one of: Release Note · Coming Soon · Latest News · Known Issue
- `feature_description` (textarea; customer-facing, benefit-led prose)
- `feature_module` (text, e.g. "Sales / Invoicing")
- `support_doc_required` (Yes/No — set Yes and point to the docs page)

*Documentation* — add a page per [[docs_authoring]] (bootstrap+template pattern under `evolution/docs/<section>/<name>.php`) and hand-add a sidebar `<li>` in `docs/includes/sidebar.inc.php` under the right `<div class="h5">Section</div>` using `isActive("<file>.php")`.

Precedent: the Cash Sales feature shipped `docs/modules/cash-sales.php` + sidebar entry, with release-note copy delivered in the form's shape.