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

Merged

coilysiren merged 2 commits from aos/claude/ym96-nine-role into main

2026-08-16 00:33:46 +00:00

coilyco-ops commented

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

Member

Closes #1072.

Verified before fixing

All four drifts in the issue reproduce. .agents/roles.kdl carries eight role blocks - engineer, director, qa, ops, design, exec, creator, ai - and the docs described nine.

surface	said
`docs/FEATURES.md`	"nine deployed roles"
`docs/role-composed-principal-methods.md`	Community and Content Manager rows, no Creator row
`docs/role-skill-coverage-audit.md`	"all nine deployed", Corrections describing both retired roles
`scripts/aos-role-question.sh`	`community)` and `content)` cases, no `creator)`

The script one was the only live defect: aos role question cloud creator exited 2 on a role agent-compose actually deploys. It now resolves, and community correctly reports unknown.

The roster call

Kai chose: creator inherits all three orphaned methods. Its charter already says "respectful conversations" and "audience evidence", which is what tooling-customer-success-trust-repair, tooling-discord-community-host and tooling-customer-success-signal-routing are.

role creator {
    composed-skill "writing-*"
    composed-skill "personal-preference-*"
    composed-skill "personal-preferences"
+   composed-skill "tooling-customer-success-*"
+   composed-skill tooling-discord-community-host
}

It restores a claim the audit was making falsely

docs/role-skill-coverage-audit.md says every composed source is selected by at least one role except the two sales methods. #1072 established that was false for three more. Measured against roles.kdl after this change - 69 composed sources, unclaimed is exactly tooling-sales-discovery and tooling-sales-negotiation-architecture.

So the page's claim is true again rather than being weakened to match the drift, which is the better of the two available fixes.

Note

Community owns routine member interaction and a clean handoff in the handoffs section now reads Content Creator owns.... The boundary is unchanged - human stewards still retain moderation decisions - only the seat's name moved.

pre-commit clean on the changed files.

🤖 Generated with Claude Code

Closes #1072. ## Verified before fixing All four drifts in the issue reproduce. `.agents/roles.kdl` carries eight `role` blocks - engineer, director, qa, ops, design, exec, creator, ai - and the docs described nine. | surface | said | | --- | --- | | `docs/FEATURES.md` | "nine deployed roles" | | `docs/role-composed-principal-methods.md` | **Community** and **Content Manager** rows, no Creator row | | `docs/role-skill-coverage-audit.md` | "all nine deployed", Corrections describing both retired roles | | `scripts/aos-role-question.sh` | `community)` and `content)` cases, no `creator)` | The script one was the only live defect: `aos role question cloud creator` exited 2 on a role agent-compose actually deploys. It now resolves, and `community` correctly reports unknown. ## The roster call Kai chose: **creator inherits all three** orphaned methods. Its charter already says "respectful conversations" and "audience evidence", which is what `tooling-customer-success-trust-repair`, `tooling-discord-community-host` and `tooling-customer-success-signal-routing` are. ``` role creator { composed-skill "writing-*" composed-skill "personal-preference-*" composed-skill "personal-preferences" + composed-skill "tooling-customer-success-*" + composed-skill tooling-discord-community-host } ``` ## It restores a claim the audit was making falsely `docs/role-skill-coverage-audit.md` says every composed source is selected by at least one role except the two sales methods. #1072 established that was false for three more. Measured against `roles.kdl` after this change - 69 composed sources, unclaimed is exactly `tooling-sales-discovery` and `tooling-sales-negotiation-architecture`. So the page's claim is true again rather than being weakened to match the drift, which is the better of the two available fixes. ## Note `Community owns routine member interaction and a clean handoff` in the handoffs section now reads `Content Creator owns...`. The boundary is unchanged - human stewards still retain moderation decisions - only the seat's name moved. `pre-commit` clean on the changed files. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

coilyco-ops added 1 commit

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

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

ci / aos-cli-tests (pull_request) Successful in 18s

Details

ci / ward-doctor (pull_request) Successful in 11s

Details

ci / gate (pull_request) Failing after 28s

Details

35575c9282

agent-compose deploys eight roles. Four AOS surfaces still described nine and
named Community and Content Manager, which agent-compose has not deployed since
the v2 roster collapse.

- docs/FEATURES.md said nine deployed roles
- docs/role-composed-principal-methods.md carried Community and Content Manager
  rows and no Creator row
- docs/role-skill-coverage-audit.md opened on nine, and its Corrections section
  described both retired roles
- scripts/aos-role-question.sh had community) and content) cases and no
  creator), so `aos role question cloud creator` exited 2 on a deployed role

The substantive half was three composed sources orphaned when Community stopped
being a role: the two tooling-customer-success-* methods and
tooling-discord-community-host. Kai's call, asked and answered: creator
inherits all three. Its charter already reads "respectful conversations" and
"audience evidence", which is what those methods are.

That also restores a claim the audit page was making falsely. It said every
composed source is selected by at least one role except the two sales methods.
Measured against roles.kdl, unclaimed is now exactly those two again.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

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

coilyco-ops added 1 commit

2026-08-15 23:22:18 +00:00

test(roles): follow the roster to eight in the role-question test

ci / aos-cli-tests (pull_request) Successful in 18s

Details

ci / ward-doctor (pull_request) Successful in 11s

Details

ci / gate (pull_request) Successful in 49s

Details

7de7421921

The gate failed on test_question_accepts_community_role, which asserts a
role this branch retires. The script, roles.kdl and the docs all moved to
eight roles; the test still pinned nine.

Repointed at creator, the seat that absorbed community's methods, so the
case keeps covering what it covered: a non-core role name resolving
through the dispatch. Added the negative it was hiding, since the PR body
claims community now reports unknown and nothing tested that.

`ward exec repo-test-gate` exits 0, 533 passed.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>