Collapse audience-facing roles into Creator #222

New issue

Closed

opened 2026-08-06 08:38:59 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-06 08:38:59 +00:00

Member

Outcome

Collapse the Core Roster's four audience-facing roles into one role.

Canonical slug - creator
Display name - Content Creator
Remove the legacy Core Roster slugs content, community, outreach, and sales.
Replace Content Manager naming everywhere with Content Creator.
Merge the useful Content, Community, Outreach, and Sales responsibilities into the Creator charter.

Ordinary uses of the noun "content" remain unchanged.

Boundary

Creator owns the audience-facing loop from community signals through accurate artifacts, contact-specific adaptation, sustained conversation, and evidence-qualified interest. Portfolio Strategist still decides where attention should go. Director and Kai retain consequential coordination and commitments.

Role doctrine must not grant permission to post, publish, send, moderate, promise terms, accept offers, or expose material externally. Those actions remain separately authorized by the task, runtime, and user.

Acceptance

The embedded Core Roster contains eight roles and exposes creator as its only audience-facing role.
No canonical role, seat, identity card, role skill, evaluation matrix, compatibility rule, documentation page, or fixture retains the removed role identities.
Content Creator naming replaces Content Manager everywhere that identifies the current role.
Creator's charter retains the useful work of the four removed roles without inventing an active company, customer base, sales pipeline, or commercial commitment.
Cross-role boundaries and evaluation coverage target Creator.
README and docs/FEATURES.md describe the eight-role roster.
Go tests, packaging checks, build, lint, palette tests, and pre-commit pass.
The intentionally deferred fresh scorecard and replacement of immutable old-pack evidence are tracked in #223. Until then, ward exec test reaches and fails only its scorecard freshness check.

## Outcome Collapse the Core Roster's four audience-facing roles into one role. * Canonical slug - `creator` * Display name - `Content Creator` * Remove the legacy Core Roster slugs `content`, `community`, `outreach`, and `sales`. * Replace Content Manager naming everywhere with Content Creator. * Merge the useful Content, Community, Outreach, and Sales responsibilities into the Creator charter. Ordinary uses of the noun "content" remain unchanged. ## Boundary Creator owns the audience-facing loop from community signals through accurate artifacts, contact-specific adaptation, sustained conversation, and evidence-qualified interest. Portfolio Strategist still decides where attention should go. Director and Kai retain consequential coordination and commitments. Role doctrine must not grant permission to post, publish, send, moderate, promise terms, accept offers, or expose material externally. Those actions remain separately authorized by the task, runtime, and user. ## Acceptance * The embedded Core Roster contains eight roles and exposes `creator` as its only audience-facing role. * No canonical role, seat, identity card, role skill, evaluation matrix, compatibility rule, documentation page, or fixture retains the removed role identities. * Content Creator naming replaces Content Manager everywhere that identifies the current role. * Creator's charter retains the useful work of the four removed roles without inventing an active company, customer base, sales pipeline, or commercial commitment. * Cross-role boundaries and evaluation coverage target Creator. * README and `docs/FEATURES.md` describe the eight-role roster. * Go tests, packaging checks, build, lint, palette tests, and pre-commit pass. * The intentionally deferred fresh scorecard and replacement of immutable old-pack evidence are tracked in #223. Until then, `ward exec test` reaches and fails only its scorecard freshness check.

coilyco-ops referenced this issue

2026-08-06 08:53:42 +00:00

Refresh evaluations for the eight-role Creator roster #223

coilyco-ops referenced this issue from a commit

2026-08-06 08:54:35 +00:00

feat: collapse audience roles into Content Creator, closes #222

coilyco-ops closed this issue

2026-08-06 08:54:35 +00:00