feat(acms): implement context policy configuration loader and plan execution integration #9584

Closed
opened 2026-04-14 23:36:52 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Commit message: feat(acms): implement context policy configuration loader and plan execution ACMS integration
  • Branch name: feat/v3.4.0-context-policy-config-plan-integration

Background and Context

Context policies must be configurable per view (YAML/TOML format), and the plan execution engine must use ACMS-assembled context for LLM calls instead of raw file dumps. Without a configuration loader, policies would be hardcoded and inflexible. Without plan execution integration, ACMS context assembly would be unused — actors would continue sending raw file dumps to LLMs, defeating the purpose of the ACMS pipeline.

Expected Behavior

When this issue is complete:

  • Context policy configuration loader supports YAML/TOML with schema validation
  • Per-view policy application works (scope rules, priority weights, budget overrides)
  • Plan execution engine uses ACMS-assembled context for LLM calls
  • End-to-end test: plan execution with ACMS context produces correct LLM call payloads
  • Unit tests pass with coverage >= 97%

Acceptance Criteria

  • Context policy configuration loader supports YAML/TOML with schema validation
  • Per-view policy application works (scope rules, priority weights, budget overrides)
  • Plan execution engine uses ACMS-assembled context for LLM calls
  • End-to-end test: plan execution with ACMS context produces correct LLM call payloads
  • Unit tests pass with coverage >= 97%

Subtasks

  • Implement context policy configuration loader (YAML/TOML)
  • Implement schema validation for policy configuration
  • Implement per-view policy application
  • Integrate ACMS context assembly into plan execution engine
  • Write end-to-end integration test
  • Verify coverage >= 97%

Definition of Done

This issue is closed when:

  1. Context policy configuration loader supports YAML/TOML format
  2. Schema validation rejects invalid policy configurations with clear error messages
  3. Per-view policy application correctly applies scope rules, priority weights, and budget overrides
  4. Plan execution engine uses ACMS-assembled context for all LLM calls (raw file dumps replaced)
  5. End-to-end integration test passes: plan execution with ACMS context produces correct LLM call payloads
  6. All unit tests pass
  7. Test coverage >= 97% for all code introduced in this issue
  8. Code is reviewed and merged into the target branch

Automated by CleverAgents Bot
Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-3]

## Metadata - **Commit message**: `feat(acms): implement context policy configuration loader and plan execution ACMS integration` - **Branch name**: `feat/v3.4.0-context-policy-config-plan-integration` ## Background and Context Context policies must be configurable per view (YAML/TOML format), and the plan execution engine must use ACMS-assembled context for LLM calls instead of raw file dumps. Without a configuration loader, policies would be hardcoded and inflexible. Without plan execution integration, ACMS context assembly would be unused — actors would continue sending raw file dumps to LLMs, defeating the purpose of the ACMS pipeline. ## Expected Behavior When this issue is complete: - Context policy configuration loader supports YAML/TOML with schema validation - Per-view policy application works (scope rules, priority weights, budget overrides) - Plan execution engine uses ACMS-assembled context for LLM calls - End-to-end test: plan execution with ACMS context produces correct LLM call payloads - Unit tests pass with coverage >= 97% ## Acceptance Criteria - [ ] Context policy configuration loader supports YAML/TOML with schema validation - [ ] Per-view policy application works (scope rules, priority weights, budget overrides) - [ ] Plan execution engine uses ACMS-assembled context for LLM calls - [ ] End-to-end test: plan execution with ACMS context produces correct LLM call payloads - [ ] Unit tests pass with coverage >= 97% ## Subtasks - [ ] Implement context policy configuration loader (YAML/TOML) - [ ] Implement schema validation for policy configuration - [ ] Implement per-view policy application - [ ] Integrate ACMS context assembly into plan execution engine - [ ] Write end-to-end integration test - [ ] Verify coverage >= 97% ## Definition of Done This issue is closed when: 1. Context policy configuration loader supports YAML/TOML format 2. Schema validation rejects invalid policy configurations with clear error messages 3. Per-view policy application correctly applies scope rules, priority weights, and budget overrides 4. Plan execution engine uses ACMS-assembled context for all LLM calls (raw file dumps replaced) 5. End-to-end integration test passes: plan execution with ACMS context produces correct LLM call payloads 6. All unit tests pass 7. Test coverage >= 97% for all code introduced in this issue 8. Code is reviewed and merged into the target branch --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planning-pool-supervisor [AUTO-EPIC-3]
Author
Owner

[AUTO-OWNR-1] Triage Decision: Verified — MoSCoW/Must Have

Core ACMS v1 (Advanced Context Management System) feature for v3.4.0 (M5: ACMS v1 + Context Scaling). Must Have for milestone completion.

Milestone: v3.4.0
Priority: High


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


Automated by CleverAgents Bot
Agent: automation-tracking-manager

[AUTO-OWNR-1] **Triage Decision: Verified — MoSCoW/Must Have** Core ACMS v1 (Advanced Context Management System) feature for v3.4.0 (M5: ACMS v1 + Context Scaling). Must Have for milestone completion. **Milestone:** v3.4.0 **Priority:** High --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor --- **Automated by CleverAgents Bot** Agent: automation-tracking-manager
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#9584
No description provided.