Epic: Decision Framework #394

Open
opened 2026-02-23 20:34:18 +00:00 by freemo · 2 comments
Owner

Background

Covers decision domain model, persistence layer, CLI surface, and integration with plan lifecycle. Decisions can be recorded, queried, and used to influence plan execution flow.

Expected Behavior

Decisions are modeled as first-class domain objects, persisted durably, exposed through CLI commands, and integrated into the plan lifecycle to influence execution flow.

Child Issues

Definition of Done

This Epic is complete when all child issues are closed and merged. Decisions recorded and queryable.

## Background Covers decision domain model, persistence layer, CLI surface, and integration with plan lifecycle. Decisions can be recorded, queried, and used to influence plan execution flow. ## Expected Behavior Decisions are modeled as first-class domain objects, persisted durably, exposed through CLI commands, and integrated into the plan lifecycle to influence execution flow. ## Child Issues - #171 - #172 - #173 - #174 ## Definition of Done This Epic is complete when all child issues are closed and merged. Decisions recorded and queryable.
freemo self-assigned this 2026-02-24 03:37:57 +00:00
freemo added this to the v3.3.0 milestone 2026-03-17 18:32:40 +00:00
Author
Owner

UAT discovered a spec-compliance bug in the agents plan tree JSON output. A new child issue has been filed:

  • #1417 UAT: agents plan tree JSON output missing spec-required envelope (command, status, exit_code, data, timing, messages)

This issue is a child of this Epic and should be resolved before the Epic can be closed.

UAT discovered a spec-compliance bug in the `agents plan tree` JSON output. A new child issue has been filed: - #1417 UAT: `agents plan tree` JSON output missing spec-required envelope (command, status, exit_code, data, timing, messages) This issue is a child of this Epic and should be resolved before the Epic can be closed.
Author
Owner

Child issue added: #1421 — UAT: agents plan explain JSON output missing spec-required fields (impact, correction_hint, envelope, alternatives format)

This bug was discovered during UAT of the Decision Framework CLI surface. The _build_explain_dict function in plan.py produces output that diverges from the spec in 7 ways (missing envelope, missing impact, missing correction_hint, wrong sequence format, wrong alternatives format, wrong created_at field name, and extra non-spec fields). Fixing this is required for the Decision Framework to be considered complete.

Child issue added: #1421 — UAT: `agents plan explain` JSON output missing spec-required fields (impact, correction_hint, envelope, alternatives format) This bug was discovered during UAT of the Decision Framework CLI surface. The `_build_explain_dict` function in `plan.py` produces output that diverges from the spec in 7 ways (missing envelope, missing `impact`, missing `correction_hint`, wrong `sequence` format, wrong `alternatives` format, wrong `created_at` field name, and extra non-spec fields). Fixing this is required for the Decision Framework to be considered complete.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks Depends on
#173 feat(di): wire decision services
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#394
No description provided.