History

ZiyaZhang c61be60737 fix(feedback): address backend review gaps		2026-08-10 21:40:03 -07:00
..
command-feedback	docs: sync sharing-disclosure catalogs and module graph after rebase	2026-08-11 11:01:48 +08:00
message-feedback	fix(feedback): address backend review gaps	2026-08-10 21:40:03 -07:00
README.i18n.yaml	feat(feedback): add durable message feedback backend	2026-08-10 21:40:03 -07:00
README.md	feat(feedback): add durable message feedback backend	2026-08-10 21:40:03 -07:00
README.zh.md	feat(feedback): add durable message feedback backend	2026-08-10 21:40:03 -07:00

README.md

feedback/ — recorded human feedback

English | 中文

The feedback family exposes two deliberately separate contracts: an immutable remark in the canonical Session log, and editable feedback attached to one assistant message in a local sidecar. Neither form enters the model conversation.

Package	Role	ctx key
`command-feedback/`	Trigger-independent `feedback/record` event plus the human-facing `/feedback` producer	—
`message-feedback/`	Lifecycle-bound per-message rating/note sidecar plus Host `messageFeedback.list/put/delete` Remote contract	`messageFeedback`

A command feedback remark is log-only: it never enters the model surface or derived history. When mounted, dsh-session-telemetry-otel observes feedback/record to release a pending telemetry prefix or warn that disabled telemetry leaves the feedback local; capture itself remains independent of that policy.

Message feedback is not a Session event or projection. It remains in the storage-domain sidecar and causes no telemetry handoff. The Host Remote contract ships with the service; the client Remote aggregate mount and UI consumer are separately owned and deferred.