feat(acms): implement context assembly pipeline for scoped context views #8561

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

Metadata

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

Background and Context

As part of Epic #8497 (Context Assembly Pipeline & Budget Enforcement), the ACMS must produce scoped, budget-constrained context views for actors. The assembly pipeline takes a context policy and produces a context view that fits within the budget.

This issue blocks Epic #8497.

Expected Behavior

  • The assembly pipeline takes a context policy and actor scope as inputs
  • It queries the context index for relevant files/content
  • It assembles a context view that fits within the budget constraints
  • The assembled context is returned as a structured object for LLM consumption

Acceptance Criteria

  • ContextAssembler class is implemented with policy and scope inputs
  • Assembler queries the context index for relevant content
  • Assembled context fits within budget constraints (max_file_size, max_total_size)
  • Context view is returned as a structured object
  • Integration tests verify assembly with various policies and scopes
  • Unit tests achieve >= 97% coverage

Subtasks

  • Design ContextView output structure
  • Implement ContextAssembler class
  • Implement context index query with scope filtering
  • Implement budget-constrained assembly (truncate/prioritize to fit budget)
  • Write integration tests for assembly pipeline
  • Write unit tests for assembler logic

Definition of Done

  1. Context assembly pipeline is functional
  2. Integration tests verify assembly with various policies
  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-assembly-pipeline` ## Background and Context As part of Epic #8497 (Context Assembly Pipeline & Budget Enforcement), the ACMS must produce scoped, budget-constrained context views for actors. The assembly pipeline takes a context policy and produces a context view that fits within the budget. This issue blocks Epic #8497. ## Expected Behavior - The assembly pipeline takes a context policy and actor scope as inputs - It queries the context index for relevant files/content - It assembles a context view that fits within the budget constraints - The assembled context is returned as a structured object for LLM consumption ## Acceptance Criteria - [ ] `ContextAssembler` class is implemented with policy and scope inputs - [ ] Assembler queries the context index for relevant content - [ ] Assembled context fits within budget constraints (max_file_size, max_total_size) - [ ] Context view is returned as a structured object - [ ] Integration tests verify assembly with various policies and scopes - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Design `ContextView` output structure - [ ] Implement `ContextAssembler` class - [ ] Implement context index query with scope filtering - [ ] Implement budget-constrained assembly (truncate/prioritize to fit budget) - [ ] Write integration tests for assembly pipeline - [ ] Write unit tests for assembler logic ## Definition of Done 1. Context assembly pipeline is functional 2. Integration tests verify assembly with various policies 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:36 +00:00
Author
Owner

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

Status: Verified

MoSCoW: Must Have
Priority: Critical
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 the ACMS v1 pipeline to produce scoped context output. The context assembly pipeline is the core ACMS v1 feature that all other components feed into.

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**: Critical **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 the ACMS v1 pipeline to produce scoped context output. The context assembly pipeline is the core ACMS v1 feature that all other components feed into. **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#8561
No description provided.