Update Content Manager for the Sales, Content, and Outreach trifecta #186

New issue

Closed

opened 2026-08-05 00:39:18 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-05 00:39:18 +00:00

Member

Parent

#142

What to build

Update Content Manager so the role is the content leg of a clear market-facing trifecta:

Outreach opens qualified conversations.
Sales converts qualified interest into mutual commitment.
Content creates accurate, reusable proof that compounds across both loops.

Keep the existing Content Manager mission across technical documentation, public writing, and media. Add an explicit proof-building and reuse contract for demos, case studies, architecture narratives, presentations, and channel adaptations.

Role contract update

Content Manager owns:

truthful reusable narratives grounded in real portfolio evidence
demo scripts, walkthroughs, case studies, architecture explanations, and supporting media
channel-specific adaptations for websites, social posts, recruiter packets, presentations, and outreach support
editorial coherence, audience fit, provenance, and claim discipline
reusable content systems that reduce repeated Sales and Outreach effort
repository-prescribed validation and delivery of content artifacts

Content Manager does not own:

target selection, first-touch contact, or response classification, which belong to Outreach
opportunity qualification, interviews, objections, negotiation, or commitment, which belong to Sales
portfolio priorities, which remain with Portfolio Strategist
product experience and visual interaction design, which remain with Designer
publication or sending without explicit runtime authority
invented customers, revenue, adoption, scale, outcomes, or production claims

Evaluation update

Extend the current Content Manager matrix with the new role boundaries and proof-building work. Derive the evaluated roster from the owning loader rather than assuming an eight-role, ten-role, or other fixed count. Include AI Engineer from #175 if it has landed when this work begins.

Acceptance criteria

Content Manager explicitly owns reusable proof artifacts for the Sales, Content, and Outreach loop.
The role retains technical documentation, public writing, media, editorial fitness, and channel adaptation as first-class work.
Adjacent-role cases distinguish Content Manager from Outreach, Sales, Designer, Community Manager, and AI Engineer when present.
Evaluation cases require provenance and reject invented commercial or operational claims.
Handoff contracts let Outreach request contact-specific adaptations and Sales request opportunity-specific evidence without transferring ownership of the reusable source artifact.
Publication and sending remain outside role authority unless the runtime explicitly grants them.
The complete current roster evaluation and scorecard are regenerated from the owning loader.
Roster output, identity artifacts, snapshots, documentation, migration guidance, and feature inventory remain consistent.
Repository validation passes through declared Ward verbs.

Blocked by

#184
#185
Cost-controlled model execution is also gated by coilyco-bridge/agentic-os-hardware#83 and any approved downstream model route.

## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/142 ## What to build Update **Content Manager** so the role is the content leg of a clear market-facing trifecta: * Outreach opens qualified conversations. * Sales converts qualified interest into mutual commitment. * Content creates accurate, reusable proof that compounds across both loops. Keep the existing Content Manager mission across technical documentation, public writing, and media. Add an explicit proof-building and reuse contract for demos, case studies, architecture narratives, presentations, and channel adaptations. ## Role contract update Content Manager owns: * truthful reusable narratives grounded in real portfolio evidence * demo scripts, walkthroughs, case studies, architecture explanations, and supporting media * channel-specific adaptations for websites, social posts, recruiter packets, presentations, and outreach support * editorial coherence, audience fit, provenance, and claim discipline * reusable content systems that reduce repeated Sales and Outreach effort * repository-prescribed validation and delivery of content artifacts Content Manager does not own: * target selection, first-touch contact, or response classification, which belong to Outreach * opportunity qualification, interviews, objections, negotiation, or commitment, which belong to Sales * portfolio priorities, which remain with Portfolio Strategist * product experience and visual interaction design, which remain with Designer * publication or sending without explicit runtime authority * invented customers, revenue, adoption, scale, outcomes, or production claims ## Evaluation update Extend the current Content Manager matrix with the new role boundaries and proof-building work. Derive the evaluated roster from the owning loader rather than assuming an eight-role, ten-role, or other fixed count. Include AI Engineer from https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/175 if it has landed when this work begins. ## Acceptance criteria * [ ] Content Manager explicitly owns reusable proof artifacts for the Sales, Content, and Outreach loop. * [ ] The role retains technical documentation, public writing, media, editorial fitness, and channel adaptation as first-class work. * [ ] Adjacent-role cases distinguish Content Manager from Outreach, Sales, Designer, Community Manager, and AI Engineer when present. * [ ] Evaluation cases require provenance and reject invented commercial or operational claims. * [ ] Handoff contracts let Outreach request contact-specific adaptations and Sales request opportunity-specific evidence without transferring ownership of the reusable source artifact. * [ ] Publication and sending remain outside role authority unless the runtime explicitly grants them. * [ ] The complete current roster evaluation and scorecard are regenerated from the owning loader. * [ ] Roster output, identity artifacts, snapshots, documentation, migration guidance, and feature inventory remain consistent. * [ ] Repository validation passes through declared Ward verbs. ## Blocked by * https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/184 * https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/185 * Cost-controlled model execution is also gated by https://forgejo.coilysiren.me/coilyco-bridge/agentic-os-hardware/issues/83 and any approved downstream model route.

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

2026-08-05 00:40:31 +00:00

Align reusable Content skills with demo and proof conversion #889

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-05 00:42:00 +00:00

coilyco-ops commented

2026-08-05 00:48:23 +00:00

Author

Member

Program tracker: coilysiren/inbox#329

This role issue keeps its existing Agent Compose parent. The inbox tracker owns the wider DeepSeek cost-control gate and cross-repository sequence.

Program tracker: https://forgejo.coilysiren.me/coilysiren/inbox/issues/329 This role issue keeps its existing Agent Compose parent. The inbox tracker owns the wider DeepSeek cost-control gate and cross-repository sequence.

coilyco-ops referenced this issue from a commit

2026-08-06 00:15:01 +00:00

feat(content): define reusable proof market trifecta (#186)

coilyco-ops referenced this issue from a commit

2026-08-06 00:24:08 +00:00

fix(roster): align loader-derived role contracts (#186)