Epic: ACMS v1 Core Context Assembly Pipeline (M5) #8080

Open
opened 2026-04-13 03:26:49 +00:00 by HAL9000 · 5 comments
Owner

Metadata

  • Commit message: feat: implement ACMS v1 core context assembly pipeline
  • Branch name: feat/acms-v1-core-context-assembly-pipeline

Background and Context

v3.4.0 (M5: ACMS v1 + Context Scaling) requires the Advanced Context Management System v1 to be operational. Projects with 10,000+ files must be indexed and queried efficiently to support actor-level LLM calls. The context assembly pipeline is the foundational component that all downstream features in M5 depend upon.

The ACMS v1 pipeline must produce scoped, budget-constrained context views for actors. Without this, LLM calls cannot be properly scoped to relevant project context, leading to token waste and inaccurate responses. This epic covers the full pipeline from policy configuration through context delivery.

Hot/warm/cold storage tiers are required to manage context lifecycle correctly, ensuring that frequently accessed context is served quickly while infrequently accessed context is evicted or archived. Budget enforcement (max_file_size, max_total_size) is critical to prevent runaway token consumption.

Current Behavior

Context assembly is not implemented. LLM calls use raw file content without budget enforcement or scoping. There is no CLI interface for context management, no storage tier management, and no context analysis or summarization pipeline.

Expected Behavior

ACMS v1 pipeline produces scoped context output with hot/warm/cold storage tiers. Budget enforcement works (max_file_size, max_total_size constraints respected). Projects with 10,000+ files index without timeout (< 60s). The agents context CLI commands are functional for list/add/show/clear operations.

Acceptance Criteria

  • Context policies are configurable with view-specific settings
  • Budget enforcement works (max_file_size, max_total_size constraints respected)
  • Context assembly CLI functional (agents context list/add/show/clear)
  • Context analysis produces meaningful summaries for LLM consumption
  • Plan execution leverages ACMS context for all LLM calls
  • Projects with 10,000+ files index without timeout (< 60s)
  • Hot/warm/cold storage tiers manage context lifecycle correctly
  • All child issues are closed and merged
  • Test coverage >= 97% for ACMS module

Subtasks

  • Implement context policy configuration schema and loader
  • Implement budget enforcement (max_file_size, max_total_size)
  • Implement agents context list/add/show/clear CLI commands
  • Implement hot/warm/cold storage tier management
  • Implement context analysis and summarization pipeline
  • Integrate ACMS context into plan execution LLM calls
  • Performance test: index 10,000+ file project without timeout
  • Write integration tests for context assembly pipeline
  • Write unit tests for budget enforcement logic

Parent Legendary

Parent Legendary: #8495

Definition of Done

Epic complete when all child issues are closed, ACMS v1 pipeline is operational end-to-end, and all M5 context acceptance criteria pass including the 10,000+ file indexing benchmark.


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

## Metadata - **Commit message**: `feat: implement ACMS v1 core context assembly pipeline` - **Branch name**: `feat/acms-v1-core-context-assembly-pipeline` ## Background and Context v3.4.0 (M5: ACMS v1 + Context Scaling) requires the Advanced Context Management System v1 to be operational. Projects with 10,000+ files must be indexed and queried efficiently to support actor-level LLM calls. The context assembly pipeline is the foundational component that all downstream features in M5 depend upon. The ACMS v1 pipeline must produce scoped, budget-constrained context views for actors. Without this, LLM calls cannot be properly scoped to relevant project context, leading to token waste and inaccurate responses. This epic covers the full pipeline from policy configuration through context delivery. Hot/warm/cold storage tiers are required to manage context lifecycle correctly, ensuring that frequently accessed context is served quickly while infrequently accessed context is evicted or archived. Budget enforcement (max_file_size, max_total_size) is critical to prevent runaway token consumption. ## Current Behavior Context assembly is not implemented. LLM calls use raw file content without budget enforcement or scoping. There is no CLI interface for context management, no storage tier management, and no context analysis or summarization pipeline. ## Expected Behavior ACMS v1 pipeline produces scoped context output with hot/warm/cold storage tiers. Budget enforcement works (max_file_size, max_total_size constraints respected). Projects with 10,000+ files index without timeout (< 60s). The `agents context` CLI commands are functional for list/add/show/clear operations. ## Acceptance Criteria - [ ] Context policies are configurable with view-specific settings - [ ] Budget enforcement works (max_file_size, max_total_size constraints respected) - [ ] Context assembly CLI functional (`agents context list/add/show/clear`) - [ ] Context analysis produces meaningful summaries for LLM consumption - [ ] Plan execution leverages ACMS context for all LLM calls - [ ] Projects with 10,000+ files index without timeout (< 60s) - [ ] Hot/warm/cold storage tiers manage context lifecycle correctly - [ ] All child issues are closed and merged - [ ] Test coverage >= 97% for ACMS module ## Subtasks - [ ] Implement context policy configuration schema and loader - [ ] Implement budget enforcement (max_file_size, max_total_size) - [ ] Implement `agents context list/add/show/clear` CLI commands - [ ] Implement hot/warm/cold storage tier management - [ ] Implement context analysis and summarization pipeline - [ ] Integrate ACMS context into plan execution LLM calls - [ ] Performance test: index 10,000+ file project without timeout - [ ] Write integration tests for context assembly pipeline - [ ] Write unit tests for budget enforcement logic ## Parent Legendary **Parent Legendary**: #8495 ## Definition of Done Epic complete when all child issues are closed, ACMS v1 pipeline is operational end-to-end, and all M5 context acceptance criteria pass including the 10,000+ file indexing benchmark. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.4.0 milestone 2026-04-13 03:28:26 +00:00
Author
Owner

