LEGENDARY: Advanced Context Management System (ACMS) — Context Scaling & Tier Management #4943

Open
opened 2026-04-08 23:38:29 +00:00 by freemo · 4 comments
Owner

Strategic Pillar: Advanced Context Management System (ACMS)

This Legendary covers the ACMS v1 implementation that enables CleverAgents to work with large codebases (10,000+ files) through intelligent context assembly, hot/warm/cold storage tiers, and budget-constrained context views. It spans milestone v3.4.0.

Articulated End State

When this Legendary is complete:

  • Projects with 10,000+ files can be indexed and queried without timeout
  • Context assembly pipeline produces scoped, budget-constrained context views for actors
  • Hot/warm/cold storage tiers manage context lifecycle
  • Context policies are configurable with view-specific settings
  • Budget enforcement works (max_file_size, max_total_size constraints)
  • Context analysis produces meaningful summaries
  • Plan execution leverages ACMS context for LLM calls

Child Epics

  • Epic: Context Tier Storage (Hot/Warm/Cold) (v3.4.0)
  • Epic: Context Assembly Pipeline (v3.4.0)
  • Epic: Context Budget Enforcement (v3.4.0)
  • Epic: Context CLI Commands (v3.4.0)
  • Epic: Large Project Indexing (v3.4.0)

Definition of Done

  • All child Epics are closed
  • Projects with 10,000+ files index without timeout
  • Context window management works (hot/warm/cold tiers)
  • ACMS v1 pipeline produces scoped context output
  • agents context list/add/show/clear CLI functional
  • Test coverage >= 97%

Metadata

  • Milestone: v3.4.0
  • Strategic Area: Context Intelligence

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

## Strategic Pillar: Advanced Context Management System (ACMS) This Legendary covers the ACMS v1 implementation that enables CleverAgents to work with large codebases (10,000+ files) through intelligent context assembly, hot/warm/cold storage tiers, and budget-constrained context views. It spans milestone v3.4.0. ### Articulated End State When this Legendary is complete: - Projects with 10,000+ files can be indexed and queried without timeout - Context assembly pipeline produces scoped, budget-constrained context views for actors - Hot/warm/cold storage tiers manage context lifecycle - Context policies are configurable with view-specific settings - Budget enforcement works (max_file_size, max_total_size constraints) - Context analysis produces meaningful summaries - Plan execution leverages ACMS context for LLM calls ### Child Epics <!-- Updated by automation after child epics are created --> - [ ] Epic: Context Tier Storage (Hot/Warm/Cold) (v3.4.0) - [ ] Epic: Context Assembly Pipeline (v3.4.0) - [ ] Epic: Context Budget Enforcement (v3.4.0) - [ ] Epic: Context CLI Commands (v3.4.0) - [ ] Epic: Large Project Indexing (v3.4.0) ### Definition of Done - [ ] All child Epics are closed - [ ] Projects with 10,000+ files index without timeout - [ ] Context window management works (hot/warm/cold tiers) - [ ] ACMS v1 pipeline produces scoped context output - [ ] `agents context list/add/show/clear` CLI functional - [ ] Test coverage >= 97% ## Metadata - **Milestone**: v3.4.0 - **Strategic Area**: Context Intelligence --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — ACMS (Advanced Context Management System) is a core architectural pillar enabling context scaling, tier management, and UKO/CRP strategies
  • Milestone: v3.4.0
  • Story Points: 88 — XXL — Legendary spanning the entire v3.4.0 milestone with multiple child Epics
  • MoSCoW: Must Have — Context management at scale is essential for production use; without ACMS, the system cannot handle large context windows or multi-tier context strategies
  • Type: Legendary

This Legendary is valid and well-scoped. It covers the full ACMS implementation including UKO, CRP, context assembly pipeline, and tier management strategies.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — ACMS (Advanced Context Management System) is a core architectural pillar enabling context scaling, tier management, and UKO/CRP strategies - **Milestone**: v3.4.0 - **Story Points**: 88 — XXL — Legendary spanning the entire v3.4.0 milestone with multiple child Epics - **MoSCoW**: Must Have — Context management at scale is essential for production use; without ACMS, the system cannot handle large context windows or multi-tier context strategies - **Type**: Legendary This Legendary is valid and well-scoped. It covers the full ACMS implementation including UKO, CRP, context assembly pipeline, and tier management strategies. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 added this to the v3.4.0 milestone 2026-04-09 00:21:13 +00:00
Owner

