Tianyi Cui
a7a5be1703
Run the dsh-archive-agent-notes audit over every active Agent Note on current master, judging each record by whether its rationale still guides work rather than by size or age. - Archive 453 implemented bilingual triplets (417,882 English words): completed UI chrome, narrow adapters, closed bug fixes, implementation walkthroughs whose package READMEs, docs pages, generators, or successor notes now carry the useful behavior, and 51 records fully superseded by a later active note. Keep 201 implemented notes whose ownership rules, negative guarantees, durable or wire semantics, security rules, reintroduction conditions, or still-tempting rejected alternatives remain useful. - Reject 7 proposals whose premise is gone or whose work shipped in amended form under other records; delete 2 rejected notes that no longer prevent a plausible mistake. - Retarget every remaining inbound link to the archived path, and repair active prose that named an archived record as the owner of a live fact: parenthetical citations drop, ownership sentences redirect to the README, docs page, or active note that states the fact, and history citations say so. Chinese files link the English archived path because the pairing gate treats the frozen tree as outside the bilingual corpus. - Seal 1,359 new frozen artifacts; existing seals are unchanged and outbound links from archived notes are neither inspected nor repaired. - Regenerate docs/config-catalog.md after the hook-bridge comment edits shifted two source line numbers.
description, kind
| description | kind |
|---|---|
| The feedback package group: user feedback on sessions and assistant messages, for users and maintainers choosing, composing, or debugging feedback capture. | package-group |
feedback/ — recorded human feedback
English | 中文
Summary
The feedback group collects human opinions about the harness's work: users can submit a free-text remark about a whole session, and rate or annotate individual assistant messages. Neither kind of feedback reaches the model — these are signals about the output, never input to it. Users record a session remark with the /feedback command; product surfaces read and change per-message ratings through the messageFeedback service. The two packages are independent: session remarks and per-message ratings do not interact. This page maps the group; the package READMEs and the feedback subsystem page own the per-package contracts.
Table of Contents
Packages
| Package | Role |
|---|---|
command-feedback |
A /feedback command that records a free-text session remark with one command, without a model turn |
message-feedback |
Per-message ratings and notes, served to product surfaces through the messageFeedback service |
Session remarks are a one-way signal: recording one is safe at any point in a conversation and never changes what the model sees. With a feedback-gated sharing policy, recording a session remark is what releases the session for sharing.
Per-message ratings and notes are stored with the session, survive restarts, and never appear in model history or telemetry.
Related documentation
- Feedback subsystem — the message-feedback types, service contract, and Web consumer.
- Session telemetry subsystem — the sharing policy disclosed by the
/feedbackacknowledgement. - Anonymous user identity — the per-harness-home id embedded in the feedback acknowledgement.
Dev Note
None.