feat: implement ACMS context policy configuration schema and loader #8196

Open
opened 2026-04-13 04:26:23 +00:00 by HAL9000 · 1 comment
Owner

Background and Context

The ACMS v1 pipeline requires context policies to be configurable with view-specific settings. Context policies define which files are included, budget limits, and storage tier assignments. Without a policy configuration system, all context assembly uses hardcoded defaults that cannot be customized per project or per actor.

Current Behavior

Context assembly uses hardcoded defaults. No policy configuration schema exists. Users cannot configure context policies via YAML or CLI.

Expected Behavior

A YAML-based context policy configuration schema is defined. The policy loader reads and validates policy files. View-specific settings (file patterns, budget limits, tier assignments) are configurable. The agents context CLI commands use the loaded policy.

Acceptance Criteria

  • Context policy YAML schema is defined and documented
  • Policy loader reads and validates policy files
  • View-specific settings are configurable (file patterns, budget limits)
  • Storage tier assignments are configurable per policy
  • Invalid policy files produce clear validation errors
  • Default policy is used when no policy file is present
  • Test coverage >= 97% for policy configuration module

Metadata

  • Commit Message: feat: implement ACMS context policy configuration schema and loader
  • Branch Name: feat/acms-context-policy-configuration-schema

Subtasks

  • Design context policy YAML schema
  • Implement policy loader with validation
  • Implement view-specific settings parsing
  • Implement storage tier assignment configuration
  • Implement default policy fallback
  • Write unit tests for policy loader
  • Write integration tests for policy loading in context assembly

Definition of Done

Context policy YAML schema is defined, loader validates policies, view-specific settings are configurable, and test coverage >= 97%.

Parent Epic

Child of and blocks #8080 — ACMS v1 Core Context Assembly Pipeline


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

## Background and Context The ACMS v1 pipeline requires context policies to be configurable with view-specific settings. Context policies define which files are included, budget limits, and storage tier assignments. Without a policy configuration system, all context assembly uses hardcoded defaults that cannot be customized per project or per actor. ## Current Behavior Context assembly uses hardcoded defaults. No policy configuration schema exists. Users cannot configure context policies via YAML or CLI. ## Expected Behavior A YAML-based context policy configuration schema is defined. The policy loader reads and validates policy files. View-specific settings (file patterns, budget limits, tier assignments) are configurable. The `agents context` CLI commands use the loaded policy. ## Acceptance Criteria - [ ] Context policy YAML schema is defined and documented - [ ] Policy loader reads and validates policy files - [ ] View-specific settings are configurable (file patterns, budget limits) - [ ] Storage tier assignments are configurable per policy - [ ] Invalid policy files produce clear validation errors - [ ] Default policy is used when no policy file is present - [ ] Test coverage >= 97% for policy configuration module ## Metadata - **Commit Message**: `feat: implement ACMS context policy configuration schema and loader` - **Branch Name**: `feat/acms-context-policy-configuration-schema` ## Subtasks - [ ] Design context policy YAML schema - [ ] Implement policy loader with validation - [ ] Implement view-specific settings parsing - [ ] Implement storage tier assignment configuration - [ ] Implement default policy fallback - [ ] Write unit tests for policy loader - [ ] Write integration tests for policy loading in context assembly ## Definition of Done Context policy YAML schema is defined, loader validates policies, view-specific settings are configurable, and test coverage >= 97%. ## Parent Epic Child of and blocks #8080 — ACMS v1 Core Context Assembly Pipeline --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor
HAL9000 added this to the v3.4.0 milestone 2026-04-13 04:28:45 +00:00
Author
Owner

Verified — ACMS context policy configuration is an explicit v3.4.0 acceptance criterion: 'Context policies configurable with view-specific settings.' Must Have for v3.4.0. Verified.


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

✅ **Verified** — ACMS context policy configuration is an explicit v3.4.0 acceptance criterion: 'Context policies configurable with view-specific settings.' **Must Have** for v3.4.0. Verified. --- **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#8196
No description provided.