feat(autonomy): implement decision correction propagation to child subplans #8865

Open
opened 2026-04-14 03:02:02 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit Message: feat(autonomy): implement decision correction propagation to child subplans
  • Branch: feat/v3.5.0-correction-propagation-subplans

Background and Context

The v3.5.0 milestone (M6: Autonomy Hardening) requires that decision correction (revert mode) works correctly during autonomous execution with hierarchical subplans. When a decision is corrected in a parent plan, the correction must propagate to child subplans if the corrected decision affects them.

Parent Epic: #8603 (Epic: Decision Correction Integration for Autonomy Hardening)

Expected Behavior

When this issue is complete:

  • Decision correction (revert mode) correctly identifies which child subplans are affected by the corrected decision
  • Correction propagates to affected child subplans, triggering selective subtree recomputation
  • Unaffected child subplans continue executing without interruption
  • Correction propagation is logged at DEBUG level for traceability

Acceptance Criteria

  • Decision correction identifies affected child subplans based on dependency graph
  • Correction propagates to affected child subplans
  • Unaffected child subplans are not interrupted
  • Correction propagation is logged at DEBUG level
  • BDD scenarios cover: correction in parent plan, correction propagation to child, no propagation to unaffected child
  • nox passes with coverage >= 97%

Subtasks

  • Audit decision correction integration with hierarchical subplans
  • Implement dependency graph traversal to identify affected child subplans
  • Implement correction propagation to affected child subplans
  • Add DEBUG logging for correction propagation
  • Write BDD scenarios for correction propagation
  • Verify coverage >= 97%
  • Run nox (all default sessions), fix any errors

Definition of Done

This issue is complete when:

  • All subtasks above are completed and checked off
  • Correction propagation to child subplans is implemented and tested
  • CI passes with coverage >= 97%
  • PR is merged to master

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor

## Metadata - **Commit Message**: `feat(autonomy): implement decision correction propagation to child subplans` - **Branch**: `feat/v3.5.0-correction-propagation-subplans` ## Background and Context The v3.5.0 milestone (M6: Autonomy Hardening) requires that decision correction (revert mode) works correctly during autonomous execution with hierarchical subplans. When a decision is corrected in a parent plan, the correction must propagate to child subplans if the corrected decision affects them. Parent Epic: #8603 (Epic: Decision Correction Integration for Autonomy Hardening) ## Expected Behavior When this issue is complete: - Decision correction (revert mode) correctly identifies which child subplans are affected by the corrected decision - Correction propagates to affected child subplans, triggering selective subtree recomputation - Unaffected child subplans continue executing without interruption - Correction propagation is logged at DEBUG level for traceability ## Acceptance Criteria - [ ] Decision correction identifies affected child subplans based on dependency graph - [ ] Correction propagates to affected child subplans - [ ] Unaffected child subplans are not interrupted - [ ] Correction propagation is logged at DEBUG level - [ ] BDD scenarios cover: correction in parent plan, correction propagation to child, no propagation to unaffected child - [ ] `nox` passes with coverage >= 97% ## Subtasks - [ ] Audit decision correction integration with hierarchical subplans - [ ] Implement dependency graph traversal to identify affected child subplans - [ ] Implement correction propagation to affected child subplans - [ ] Add DEBUG logging for correction propagation - [ ] Write BDD scenarios for correction propagation - [ ] Verify coverage >= 97% - [ ] Run `nox` (all default sessions), fix any errors ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off - Correction propagation to child subplans is implemented and tested - CI passes with coverage >= 97% - PR is merged to master --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-14 03:04:37 +00:00
Author
Owner

Triage Decision: VERIFIED — MoSCoW/Must Have

Core v3.5.0 feature: decision correction propagation to child subplans is required for the autonomy hardening milestone. When a decision is corrected in a parent plan, child subplans that depend on that decision must be notified and re-evaluated.

Priority/Critical — Required for v3.5.0 acceptance criteria (decision correction recomputes only affected subtree).


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

✅ **Triage Decision: VERIFIED — MoSCoW/Must Have** Core v3.5.0 feature: decision correction propagation to child subplans is required for the autonomy hardening milestone. When a decision is corrected in a parent plan, child subplans that depend on that decision must be notified and re-evaluated. **Priority/Critical** — Required for v3.5.0 acceptance criteria (decision correction recomputes only affected subtree). --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
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.

Reference
cleveragents/cleveragents-core#8865
No description provided.