feat(acms): integrate ACMS context assembly into plan execution LLM calls #8563

Open
opened 2026-04-13 20:39:54 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message type: feat
  • Scope: acms
  • Branch name prefix: feat/v3.4.0-acms-llm-integration

Background and Context

As part of Epic #8497 (Context Assembly Pipeline & Budget Enforcement), the ACMS context assembly pipeline must be integrated into plan execution so that LLM calls use the assembled context. This replaces any ad-hoc context gathering with the structured ACMS pipeline.

This issue blocks Epic #8497.

Expected Behavior

  • Before each LLM call in plan execution, the ACMS assembles a context view
  • The assembled context view is included in the LLM prompt
  • Context assembly uses the current actor's scope and policy
  • LLM calls without ACMS context are replaced with ACMS-backed calls

Acceptance Criteria

  • Plan execution uses ACMS context assembly before each LLM call
  • Assembled context view is included in the LLM prompt
  • Context assembly uses the current actor's scope and policy
  • Integration tests verify ACMS context appears in LLM calls during plan execution
  • Unit tests achieve >= 97% coverage

Subtasks

  • Identify all LLM call sites in plan execution
  • Integrate ACMS context assembly at each LLM call site
  • Pass actor scope and policy to context assembler
  • Write integration tests for ACMS-backed LLM calls
  • Write unit tests for integration logic

Definition of Done

  1. ACMS context is integrated into plan execution LLM calls
  2. Integration tests verify ACMS context in LLM calls
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

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

## Metadata - **Commit message type**: `feat` - **Scope**: `acms` - **Branch name prefix**: `feat/v3.4.0-acms-llm-integration` ## Background and Context As part of Epic #8497 (Context Assembly Pipeline & Budget Enforcement), the ACMS context assembly pipeline must be integrated into plan execution so that LLM calls use the assembled context. This replaces any ad-hoc context gathering with the structured ACMS pipeline. This issue blocks Epic #8497. ## Expected Behavior - Before each LLM call in plan execution, the ACMS assembles a context view - The assembled context view is included in the LLM prompt - Context assembly uses the current actor's scope and policy - LLM calls without ACMS context are replaced with ACMS-backed calls ## Acceptance Criteria - [ ] Plan execution uses ACMS context assembly before each LLM call - [ ] Assembled context view is included in the LLM prompt - [ ] Context assembly uses the current actor's scope and policy - [ ] Integration tests verify ACMS context appears in LLM calls during plan execution - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Identify all LLM call sites in plan execution - [ ] Integrate ACMS context assembly at each LLM call site - [ ] Pass actor scope and policy to context assembler - [ ] Write integration tests for ACMS-backed LLM calls - [ ] Write unit tests for integration logic ## Definition of Done 1. ACMS context is integrated into plan execution LLM calls 2. Integration tests verify ACMS context in LLM calls 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.4.0 milestone 2026-04-13 20:40:38 +00:00
Author
Owner

[AUTO-OWNR-3] Triage Decision (Cycle 2)

Status: Verified

MoSCoW: Must Have
Priority: High
Milestone: v3.4.0

Rationale: This is a required implementation task for the v3.4.0 milestone (Advanced Context Management System v1). The v3.4.0 acceptance criteria explicitly requires plan execution to leverage ACMS context for LLM calls.

Next Steps: Implementation worker should pick this up as part of the v3.4.0 ACMS epic work.


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

## [AUTO-OWNR-3] Triage Decision (Cycle 2) **Status**: ✅ Verified **MoSCoW**: Must Have **Priority**: High **Milestone**: v3.4.0 **Rationale**: This is a required implementation task for the v3.4.0 milestone (Advanced Context Management System v1). The v3.4.0 acceptance criteria explicitly requires plan execution to leverage ACMS context for LLM calls. **Next Steps**: Implementation worker should pick this up as part of the v3.4.0 ACMS epic work. --- **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.

Dependencies

No dependencies set.

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