`MAZENG-FT-50` · Product satisfaction feedback

Feature intent

Users need a clear way to submit scored comments, while product staff need privacy-respecting aggregate insight.

Why it matters

Users need a clear way to submit scored comments, while product staff need privacy-respecting aggregate insight.

The product team can identify satisfaction trends without exposing or allowing unauthorized changes to individual feedback.

Authenticated scored-comment submission with explicit result feedback.
Server-side validation and governed ownership, privacy, update, and deletion rules.
Authorized aggregate reporting with least-data access.

Acceptance

01
An authenticated user selects a valid score, submits comments, and receives explicit success or failure confirmation.
02
The server validates input and enforces ownership and privacy for reading, updating, deleting, and aggregating feedback.
03
Authorized product staff can view aggregate scores without unnecessary user data.

None recorded.

Legacy average-score behavior is unimplemented.
Legacy read, update, and delete paths lack adequate ownership or administrator checks.
Legacy UI clears comments before success and provides no completion result.

No authoritative Architecture tasks are linked.