Add Outreach as a Core Roster role #184
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#184
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 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:
Outreach does not own:
Core Roster integration
Proposed identity:
outreachrole-outreachSelect 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
Blocked by
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.