Epic Planning Complete: All 5 child Epics have been created and linked to this Legendary.

Child Epics Created

  • #5165 — EPIC: Context Tier Storage — Hot/Warm/Cold Storage Implementation
  • #5166 — EPIC: Context Assembly Pipeline — Budget-Constrained Context Views
  • #5167 — EPIC: Context Budget Enforcement — Token & Size Constraint System
  • #5168 — EPIC: Context CLI Commands — agents context list/add/show/clear/inspect
  • #5169 — EPIC: Large Project Indexing — 10,000+ File Codebase Support

Dependency Chain

#5165 Context Tier Storage ──┐
#5166 Assembly Pipeline ─────┤
#5167 Budget Enforcement ────┼──► LEGENDARY #4943 (ACMS)
#5168 Context CLI Commands ──┤
#5169 Large Project Indexing ┘

Note: v3.4.0 milestone is converging (57 open / 130 closed). These epics represent the structural ACMS work that was missing from the hierarchy. Implementation workers should prioritize existing open issues first.


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

**Epic Planning Complete**: All 5 child Epics have been created and linked to this Legendary. ## Child Epics Created - [ ] #5165 — EPIC: Context Tier Storage — Hot/Warm/Cold Storage Implementation - [ ] #5166 — EPIC: Context Assembly Pipeline — Budget-Constrained Context Views - [ ] #5167 — EPIC: Context Budget Enforcement — Token & Size Constraint System - [ ] #5168 — EPIC: Context CLI Commands — agents context list/add/show/clear/inspect - [ ] #5169 — EPIC: Large Project Indexing — 10,000+ File Codebase Support ## Dependency Chain ``` #5165 Context Tier Storage ──┐ #5166 Assembly Pipeline ─────┤ #5167 Budget Enforcement ────┼──► LEGENDARY #4943 (ACMS) #5168 Context CLI Commands ──┤ #5169 Large Project Indexing ┘ ``` **Note**: v3.4.0 milestone is converging (57 open / 130 closed). These epics represent the structural ACMS work that was missing from the hierarchy. Implementation workers should prioritize existing open issues first. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Owner

Closing as superseded by the canonical Legendary #8495 which covers the same scope with a more complete structure.


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

Closing as superseded by the canonical Legendary #8495 which covers the same scope with a more complete structure. --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
Owner

⚠️ CORRECTION — Previous comment retracted: This Legendary has open child Epics with active work items and cannot be closed at this time. The previous comment suggesting closure was premature. This issue requires human review before any closure decision is made.

Reason for retraction: Forgejo blocked closure (HTTP 412) because this Legendary has open dependencies (child Epics and/or UAT issues) that are still actively being worked on. These child Epics are NOT covered by the canonical Legendary and represent unique, active work.

Action required: Human review needed to determine whether:

  1. The open child Epics should be migrated to the canonical Legendary before closing this one, OR
  2. This Legendary should remain open as a parallel tracking vehicle, OR
  3. The child Epics should be closed first, then this Legendary closed

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

**⚠️ CORRECTION — Previous comment retracted:** This Legendary has open child Epics with active work items and cannot be closed at this time. The previous comment suggesting closure was premature. This issue requires human review before any closure decision is made. **Reason for retraction:** Forgejo blocked closure (HTTP 412) because this Legendary has open dependencies (child Epics and/or UAT issues) that are still actively being worked on. These child Epics are NOT covered by the canonical Legendary and represent unique, active work. **Action required:** Human review needed to determine whether: 1. The open child Epics should be migrated to the canonical Legendary before closing this one, OR 2. This Legendary should remain open as a parallel tracking vehicle, OR 3. The child Epics should be closed first, then this Legendary closed --- **Automated by CleverAgents Bot** Supervisor: Epic Planning Pool | Agent: epic-planning-pool-supervisor
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#4943
No description provided.