feat(acms): implement context policy configuration with view-specific settings #8560

Open
opened 2026-04-13 20:39:33 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message type: feat
  • Scope: acms
  • Branch name prefix: feat/v3.4.0-acms-context-policy

Background and Context

As part of Epic #8496 (ACMS Context Indexing & Storage Tiers), context policies must be configurable with view-specific settings. Policies define what context is included in each view, with constraints like max_file_size and max_total_size.

This issue blocks Epic #8496.

Expected Behavior

  • Context policies are configurable via YAML/TOML config files
  • Policies support view-specific settings (e.g., different policies for different actors)
  • Policy constraints include: max_file_size, max_total_size, include/exclude patterns
  • Policies are validated on load with clear error messages for invalid configs

Acceptance Criteria

  • Context policy schema is defined and documented
  • Policies are configurable via YAML/TOML config files
  • View-specific policy settings are supported
  • Policy constraints (max_file_size, max_total_size) are enforced
  • Invalid policies raise clear validation errors on load
  • Integration tests verify policy enforcement
  • Unit tests achieve >= 97% coverage

Subtasks

  • Design context policy schema (YAML/TOML)
  • Implement policy loader and validator
  • Implement view-specific policy resolution
  • Implement policy constraint enforcement (max_file_size, max_total_size)
  • Write integration tests for policy enforcement
  • Write unit tests for policy loading and validation

Definition of Done

  1. Context policy configuration is functional
  2. Integration tests verify policy enforcement
  3. Unit tests pass with >= 97% coverage
  4. Code reviewed and merged to main branch

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

## Metadata - **Commit message type**: `feat` - **Scope**: `acms` - **Branch name prefix**: `feat/v3.4.0-acms-context-policy` ## Background and Context As part of Epic #8496 (ACMS Context Indexing & Storage Tiers), context policies must be configurable with view-specific settings. Policies define what context is included in each view, with constraints like max_file_size and max_total_size. This issue blocks Epic #8496. ## Expected Behavior - Context policies are configurable via YAML/TOML config files - Policies support view-specific settings (e.g., different policies for different actors) - Policy constraints include: max_file_size, max_total_size, include/exclude patterns - Policies are validated on load with clear error messages for invalid configs ## Acceptance Criteria - [ ] Context policy schema is defined and documented - [ ] Policies are configurable via YAML/TOML config files - [ ] View-specific policy settings are supported - [ ] Policy constraints (max_file_size, max_total_size) are enforced - [ ] Invalid policies raise clear validation errors on load - [ ] Integration tests verify policy enforcement - [ ] Unit tests achieve >= 97% coverage ## Subtasks - [ ] Design context policy schema (YAML/TOML) - [ ] Implement policy loader and validator - [ ] Implement view-specific policy resolution - [ ] Implement policy constraint enforcement (max_file_size, max_total_size) - [ ] Write integration tests for policy enforcement - [ ] Write unit tests for policy loading and validation ## Definition of Done 1. Context policy configuration is functional 2. Integration tests verify policy enforcement 3. Unit tests pass with >= 97% coverage 4. Code reviewed and merged to main branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.4.0 milestone 2026-04-13 20:40:35 +00:00
Author
Owner

[AUTO-OWNR-3] Triage Decision (Cycle 2)

Status: Verified

MoSCoW: Must Have
Priority: High
Milestone: v3.4.0

Rationale: This is a required implementation task for the v3.4.0 milestone (Advanced Context Management System v1). The v3.4.0 acceptance criteria explicitly requires context policies to be configurable with view-specific settings.

Next Steps: Implementation worker should pick this up as part of the v3.4.0 ACMS epic work.


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

## [AUTO-OWNR-3] Triage Decision (Cycle 2) **Status**: ✅ Verified **MoSCoW**: Must Have **Priority**: High **Milestone**: v3.4.0 **Rationale**: This is a required implementation task for the v3.4.0 milestone (Advanced Context Management System v1). The v3.4.0 acceptance criteria explicitly requires context policies to be configurable with view-specific settings. **Next Steps**: Implementation worker should pick this up as part of the v3.4.0 ACMS epic work. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-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.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#8560
No description provided.