Epic: Decision Correction Integration for Autonomy Hardening (v3.5.0) #8603

Open
opened 2026-04-13 21:14:23 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message: feat(autonomy): integrate decision correction with selective subtree recomputation into autonomy hardening
  • Branch name: feat/v3.5.0-decision-correction-autonomy-integration

Background and Context

As part of the v3.5.0 milestone (M6: Autonomy Hardening) and Legendary #8450 (Autonomy Hardening Workstream B), the decision correction engine (delivered in v3.2.0) must be integrated into the autonomy hardening flow. Specifically, selective subtree recomputation must work correctly when decisions are corrected during autonomous execution.

This Epic ensures that the v3.2.0 decision correction work (plan correct --mode=revert with selective subtree recomputation) is properly integrated with the v3.5.0 parallel execution and hierarchical decomposition features.

This Epic blocks the parent Legendary issue #8450.

Expected Behavior

When this Epic is complete:

  • Decision correction (revert mode) works correctly during autonomous execution
  • Selective subtree recomputation correctly identifies and re-evaluates only downstream decisions
  • Decision correction works with hierarchical subplans (corrections propagate to child subplans if needed)
  • Decision correction works with parallel execution (corrections do not cause race conditions)
  • The correction flow is covered by integration tests

Acceptance Criteria

  • Decision correction (revert mode) works during autonomous execution
  • Selective subtree recomputation correctly identifies downstream decisions in hierarchical plans
  • Corrections propagate to child subplans when the corrected decision affects them
  • Decision correction works without race conditions in parallel execution
  • Integration tests verify correction in hierarchical and parallel execution scenarios
  • nox passes with coverage >= 97%

Subtasks

  • Audit decision correction integration with hierarchical subplans
  • Implement correction propagation to child subplans
  • Implement race condition prevention for corrections in parallel execution
  • Write integration tests for correction in hierarchical plans
  • Write integration tests for correction in parallel execution
  • Verify nox passes with coverage >= 97%

Child Issues / Child Epics

  • #8865 — Implement decision correction propagation to child subplans
  • #8866 — Implement race condition prevention for decision corrections in parallel execution
  • Integration tests for correction in hierarchical and parallel execution — TBD

Definition of Done

This Epic should be closed when:

  1. All acceptance criteria above are verified and checked off
  2. All child implementation issues are closed
  3. Test coverage >= 97% is confirmed by CI
  4. Code has passed peer review and been merged to the main branch
  5. The parent Legendary issue #8450 has been updated to reflect this Epic's completion

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

## Metadata - **Commit message**: `feat(autonomy): integrate decision correction with selective subtree recomputation into autonomy hardening` - **Branch name**: `feat/v3.5.0-decision-correction-autonomy-integration` ## Background and Context As part of the v3.5.0 milestone (M6: Autonomy Hardening) and Legendary #8450 (Autonomy Hardening Workstream B), the decision correction engine (delivered in v3.2.0) must be integrated into the autonomy hardening flow. Specifically, selective subtree recomputation must work correctly when decisions are corrected during autonomous execution. This Epic ensures that the v3.2.0 decision correction work (plan correct --mode=revert with selective subtree recomputation) is properly integrated with the v3.5.0 parallel execution and hierarchical decomposition features. This Epic blocks the parent Legendary issue #8450. ## Expected Behavior When this Epic is complete: - Decision correction (revert mode) works correctly during autonomous execution - Selective subtree recomputation correctly identifies and re-evaluates only downstream decisions - Decision correction works with hierarchical subplans (corrections propagate to child subplans if needed) - Decision correction works with parallel execution (corrections do not cause race conditions) - The correction flow is covered by integration tests ## Acceptance Criteria - [ ] Decision correction (revert mode) works during autonomous execution - [ ] Selective subtree recomputation correctly identifies downstream decisions in hierarchical plans - [ ] Corrections propagate to child subplans when the corrected decision affects them - [ ] Decision correction works without race conditions in parallel execution - [ ] Integration tests verify correction in hierarchical and parallel execution scenarios - [ ] `nox` passes with coverage >= 97% ## Subtasks - [ ] Audit decision correction integration with hierarchical subplans - [ ] Implement correction propagation to child subplans - [ ] Implement race condition prevention for corrections in parallel execution - [ ] Write integration tests for correction in hierarchical plans - [ ] Write integration tests for correction in parallel execution - [ ] Verify `nox` passes with coverage >= 97% ## Child Issues / Child Epics - [ ] #8865 — Implement decision correction propagation to child subplans - [ ] #8866 — Implement race condition prevention for decision corrections in parallel execution - [ ] Integration tests for correction in hierarchical and parallel execution — _TBD_ ## Definition of Done This Epic should be closed when: 1. All acceptance criteria above are verified and checked off 2. All child implementation issues are closed 3. Test coverage >= 97% is confirmed by CI 4. Code has passed peer review and been merged to the main branch 5. The parent Legendary issue #8450 has been updated to reflect this Epic's completion --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.5.0 milestone 2026-04-13 21:14:30 +00:00
Author
Owner

Child Implementation Issues Created

The following child implementation issues have been created for this Epic and are now tracked in the v3.5.0 milestone. Each child issue BLOCKS this Epic (#8603).

# Issue Labels
#8651 feat(autonomy): implement decision correction propagation to child subplans Type/Feature Priority/Critical MoSCoW/Must have State/Verified
#8652 feat(autonomy): implement race condition prevention for decision corrections in parallel execution Type/Feature Priority/Critical MoSCoW/Must have State/Verified
#8653 test(autonomy): integration tests for decision correction in hierarchical and parallel execution Type/Feature Priority/Critical MoSCoW/Must have State/Verified

All issues are assigned to milestone v3.5.0 (ID: 108).


Automated by CleverAgents Bot
Agent: new-issue-creator

## Child Implementation Issues Created The following child implementation issues have been created for this Epic and are now tracked in the v3.5.0 milestone. Each child issue BLOCKS this Epic (#8603). | # | Issue | Labels | |---|-------|--------| | #8651 | [feat(autonomy): implement decision correction propagation to child subplans](https://git.cleverthis.com/cleveragents/cleveragents-core/issues/8651) | `Type/Feature` `Priority/Critical` `MoSCoW/Must have` `State/Verified` | | #8652 | [feat(autonomy): implement race condition prevention for decision corrections in parallel execution](https://git.cleverthis.com/cleveragents/cleveragents-core/issues/8652) | `Type/Feature` `Priority/Critical` `MoSCoW/Must have` `State/Verified` | | #8653 | [test(autonomy): integration tests for decision correction in hierarchical and parallel execution](https://git.cleverthis.com/cleveragents/cleveragents-core/issues/8653) | `Type/Feature` `Priority/Critical` `MoSCoW/Must have` `State/Verified` | All issues are assigned to milestone **v3.5.0** (ID: 108). --- **Automated by CleverAgents Bot** Agent: new-issue-creator
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#8603
No description provided.