P2-03: ADR "Consequences" section is static boilerplate regardless of decision #13

New issue

Closed

opened 2026-06-16 13:57:01 +00:00 by Artur · 0 comments

Artur commented

2026-06-16 13:57:01 +00:00

Owner

Severity: P2 (Medium)
File: decider/adr.py lines 72-74

Problem

The ADR Generator always writes the same consequence:

## Consequences

- {decision} allows progress without user interruption

For abort decisions, this reads "abort allows progress without user interruption" — which is semantically wrong (abort literally stops progress). For ask_user decisions, the text is misleading.

Additionally, the consequences should differ per decision type:

auto_approve: "Action executed autonomously. Risk: low. Reversibility: high."
ask_user: "Decision escalated. User must approve before execution."
abort: "Action blocked. Risk assessed as too high for autonomous execution."

Fix

Implement decision-type-specific consequence text. Also consider using the LLM to generate substantive consequences for the auto_approve path (what becomes easier, what becomes harder).

**Severity**: P2 (Medium) **File**: `decider/adr.py` lines 72-74 ## Problem The ADR Generator always writes the same consequence: ``` ## Consequences - {decision} allows progress without user interruption ``` For `abort` decisions, this reads "abort allows progress without user interruption" — which is semantically wrong (abort literally stops progress). For `ask_user` decisions, the text is misleading. Additionally, the consequences should differ per decision type: - **auto_approve**: "Action executed autonomously. Risk: low. Reversibility: high." - **ask_user**: "Decision escalated. User must approve before execution." - **abort**: "Action blocked. Risk assessed as too high for autonomous execution." ## Fix Implement decision-type-specific consequence text. Also consider using the LLM to generate substantive consequences for the `auto_approve` path (what becomes easier, what becomes harder).

Artur added the

bug

P2-Medium

labels

2026-06-16 13:57:01 +00:00

Artur referenced this issue from a commit

2026-06-16 13:59:52 +00:00

fix: P2-03, P2-06 — ADR consequences + config-driven thresholds

Artur closed this issue

2026-06-16 13:59:52 +00:00