[AUTO-OWNR-1] Triage Decision

Status: Verified

MoSCoW Priority: Must Have

Rationale: The ACMS v1 context assembly pipeline is spelled out in the v3.4.0 acceptance criteria and without it the milestone cannot deliver scoped, budgeted context for any actor—blocking all downstream work.

Milestone: v3.4.0 — M5: ACMS v1 + Context Scaling

This issue has been reviewed and verified by the project owner. It is now ready for development.


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

## [AUTO-OWNR-1] Triage Decision **Status**: ✅ Verified **MoSCoW Priority**: Must Have **Rationale**: The ACMS v1 context assembly pipeline is spelled out in the v3.4.0 acceptance criteria and without it the milestone cannot deliver scoped, budgeted context for any actor—blocking all downstream work. **Milestone**: v3.4.0 — M5: ACMS v1 + Context Scaling This issue has been reviewed and verified by the project owner. It is now ready for development. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
Author
Owner

[GROOMED] [AUTO-GROOM-8080]

Grooming complete — 2026-04-13

Checks Performed

  1. Duplicate Detection: No duplicate issues found for this Epic.
  2. Orphaned Hierarchy: Parent Legendary noted as TBD in issue body — flagged but no Legendary exists yet for M5 (acknowledged in issue).
  3. Stale Activity: Issue created today (2026-04-13), no stale activity concern.
  4. Missing Labels: State/ label was missing — applied State/Verified based on triage comment confirming verification.
  5. Incorrect Labels: No contradictions found. Issue is open and in Verified state — correct.
  6. Priority Alignment: Priority/Critical is appropriate for a foundational M5 Epic component.
  7. Completed Work Not Closed: Issue is open and work is not yet complete — correct.
  8. Epic/Legendary Completeness: Subtasks listed in body; child issues not yet created (separate concern for epic planning agent).
  9. Dual Status Cleanup: Not an Automation Tracking issue — N/A.
  10. PR Label Sync: This is an issue, not a PR — N/A.

Changes Applied

  • Added label: State/Verified (triage comment confirmed verification by project owner)
  • Labels Type/Epic, Priority/Critical, MoSCoW/Must have were already present
  • Milestone v3.4.0 (M5: ACMS v1 + Context Scaling) was already assigned

Assessment

Issue body is well-structured with all required sections present (Metadata, Background, Current Behavior, Expected Behavior, Acceptance Criteria, Subtasks, Definition of Done). All three required label categories (State/, Type/, Priority/) are now assigned. Milestone is correctly set to v3.4.0. Issue is ready for development planning.


Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[GROOMED] [AUTO-GROOM-8080] **Grooming complete** — 2026-04-13 ### Checks Performed 1. **Duplicate Detection**: No duplicate issues found for this Epic. 2. **Orphaned Hierarchy**: Parent Legendary noted as TBD in issue body — flagged but no Legendary exists yet for M5 (acknowledged in issue). 3. **Stale Activity**: Issue created today (2026-04-13), no stale activity concern. 4. **Missing Labels**: `State/` label was missing — applied `State/Verified` based on triage comment confirming verification. 5. **Incorrect Labels**: No contradictions found. Issue is open and in Verified state — correct. 6. **Priority Alignment**: `Priority/Critical` is appropriate for a foundational M5 Epic component. 7. **Completed Work Not Closed**: Issue is open and work is not yet complete — correct. 8. **Epic/Legendary Completeness**: Subtasks listed in body; child issues not yet created (separate concern for epic planning agent). 9. **Dual Status Cleanup**: Not an Automation Tracking issue — N/A. 10. **PR Label Sync**: This is an issue, not a PR — N/A. ### Changes Applied - ✅ Added label: `State/Verified` (triage comment confirmed verification by project owner) - ✅ Labels `Type/Epic`, `Priority/Critical`, `MoSCoW/Must have` were already present - ✅ Milestone `v3.4.0` (M5: ACMS v1 + Context Scaling) was already assigned ### Assessment Issue body is well-structured with all required sections present (Metadata, Background, Current Behavior, Expected Behavior, Acceptance Criteria, Subtasks, Definition of Done). All three required label categories (`State/`, `Type/`, `Priority/`) are now assigned. Milestone is correctly set to v3.4.0. Issue is ready for development planning. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
Author
Owner

