feat(context): implement context view scoping (project-level, actor-level, plan-level) #5222

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

Background

Part of Epic #5166 (Context Assembly Pipeline). Implements context view scoping so that different actors and plans can have different context views of the same project, with scope-specific policies applied.

Expected Behavior

  • ContextScope enum: PROJECT, ACTOR, PLAN
  • Scope-specific context policies override project-level defaults
  • ContextAssembler.assemble() accepts scope parameter
  • Actor-level context can restrict to actor's working directories
  • Plan-level context can restrict to plan's relevant files

Subtasks

  • Define ContextScope enum and scope-specific policy overrides
  • Implement scope-aware policy resolution in ContextAssembler
  • Implement actor-level context scoping (restrict to actor directories)
  • Implement plan-level context scoping (restrict to plan-relevant files)
  • Write Behave unit tests for context scoping

Definition of Done

  • All three scope levels work correctly
  • Scope-specific policy overrides applied correctly
  • Actor and plan scoping restrict context appropriately
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch: feat/v3.4.0/acms-context-scoping
  • Commit Message: feat(context): implement context view scoping (project, actor, plan levels)
  • Milestone: v3.4.0
  • Parent Epic: #5166
  • Depends on: #5221 (budget enforcement must exist first)

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

## Background Part of Epic #5166 (Context Assembly Pipeline). Implements context view scoping so that different actors and plans can have different context views of the same project, with scope-specific policies applied. ## Expected Behavior - `ContextScope` enum: `PROJECT`, `ACTOR`, `PLAN` - Scope-specific context policies override project-level defaults - `ContextAssembler.assemble()` accepts scope parameter - Actor-level context can restrict to actor's working directories - Plan-level context can restrict to plan's relevant files ## Subtasks - [ ] Define `ContextScope` enum and scope-specific policy overrides - [ ] Implement scope-aware policy resolution in `ContextAssembler` - [ ] Implement actor-level context scoping (restrict to actor directories) - [ ] Implement plan-level context scoping (restrict to plan-relevant files) - [ ] Write Behave unit tests for context scoping ## Definition of Done - [ ] All three scope levels work correctly - [ ] Scope-specific policy overrides applied correctly - [ ] Actor and plan scoping restrict context appropriately - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch**: `feat/v3.4.0/acms-context-scoping` - **Commit Message**: `feat(context): implement context view scoping (project, actor, plan levels)` - **Milestone**: v3.4.0 - **Parent Epic**: #5166 - **Depends on**: #5221 (budget enforcement 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:36:54 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — ACMS context assembly and budget enforcement are required for v3.4.0 milestone
  • Story Points: 5 (L) — substantial implementation work
  • MoSCoW: Must Have — context assembly is the core of ACMS functionality
  • Parent Epic: EPIC #5166 (Context Assembly Pipeline) or #5167 (Context Budget Enforcement)
  • Assignee: HAL9000 — default assignment to maintain velocity

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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — ACMS context assembly and budget enforcement are required for v3.4.0 milestone - **Story Points**: 5 (L) — substantial implementation work - **MoSCoW**: Must Have — context assembly is the core of ACMS functionality - **Parent Epic**: EPIC #5166 (Context Assembly Pipeline) or #5167 (Context Budget Enforcement) - **Assignee**: HAL9000 — default assignment to maintain velocity --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 self-assigned this 2026-04-09 03:42:45 +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#5222
No description provided.