docs: retire the nine-role roster from AOS docs and the role-question probe #1072

New issue

Closed

opened 2026-08-15 21:57:41 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-15 21:57:41 +00:00

Member

agent-compose catalog roles (v2.22.0) reports eight deployed roles:
engineer, director, qa, ops, design, exec, creator, ai. There is no
community role and no content role. .agents/roles.kdl and
.agents/harness-launch-profiles.yaml agree with that.

Several AOS surfaces still describe the pre-v2 nine-role roster.

Observed drift

docs/FEATURES.md line 17 - "nine deployed roles including AI Engineer"
docs/role-composed-principal-methods.md - the matrix carries Community and Content Manager rows and has no Creator row
docs/role-skill-coverage-audit.md - opens with "all nine deployed Agent Compose roles", and its Corrections section still describes Community and Content
scripts/aos-role-question.sh - has community) and content) cases and no creator) case, so aos role question cloud creator exits 2 with "unknown role creator"

The substantive part

docs/role-skill-coverage-audit.md claims every composed source is selected
by at least one role except the two sales methods. That is false for three
more, all orphaned when Community stopped being a role:

tooling-customer-success-signal-routing
tooling-customer-success-trust-repair
tooling-discord-community-host

Creator is the closest successor by charter - "respectful conversations"
and audience evidence - but assigning them is a roster decision rather than
a config repair, so it is not folded into the exec restoration.

Not this issue

The exec role's own missing block is restored separately in the PR that
filed this.

Found while restoring the exec role block.

`agent-compose catalog roles` (v2.22.0) reports eight deployed roles: engineer, director, qa, ops, design, exec, creator, ai. There is no `community` role and no `content` role. `.agents/roles.kdl` and `.agents/harness-launch-profiles.yaml` agree with that. Several AOS surfaces still describe the pre-v2 nine-role roster. ## Observed drift * `docs/FEATURES.md` line 17 - "nine deployed roles including AI Engineer" * `docs/role-composed-principal-methods.md` - the matrix carries **Community** and **Content Manager** rows and has no **Creator** row * `docs/role-skill-coverage-audit.md` - opens with "all nine deployed Agent Compose roles", and its Corrections section still describes Community and Content * `scripts/aos-role-question.sh` - has `community)` and `content)` cases and no `creator)` case, so `aos role question cloud creator` exits 2 with "unknown role creator" ## The substantive part `docs/role-skill-coverage-audit.md` claims every composed source is selected by at least one role except the two sales methods. That is false for three more, all orphaned when Community stopped being a role: * `tooling-customer-success-signal-routing` * `tooling-customer-success-trust-repair` * `tooling-discord-community-host` Creator is the closest successor by charter - "respectful conversations" and audience evidence - but assigning them is a roster decision rather than a config repair, so it is not folded into the exec restoration. ## Not this issue The `exec` role's own missing block is restored separately in the PR that filed this. Found while restoring the `exec` role block.

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-15 22:09:25 +00:00

docs(roles): retire the nine-role roster, and give creator the orphaned methods #1075

coilyco-ops referenced this issue

2026-08-15 23:21:11 +00:00

Nothing validates .agents/roles.kdl against the composed catalogue, which is why a deleted role block and three orphaned methods both went unnoticed #1076