cleveragents/cleveragents-core

Fork 3

UAT: `NamespacedProject` missing `context_policy` field — `ProjectContextPolicy` not part of project domain model #4822

New issue

Open

opened 2026-04-08 19:45:34 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-08 19:45:34 +00:00

Owner

Bug Report

Tested by: UAT tester instance uat-tester-project-model-1
Feature area: Project Model — Context Policies

What Was Tested

The NamespacedProject domain model's ability to carry a ProjectContextPolicy as specified.

Expected Behavior (from spec)

The spec defines that projects have a context policy (ProjectContextPolicy) that controls what context (resources and files) is available during each ACMS phase (default → strategize → execute → apply). This policy uses view inheritance and should be a first-class field on the project domain model.

Actual Behavior

The NamespacedProject Pydantic model in src/cleveragents/domain/models/core/project.py has a context_config: ContextConfig field (for basic file filtering and size limits), but does NOT have a context_policy: ProjectContextPolicy field for the phase-based view inheritance policy:

class NamespacedProject(BaseModel):
    name: str
    namespace: str
    server: str | None
    description: str | None
    linked_resources: list[LinkedResource]
    context_config: ContextConfig  # ← basic config only
    # ← NO context_policy: ProjectContextPolicy field
    created_at: datetime
    updated_at: datetime

The ProjectContextPolicy model exists in src/cleveragents/domain/models/core/context_policy.py with full phase-based view inheritance:

class ProjectContextPolicy(BaseModel):
    default_view: ContextView
    strategize_view: ContextView | None
    execute_view: ContextView | None
    apply_view: ContextView | None

    def resolve_view(self, phase: str) -> ContextView: ...

The agents project context set/show/inspect/simulate commands exist in project_context.py (45KB), but they appear to manage context policy separately from the NamespacedProject domain model, likely using their own storage mechanism.

Code Location

src/cleveragents/domain/models/core/project.py — NamespacedProject has context_config but not context_policy
src/cleveragents/domain/models/core/context_policy.py — ProjectContextPolicy model exists but is not on NamespacedProject
src/cleveragents/cli/commands/project_context.py — context policy CLI commands (separate from project model)

Impact

NamespacedProject.context_config only covers basic file filtering (ignore patterns, size limits, chunking)
The phase-based context policy (ProjectContextPolicy) is not accessible via the project domain model
The ACMS pipeline cannot load the project's context policy from the NamespacedProject object directly
agents project show doesn't display the project's context policy

Fix Direction

Add context_policy: ProjectContextPolicy field to NamespacedProject (or clarify the architectural separation between ContextConfig and ProjectContextPolicy in the spec and ensure the ACMS pipeline can load both).

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Tested by:** UAT tester instance `uat-tester-project-model-1` **Feature area:** Project Model — Context Policies ### What Was Tested The `NamespacedProject` domain model's ability to carry a `ProjectContextPolicy` as specified. ### Expected Behavior (from spec) The spec defines that projects have a context policy (`ProjectContextPolicy`) that controls what context (resources and files) is available during each ACMS phase (default → strategize → execute → apply). This policy uses view inheritance and should be a first-class field on the project domain model. ### Actual Behavior The `NamespacedProject` Pydantic model in `src/cleveragents/domain/models/core/project.py` has a `context_config: ContextConfig` field (for basic file filtering and size limits), but **does NOT have a `context_policy: ProjectContextPolicy` field** for the phase-based view inheritance policy: ```python class NamespacedProject(BaseModel): name: str namespace: str server: str | None description: str | None linked_resources: list[LinkedResource] context_config: ContextConfig # ← basic config only # ← NO context_policy: ProjectContextPolicy field created_at: datetime updated_at: datetime ``` The `ProjectContextPolicy` model exists in `src/cleveragents/domain/models/core/context_policy.py` with full phase-based view inheritance: ```python class ProjectContextPolicy(BaseModel): default_view: ContextView strategize_view: ContextView | None execute_view: ContextView | None apply_view: ContextView | None def resolve_view(self, phase: str) -> ContextView: ... ``` The `agents project context set/show/inspect/simulate` commands exist in `project_context.py` (45KB), but they appear to manage context policy separately from the `NamespacedProject` domain model, likely using their own storage mechanism. ### Code Location - `src/cleveragents/domain/models/core/project.py` — `NamespacedProject` has `context_config` but not `context_policy` - `src/cleveragents/domain/models/core/context_policy.py` — `ProjectContextPolicy` model exists but is not on `NamespacedProject` - `src/cleveragents/cli/commands/project_context.py` — context policy CLI commands (separate from project model) ### Impact - `NamespacedProject.context_config` only covers basic file filtering (ignore patterns, size limits, chunking) - The phase-based context policy (`ProjectContextPolicy`) is not accessible via the project domain model - The ACMS pipeline cannot load the project's context policy from the `NamespacedProject` object directly - `agents project show` doesn't display the project's context policy ### Fix Direction Add `context_policy: ProjectContextPolicy` field to `NamespacedProject` (or clarify the architectural separation between `ContextConfig` and `ProjectContextPolicy` in the spec and ensure the ACMS pipeline can load both). --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-08 19:49:43 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 19:59:07 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 20:12:39 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 referenced this issue

2026-04-08 20:22:25 +00:00

[Automated] CleverAgents Build Session - 2026-04-08 #4799

HAL9000 added the

labels

2026-04-08 23:00:06 +00:00

HAL9000 commented

2026-04-09 03:03:00 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Medium — spec compliance bug identified by UAT testing
Story Points: 3 (M) — targeted fix to align implementation with spec
MoSCoW: Must Have — spec compliance is required for correct system behavior

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Medium — spec compliance bug identified by UAT testing - **Story Points**: 3 (M) — targeted fix to align implementation with spec - **MoSCoW**: Must Have — spec compliance is required for correct system behavior --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 added

and removed

labels

2026-04-09 03:03:01 +00:00

HAL9000 added this to the v3.5.0 milestone