Add Outreach as a Core Roster role #184

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

Parent

#142

What to build

Add Outreach as a first-party Core Roster role.

Proposed slug: outreach.

This explicitly reopens the v2 decision to ship exactly eight roles. The new market loop has three distinct owners:

  • Outreach opens qualified conversations.
  • Sales converts qualified interest into mutual commitment.
  • Content creates reusable proof that makes both loops more effective.

Outreach turns a chosen market, audience, or target set into respectful, qualified first conversations. It owns the path from target selection through a substantive response, then hands the opportunity to Sales.

Role contract

Outreach owns:

  • target research, segmentation, and prioritization within an accepted strategy
  • channel choice and contact-path research
  • evidence-backed personalization
  • first-touch and bounded follow-up drafting
  • qualification thresholds and response classification
  • experiment design, response measurement, and stop conditions
  • clean handoff of qualified interest to Sales
  • repository-prescribed validation and delivery of outreach artifacts

Outreach does not own:

  • portfolio strategy or market selection, which remain with Portfolio Strategist
  • reusable narrative, demo, case-study, or channel content, which remain with Content Manager
  • opportunity conversion, interviews, discovery after qualification, objections, negotiation, or commitment, which remain with Sales
  • durable community relationships or community governance, which remain with Community Manager
  • publication, sending, account access, or external commitments without explicit runtime authority
  • spam, bulk-contact theater, invented familiarity, or unsupported claims

Core Roster integration

Proposed identity:

  • Display name: Outreach
  • Slug: outreach
  • Purpose: Open qualified conversations with the right people through relevant, respectful contact.
  • Role skill: role-outreach
  • Proposed meld: Curious, Diplomatic, Editorial, Bold

Select and validate the seat identities, palette, compatibility, and derived artifacts through the existing Core Roster contracts. Do not copy Kai-specific career filters or private target data into the public role.

Acceptance criteria

  • Outreach ships as a complete first-party Core Roster role with the stated mission and bounded authority.
  • The v2 roster documentation explicitly records why the earlier fixed eight-role decision changed.
  • Outreach has a complete current evaluation pack covering mission fit, personality expression, authority boundaries, completion ownership, and a representative portfolio replay.
  • Adjacent-role cases distinguish Outreach from Sales, Content Manager, Community Manager, and Portfolio Strategist.
  • Evaluation cases reject spam, invented relationships, unsupported personalization, and unauthorized sending or publication.
  • Handoff output makes target, evidence, channel, contact state, qualification result, and next owner explicit.
  • Model-class support remains fail closed and is backed by current scored evidence.
  • Roster output, identity artifacts, snapshots, documentation, migration guidance, scorecards, and feature inventory remain consistent.
  • Repository validation passes through declared Ward verbs.

Blocked by

  • Cost-controlled evaluation execution is blocked by the decision in coilyco-bridge/agentic-os-hardware#83 and, if that decision is positive, the downstream Agent Proxy-routed model path it requires.
  • Role drafting and deterministic validation may proceed before that gate. Do not spend the remaining frontier subscription quota on the new high-volume evaluation matrix.
## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/142 ## What to build Add **Outreach** as a first-party Core Roster role. Proposed slug: `outreach`. This explicitly reopens the v2 decision to ship exactly eight roles. The new market loop has three distinct owners: * Outreach opens qualified conversations. * Sales converts qualified interest into mutual commitment. * Content creates reusable proof that makes both loops more effective. Outreach turns a chosen market, audience, or target set into respectful, qualified first conversations. It owns the path from target selection through a substantive response, then hands the opportunity to Sales. ## Role contract Outreach owns: * target research, segmentation, and prioritization within an accepted strategy * channel choice and contact-path research * evidence-backed personalization * first-touch and bounded follow-up drafting * qualification thresholds and response classification * experiment design, response measurement, and stop conditions * clean handoff of qualified interest to Sales * repository-prescribed validation and delivery of outreach artifacts Outreach does not own: * portfolio strategy or market selection, which remain with Portfolio Strategist * reusable narrative, demo, case-study, or channel content, which remain with Content Manager * opportunity conversion, interviews, discovery after qualification, objections, negotiation, or commitment, which remain with Sales * durable community relationships or community governance, which remain with Community Manager * publication, sending, account access, or external commitments without explicit runtime authority * spam, bulk-contact theater, invented familiarity, or unsupported claims ## Core Roster integration Proposed identity: * Display name: **Outreach** * Slug: `outreach` * Purpose: **Open qualified conversations with the right people through relevant, respectful contact.** * Role skill: `role-outreach` * Proposed meld: Curious, Diplomatic, Editorial, Bold Select and validate the seat identities, palette, compatibility, and derived artifacts through the existing Core Roster contracts. Do not copy Kai-specific career filters or private target data into the public role. ## Acceptance criteria * [ ] Outreach ships as a complete first-party Core Roster role with the stated mission and bounded authority. * [ ] The v2 roster documentation explicitly records why the earlier fixed eight-role decision changed. * [ ] Outreach has a complete current evaluation pack covering mission fit, personality expression, authority boundaries, completion ownership, and a representative portfolio replay. * [ ] Adjacent-role cases distinguish Outreach from Sales, Content Manager, Community Manager, and Portfolio Strategist. * [ ] Evaluation cases reject spam, invented relationships, unsupported personalization, and unauthorized sending or publication. * [ ] Handoff output makes target, evidence, channel, contact state, qualification result, and next owner explicit. * [ ] Model-class support remains fail closed and is backed by current scored evidence. * [ ] Roster output, identity artifacts, snapshots, documentation, migration guidance, scorecards, and feature inventory remain consistent. * [ ] Repository validation passes through declared Ward verbs. ## Blocked by * Cost-controlled evaluation execution is blocked by the decision in https://forgejo.coilysiren.me/coilyco-bridge/agentic-os-hardware/issues/83 and, if that decision is positive, the downstream Agent Proxy-routed model path it requires. * Role drafting and deterministic validation may proceed before that gate. Do not spend the remaining frontier subscription quota on the new high-volume evaluation matrix.
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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-compose#184
No description provided.