EPIC: Context Assembly Pipeline — Budget-Constrained Context Views (ACMS v3.4.0) #5166

Open
opened 2026-04-09 02:57:28 +00:00 by HAL9000 · 1 comment
Owner

Background

Part of the ACMS (Advanced Context Management System) Legendary (#4943). This Epic implements the context assembly pipeline that produces scoped, budget-constrained context views for actors. The pipeline takes project files, applies context policies, and produces a context view that fits within token/size budgets.

Demonstrable Capability

When this Epic is complete, actors receive context views assembled from the ACMS pipeline that respect budget constraints (max_file_size, max_total_size) and context policies.

Child Issues

  • Implement ContextAssembler service with policy-driven file selection
  • Implement budget enforcement (max_file_size, max_total_size constraints)
  • Implement context view scoping (project-level, actor-level, plan-level)
  • Wire ACMS context into plan execution LLM calls
  • Add context policy YAML schema and ContextPolicy model

Definition of Done

  • All child issues are closed and merged
  • Context assembly pipeline produces scoped context views
  • Budget constraints enforced (max_file_size, max_total_size)
  • Plan execution uses ACMS context for LLM calls
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch Naming Convention: feat/v3.4.0/acms-assembly-pipeline
  • Milestone: v3.4.0
  • Parent Legendary: #4943

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planner

## Background Part of the ACMS (Advanced Context Management System) Legendary (#4943). This Epic implements the context assembly pipeline that produces scoped, budget-constrained context views for actors. The pipeline takes project files, applies context policies, and produces a context view that fits within token/size budgets. ## Demonstrable Capability When this Epic is complete, actors receive context views assembled from the ACMS pipeline that respect budget constraints (max_file_size, max_total_size) and context policies. ## Child Issues <!-- Updated by automation after child issues are created --> - [ ] Implement `ContextAssembler` service with policy-driven file selection - [ ] Implement budget enforcement (max_file_size, max_total_size constraints) - [ ] Implement context view scoping (project-level, actor-level, plan-level) - [ ] Wire ACMS context into plan execution LLM calls - [ ] Add context policy YAML schema and `ContextPolicy` model ## Definition of Done - [ ] All child issues are closed and merged - [ ] Context assembly pipeline produces scoped context views - [ ] Budget constraints enforced (max_file_size, max_total_size) - [ ] Plan execution uses ACMS context for LLM calls - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `feat/v3.4.0/acms-assembly-pipeline` - **Milestone**: v3.4.0 - **Parent Legendary**: #4943 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.4.0 milestone 2026-04-09 02:58:02 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — context assembly pipeline is the core of ACMS functionality
  • Milestone: v3.4.0 (already assigned)
  • Story Points: 21 (XXL) — budget-constrained context view assembly
  • MoSCoW: Must Have — core ACMS pipeline is the foundation of the context management system
  • Parent Epic: LEGENDARY #4943 (Advanced Context Management System)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — context assembly pipeline is the core of ACMS functionality - **Milestone**: v3.4.0 (already assigned) - **Story Points**: 21 (XXL) — budget-constrained context view assembly - **MoSCoW**: Must Have — core ACMS pipeline is the foundation of the context management system - **Parent Epic**: LEGENDARY #4943 (Advanced Context Management System) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
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
Reference
cleveragents/cleveragents-core#5166
No description provided.