feat(context): implement cold-tier compressed archive storage #5210

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

Background

Part of Epic #5165 (Context Tier Storage). Implements the cold-tier compressed archive storage for context data that is rarely accessed but must be retained for historical reference.

Expected Behavior

  • ColdTierStorage stores context data as gzip-compressed JSON archives in <data-dir>/context/cold/
  • LRU eviction based on context_max_decisions_cold setting
  • Automatic warm-tier promotion on access (with decompression)
  • Compression ratio reporting in stats

Subtasks

  • Implement ColdTierStorage with gzip-compressed file storage
  • Add context_max_decisions_cold to Settings with spec-correct default
  • Implement LRU eviction for cold tier
  • Implement automatic warm-tier promotion on cold-tier access
  • Write Behave unit tests for cold tier operations

Definition of Done

  • ColdTierStorage functional with compressed storage
  • LRU eviction works correctly
  • Warm-tier promotion on access works
  • context_max_decisions_cold setting respected
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.4.0/acms-cold-tier-storage
  • Commit Message: feat(context): implement cold-tier compressed archive storage
  • Milestone: v3.4.0
  • Parent Epic: #5165
  • Depends on: #5209 (warm tier must exist first)

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

## Background Part of Epic #5165 (Context Tier Storage). Implements the cold-tier compressed archive storage for context data that is rarely accessed but must be retained for historical reference. ## Expected Behavior - `ColdTierStorage` stores context data as gzip-compressed JSON archives in `<data-dir>/context/cold/` - LRU eviction based on `context_max_decisions_cold` setting - Automatic warm-tier promotion on access (with decompression) - Compression ratio reporting in stats ## Subtasks - [ ] Implement `ColdTierStorage` with gzip-compressed file storage - [ ] Add `context_max_decisions_cold` to `Settings` with spec-correct default - [ ] Implement LRU eviction for cold tier - [ ] Implement automatic warm-tier promotion on cold-tier access - [ ] Write Behave unit tests for cold tier operations ## Definition of Done - [ ] `ColdTierStorage` functional with compressed storage - [ ] LRU eviction works correctly - [ ] Warm-tier promotion on access works - [ ] `context_max_decisions_cold` setting respected - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.4.0/acms-cold-tier-storage` - **Commit Message**: `feat(context): implement cold-tier compressed archive storage` - **Milestone**: v3.4.0 - **Parent Epic**: #5165 - **Depends on**: #5209 (warm 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#5210
No description provided.