Patterns
Feedback & Correction
Patterns for collecting reviewer feedback on agent responses — thumbs rating, inline corrections, numeric scales, behavioral consequences, and feedback history.
Rating
Thumbs Feedback
Quick signal from the reviewer on response quality. Thumbs up confirms accuracy. Thumbs down opens a correction flow for structured remediation.
The project brief defines 23 requirements across 5 classes. implementation notes summarize the workflow behavior and open dependencies. I've mapped each requirement to its corresponding test case in the review plan.
| State | Trigger | Behavior |
|---|---|---|
| Neutral | Default | Thumbs visible at half opacity, no selection |
| Positive | Thumbs up clicked | Brief green flash confirms, selection persists |
| Negative | Thumbs down clicked | Correction textarea expands below the message |
| With Correction | Submit button or Cmd/Ctrl+Enter | Textarea pre-filled, submit records the correction |
Editing
Inline Correction
Direct editing of agent prose when a specific factual error is identified — typically an incorrect launch plan reference or misquoted launch requirement.
The launch readiness plan requires dedicated support plan for issue triage procedures. This pattern ensures that the team has an explicit process to track and correct issues reported by users.
| State | Visual | Behavior |
|---|---|---|
| Original | Error text with subtle highlight + edit button | Clicking the edit button transitions to corrected state |
| Corrected | Replacement text with green-tinted highlight | Applied tag appears with before → after summary |
Assessment
Rating Scale
Numeric quality rating for agent responses, used to build a calibration dataset over time. More granular than thumbs, less intrusive than a full correction.
Based on the launch policy, the product must implement Export workflow for CSV and JSON exports and Retention setting for account retention. Both are covered by the ACME export service's internal platform approval.
| Rating | Meaning | Agent Response |
|---|---|---|
| 1 | Incorrect or harmful | Flagged for immediate review, excluded from training |
| 2 | Mostly wrong | Queued for regeneration with guided corrections |
| 3 | Partially correct | Logged as neutral — no behavioral change |
| 4 | Good with minor issues | Reinforced with small adjustments noted |
| 5 | Excellent | Reinforced as-is, used as positive calibration example |
Adaptation
Behavioral Consequence
How the agent's behavior visibly changes after receiving feedback. Demonstrates the feedback loop closing — the reviewer sees the before and after side by side.
The launch readiness plan requires dedicated support plan for issue triage procedures. This pattern ensures that the team has an explicit process to track and correct issues reported by users of the product.
| State | Content | Purpose |
|---|---|---|
| Before | Original agent response with error | Establishes baseline for comparison |
| After | Corrected response with annotation | Shows the loop closing — feedback produces visible change |
Record
Feedback History
A running log of all reviewer feedback — positive signals, negative signals, and corrections. Provides an audit trail and training reference for the agent.
| Column | Content | Notes |
|---|---|---|
| Type | Positive / Negative / Correction | Icon-coded, monochrome |
| Timestamp | Date and time of feedback | Sorted most recent first |
| Message | Excerpt of the rated agent response | Truncated to one line, full text on expand |
| Detail | Reviewer's note or correction text | Visible only when row is expanded |