Separate agent-compose provider policy from Ward role authority #664

Closed
opened 2026-07-23 23:20:41 +00:00 by coilyco-ops · 0 comments
Owner

Problem

AOS currently mixes agent-compose provider policy with Ward execution policy in .ward/roles.kdl. Agent-compose now owns role-intent routes through provider configuration, while Ward must retain only executable authority and runtime controls.

Change

  • Keep composed-skill bindings and intent-to-harness routes in .agents/roles.kdl.
  • Keep guardfiles, execution defaults, and authority policy in .ward/roles.kdl.
  • Point harness-board synchronization, Ward configuration, documentation, and tests at their owning files.

Acceptance

  • Provider and Ward policy have distinct canonical sources.
  • Harness-board synchronization updates the provider source.
  • Repository tests and the complete pre-commit suite pass.
  • The commit lands on canonical main.
## Problem AOS currently mixes agent-compose provider policy with Ward execution policy in `.ward/roles.kdl`. Agent-compose now owns role-intent routes through provider configuration, while Ward must retain only executable authority and runtime controls. ## Change * Keep composed-skill bindings and intent-to-harness routes in `.agents/roles.kdl`. * Keep guardfiles, execution defaults, and authority policy in `.ward/roles.kdl`. * Point harness-board synchronization, Ward configuration, documentation, and tests at their owning files. ## Acceptance * Provider and Ward policy have distinct canonical sources. * Harness-board synchronization updates the provider source. * Repository tests and the complete pre-commit suite pass. * The commit lands on canonical `main`.
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
coilyco-flight-deck/agentic-os#664
No description provided.