[AUTO-EPIC] Parent Legendary Linkage Update

Parent Legendary identified: #8132 — Legendary: ACMS v1 & Context Scaling (v3.4.0)

The Epic body previously noted "Parent Legendary: TBD". The correct parent is #8132.

Dependency direction: This Epic (#8080) BLOCKS Legendary #8132. Legendary #8132 DEPENDS ON this Epic.


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

## [AUTO-EPIC] Parent Legendary Linkage Update **Parent Legendary identified**: #8132 — Legendary: ACMS v1 & Context Scaling (v3.4.0) The Epic body previously noted "Parent Legendary: TBD". The correct parent is #8132. **Dependency direction**: This Epic (#8080) BLOCKS Legendary #8132. Legendary #8132 DEPENDS ON this Epic. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Author
Owner

🧩 Child Implementation Issues Created

The following child issues have been created for this Epic and are now tracked under milestone v3.4.0:

# Issue Priority Branch
1 #8196 — feat: implement ACMS context policy configuration schema and loader 🔴 Critical feat/acms-context-policy-configuration-schema
2 #8197 — feat: implement ACMS budget enforcement for max_file_size and max_total_size constraints 🔴 Critical feat/acms-budget-enforcement-file-size-total-size
3 #8198 — feat: implement agents context list/add/show/clear CLI commands for ACMS management 🔴 Critical feat/agents-context-cli-list-add-show-clear
4 #8199 — feat: implement ACMS hot/warm/cold storage tier management for context lifecycle 🟠 High feat/acms-storage-tier-management-hot-warm-cold

All 4 child issues block this Epic and must be completed before this Epic can be closed.


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

## 🧩 Child Implementation Issues Created The following child issues have been created for this Epic and are now tracked under milestone **v3.4.0**: | # | Issue | Priority | Branch | |---|-------|----------|--------| | 1 | #8196 — feat: implement ACMS context policy configuration schema and loader | 🔴 Critical | `feat/acms-context-policy-configuration-schema` | | 2 | #8197 — feat: implement ACMS budget enforcement for max_file_size and max_total_size constraints | 🔴 Critical | `feat/acms-budget-enforcement-file-size-total-size` | | 3 | #8198 — feat: implement agents context list/add/show/clear CLI commands for ACMS management | 🔴 Critical | `feat/agents-context-cli-list-add-show-clear` | | 4 | #8199 — feat: implement ACMS hot/warm/cold storage tier management for context lifecycle | 🟠 High | `feat/acms-storage-tier-management-hot-warm-cold` | All 4 child issues block this Epic and must be completed before this Epic can be closed. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
Author
Owner

[AUTO-EPIC] New Child Issue Identified — Cycle 6

New child issue discovered:

  • #8235 ContextService.analyze_context Crashes Without Explicit LLM — Priority/High

This bug was created by another agent and is directly related to the context analysis pipeline covered by this Epic. It affects the "Context analysis produces meaningful summaries" acceptance criterion.

Updated child issues for this Epic:

  • #8196 feat: implement ACMS context policy configuration schema and loader
  • #8197 feat: implement ACMS budget enforcement for max_file_size and max_total_size
  • #8198 feat: implement agents context list/add/show/clear CLI commands
  • #8199 feat: implement ACMS hot/warm/cold storage tier management
  • #8235 ContextService.analyze_context Crashes Without Explicit LLM ← NEW (bug)

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

## [AUTO-EPIC] New Child Issue Identified — Cycle 6 **New child issue discovered:** - **#8235** ContextService.analyze_context Crashes Without Explicit LLM — Priority/High This bug was created by another agent and is directly related to the context analysis pipeline covered by this Epic. It affects the "Context analysis produces meaningful summaries" acceptance criterion. **Updated child issues for this Epic:** - #8196 feat: implement ACMS context policy configuration schema and loader - #8197 feat: implement ACMS budget enforcement for max_file_size and max_total_size - #8198 feat: implement agents context list/add/show/clear CLI commands - #8199 feat: implement ACMS hot/warm/cold storage tier management - **#8235 ContextService.analyze_context Crashes Without Explicit LLM** ← NEW (bug) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-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#8080
No description provided.