feat(context): implement warm-tier disk-based storage with LRU eviction #5209

Open
opened 2026-04-09 03:24:10 +00:00 by HAL9000 · 1 comment
Owner

Background

Part of Epic #5165 (Context Tier Storage). Implements the warm-tier disk-based storage that holds context data that has been evicted from the hot tier but is still likely to be needed soon.

Expected Behavior

  • WarmTierStorage stores context data as JSON files in <data-dir>/context/warm/
  • LRU eviction based on context_max_decisions_warm setting
  • Automatic promotion to hot tier on access
  • Atomic file writes to prevent corruption

Subtasks

  • Implement WarmTierStorage with disk-based JSON file storage
  • Add context_max_decisions_warm to Settings with spec-correct default
  • Implement LRU eviction for warm tier (delete oldest files when limit reached)
  • Implement automatic hot-tier promotion on warm-tier access
  • Write Behave unit tests for warm tier operations

Definition of Done

  • WarmTierStorage functional with disk-based storage
  • LRU eviction works correctly
  • Hot-tier promotion on access works
  • context_max_decisions_warm setting respected
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.4.0/acms-warm-tier-storage
  • Commit Message: feat(context): implement warm-tier disk-based storage with LRU eviction
  • Milestone: v3.4.0
  • Parent Epic: #5165
  • Depends on: #5208 (hot tier must exist first)

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

## Background Part of Epic #5165 (Context Tier Storage). Implements the warm-tier disk-based storage that holds context data that has been evicted from the hot tier but is still likely to be needed soon. ## Expected Behavior - `WarmTierStorage` stores context data as JSON files in `<data-dir>/context/warm/` - LRU eviction based on `context_max_decisions_warm` setting - Automatic promotion to hot tier on access - Atomic file writes to prevent corruption ## Subtasks - [ ] Implement `WarmTierStorage` with disk-based JSON file storage - [ ] Add `context_max_decisions_warm` to `Settings` with spec-correct default - [ ] Implement LRU eviction for warm tier (delete oldest files when limit reached) - [ ] Implement automatic hot-tier promotion on warm-tier access - [ ] Write Behave unit tests for warm tier operations ## Definition of Done - [ ] `WarmTierStorage` functional with disk-based storage - [ ] LRU eviction works correctly - [ ] Hot-tier promotion on access works - [ ] `context_max_decisions_warm` setting respected - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.4.0/acms-warm-tier-storage` - **Commit Message**: `feat(context): implement warm-tier disk-based storage with LRU eviction` - **Milestone**: v3.4.0 - **Parent Epic**: #5165 - **Depends on**: #5208 (hot tier must exist first) --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
HAL9000 added this to the v3.4.0 milestone 2026-04-09 03:24:39 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — ACMS context tier implementation is required for v3.4.0 milestone
  • Story Points: 5 (L) — substantial implementation work for each tier component
  • MoSCoW: Must Have — context tier storage is foundational for ACMS
  • Parent Epic: EPIC #5165 (Context Tier Storage — Hot/Warm/Cold Storage Implementation)

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — ACMS context tier implementation is required for v3.4.0 milestone - **Story Points**: 5 (L) — substantial implementation work for each tier component - **MoSCoW**: Must Have — context tier storage is foundational for ACMS - **Parent Epic**: EPIC #5165 (Context Tier Storage — Hot/Warm/Cold Storage Implementation) --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 self-assigned this 2026-04-09 03:31:13 +00:00
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#5209
No description provided.