Record an outcome for a past decision.
duh feedback [OPTIONS] THREAD_ID
The feedback command records whether a past consensus decision led to a successful outcome, a failure, or a partial result. This creates an Outcome record linked to the thread's latest decision.
Outcome tracking enables you to review which decisions worked and which didn't, building a history of decision quality over time.
| Argument | Required | Description |
|---|---|---|
THREAD_ID |
Yes | Full UUID or prefix (minimum 8 characters). |
| Option | Type | Required | Description |
|---|---|---|---|
--result |
choice | Yes | Outcome result: success, failure, or partial. |
--notes |
str | No | Optional notes explaining the outcome. |
Like show, you don't need the full 36-character UUID. Any unique prefix works:
duh feedback a1b2c3d4 --result successIf the prefix matches multiple threads, duh shows the ambiguous matches.
Record a successful outcome:
duh feedback a1b2c3d4 --result success --notes "Deployed to production, no issues"Record a failure:
duh feedback a1b2c3d4 --result failure --notes "Approach had scaling issues at 10k users"Record a partial result:
duh feedback a1b2c3d4 --result partial --notes "Worked for the API layer but not the frontend"Outcome recorded: success for thread a1b2c3d4
Outcomes are displayed when you inspect a thread with duh show:
Outcome: success - Deployed to production, no issues
- No thread matching:
No thread matching '<id>'. - Ambiguous prefix: Lists all matching threads
- No decisions:
No decisions found for thread <id>.