P0: migrate AOS role surfaces to the Agent Compose v2 roster #852

New issue

Closed

opened 2026-08-02 05:29:58 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-02 05:29:58 +00:00

Member

Problem

Agent Compose v2.0.0 is released and accepts only the eight Core Roster slugs. AOS still publishes the thirteen v1 roles in .agents/roles.kdl, .agents/role-harnesses.yaml, compiled launcher projections, tests, smoke paths, and documentation.

A full v2 composition currently fails before provider selection with:

source "aos" binds composed skills to undefined role "advisor"

This blocks the AOSK context-reduction P0 even though AOSK itself composes successfully in isolation with only its ordinary provider anchor.

Required migration

Keep engineer, director, qa, ops, and community.
Rename designer to design.
Merge advisor, pm, and ceo into strats, deduplicating composed skills and intent routes.
Merge technical-writer and social into content, deduplicating composed skills and intent routes.
Remove sales and customer-success as Core Roster roles. Leave their unique composed methods unbound unless a current v2 mission owner is explicit.
Migrate the AOS-owned harness routing board and every generated or embedded consumer to the same eight-role contract.
Preserve role composition as knowledge only. Do not broaden Ward or AOSGuard authority.

Acceptance

The canonical AOS provider composes under Agent Compose v2 for every Core Roster role.
An isolated strats composition with AOS plus AOSK succeeds.
The AOS harness board, compiled JSON, role-personality projection, launcher profiles, smoke paths, tests, and role docs use only v2 role slugs.
Legacy v1 context reports remain clearly historical or are regenerated under v2 names where they represent current state.
AOS validation and pre-commit pass.
The landed commit closes this issue.

## Problem Agent Compose v2.0.0 is released and accepts only the eight Core Roster slugs. AOS still publishes the thirteen v1 roles in `.agents/roles.kdl`, `.agents/role-harnesses.yaml`, compiled launcher projections, tests, smoke paths, and documentation. A full v2 composition currently fails before provider selection with: ```text source "aos" binds composed skills to undefined role "advisor" ``` This blocks the AOSK context-reduction P0 even though AOSK itself composes successfully in isolation with only its ordinary provider anchor. ## Required migration * Keep `engineer`, `director`, `qa`, `ops`, and `community`. * Rename `designer` to `design`. * Merge `advisor`, `pm`, and `ceo` into `strats`, deduplicating composed skills and intent routes. * Merge `technical-writer` and `social` into `content`, deduplicating composed skills and intent routes. * Remove `sales` and `customer-success` as Core Roster roles. Leave their unique composed methods unbound unless a current v2 mission owner is explicit. * Migrate the AOS-owned harness routing board and every generated or embedded consumer to the same eight-role contract. * Preserve role composition as knowledge only. Do not broaden Ward or AOSGuard authority. ## Acceptance * The canonical AOS provider composes under Agent Compose v2 for every Core Roster role. * An isolated `strats` composition with AOS plus AOSK succeeds. * The AOS harness board, compiled JSON, role-personality projection, launcher profiles, smoke paths, tests, and role docs use only v2 role slugs. * Legacy v1 context reports remain clearly historical or are regenerated under v2 names where they represent current state. * AOS validation and pre-commit pass. * The landed commit closes this issue. ## Related * coilyco-flight-deck/agent-compose#176 * coilyco-bridge/agentic-os-kai#810

coilyco-ops added the

autonomy

live-collab

priority

labels

2026-08-02 05:30:02 +00:00

coilyco-ops referenced this issue from a commit

2026-08-02 05:46:45 +00:00

feat(compose): migrate AOS to the v2 roster, closes #852

coilyco-ops closed this issue

2026-08-02 06:12:30 +00:00