EPIC: Guard Enforcement & Safety Profiles — Automation Profile Resolution #4951

Open
opened 2026-04-08 23:39:39 +00:00 by freemo · 2 comments
Owner

Epic: Guard Enforcement & Safety Profiles

This Epic covers the implementation of guard enforcement (denylist, budget caps, tool call limits) and automation profile resolution with correct precedence (plan > action > global). It also covers the require_sandbox, require_checkpoints, allow_unsafe_tools safety profile fields.

Demonstrable Capability

When this Epic is complete, a developer can:

  1. Configure automation profiles with safety constraints
  2. Verify that guards are enforced during plan execution
  3. Confirm that automation profile resolution follows correct precedence
  4. Test that require_sandbox and require_checkpoints are enforced

Child Issues

Definition of Done

  • All child issues are closed
  • Guard enforcement works (denylist, budget caps, tool call limits)
  • Automation profile resolution precedence correct (plan > action > global)
  • require_sandbox, require_checkpoints, allow_unsafe_tools enforced
  • Automation profile YAML schema matches spec (top-level fields, not nested under safety:)
  • AutomationProfileService._DEFAULT_PROFILE is supervised (not manual)
  • All nox stages pass
  • Coverage >= 97%

Metadata

  • Branch Naming Convention: feat/m6/guard-enforcement
  • Milestone: v3.5.0
  • Parent Legendary: #4944

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

## Epic: Guard Enforcement & Safety Profiles This Epic covers the implementation of guard enforcement (denylist, budget caps, tool call limits) and automation profile resolution with correct precedence (plan > action > global). It also covers the `require_sandbox`, `require_checkpoints`, `allow_unsafe_tools` safety profile fields. ### Demonstrable Capability When this Epic is complete, a developer can: 1. Configure automation profiles with safety constraints 2. Verify that guards are enforced during plan execution 3. Confirm that automation profile resolution follows correct precedence 4. Test that `require_sandbox` and `require_checkpoints` are enforced ### Child Issues <!-- Updated by automation after child issues are created --> ### Definition of Done - [ ] All child issues are closed - [ ] Guard enforcement works (denylist, budget caps, tool call limits) - [ ] Automation profile resolution precedence correct (plan > action > global) - [ ] `require_sandbox`, `require_checkpoints`, `allow_unsafe_tools` enforced - [ ] Automation profile YAML schema matches spec (top-level fields, not nested under `safety:`) - [ ] `AutomationProfileService._DEFAULT_PROFILE` is `supervised` (not `manual`) - [ ] All nox stages pass - [ ] Coverage >= 97% ## Metadata - **Branch Naming Convention**: `feat/m6/guard-enforcement` - **Milestone**: v3.5.0 - **Parent Legendary**: #4944 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: High — Guard enforcement and safety profiles are critical for safe autonomous execution; they prevent dangerous operations and enforce automation safety boundaries
  • Milestone: v3.5.0
  • Story Points: 34 — XXL — Epic covering guard enforcement, safety profiles, automation profile resolution, and shell safety blocking
  • MoSCoW: Must Have — Safety profiles are non-negotiable for production autonomous operation; the spec explicitly requires guard enforcement to prevent unsafe operations
  • Parent Legendary: #4944

This Epic is valid. It covers guard enforcement, automation profile resolution, and safety blocking behavior.


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

Issue triaged by project owner: - **State**: Verified - **Priority**: High — Guard enforcement and safety profiles are critical for safe autonomous execution; they prevent dangerous operations and enforce automation safety boundaries - **Milestone**: v3.5.0 - **Story Points**: 34 — XXL — Epic covering guard enforcement, safety profiles, automation profile resolution, and shell safety blocking - **MoSCoW**: Must Have — Safety profiles are non-negotiable for production autonomous operation; the spec explicitly requires guard enforcement to prevent unsafe operations - **Parent Legendary**: #4944 This Epic is valid. It covers guard enforcement, automation profile resolution, and safety blocking behavior. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 added this to the v3.5.0 milestone 2026-04-09 00:46:59 +00:00
Owner

Child Issues Created

The following child issues have been created for this Epic:

  • #5012 — feat(guards): implement guard enforcement for denylist, budget caps, and tool call limits (foundational — must be done first)
  • #5014 — feat(automation): fix automation profile resolution precedence and schema alignment with spec (depends on #5012)

Milestone: v3.5.0 (active — 505 open, 188 closed)

Dependency Chain: #5012#5014 → Epic #4951


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

## Child Issues Created The following child issues have been created for this Epic: - [ ] #5012 — feat(guards): implement guard enforcement for denylist, budget caps, and tool call limits *(foundational — must be done first)* - [ ] #5014 — feat(automation): fix automation profile resolution precedence and schema alignment with spec *(depends on #5012)* **Milestone**: v3.5.0 (active — 505 open, 188 closed) **Dependency Chain**: #5012 → #5014 → Epic #4951 --- **Automated by CleverAgents Bot** Supervisor: Epic Planning | Agent: epic-planner
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks Depends on
Reference
cleveragents/cleveragents-core#4951
No description provided.