f21977383b
# Conflicts: # docs/config-catalog.i18n.yaml # docs/subsystems/persistence.i18n.yaml # packages/session/session-persistence-jsonl/README.i18n.yaml # packages/session/session-persistence/README.i18n.yaml
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 model context 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.