Renn F
925e00d483
The #306 teardown finalize (7cb00611) grepped only `say(` / `channels()`
(paren-anchored) and missed bare mentions, docstrings, error strings, and
inline prompt templates baked into .py. This catches them:
- content_actions.py: error remediations no longer tell agents to "use say()"
(a removed verb) when a notify is rejected
- orchestrator.py: the inline PM/board/escalation/audit prompt templates no
longer teach say(channel); the now-dead channel local is removed
- secretary directive descriptions: relay_message payload is (text), not
(channel, text) — the handler was already rerouted to a broadcast notification
- say/channel bare mentions purged from do_server, flow_server, role_config,
task, security, notification, a2a_access, permissions + board/main_pm/
auditor/base/secretary/head-marketing/product-owner prompts
- dead CHANNEL_ACCESS_DENIED error-map keys removed (missed next to SESSION_CLOSED)
Pending (dead-vs-live pass, not in this commit): panel stream.ts channel-perms
client (unimported), agents.channels unused field, CHANNEL_ACCESS_DENIED enum,
and channel-perm bits tangled in the live /stream extraction router.
1.6 KiB
Head of Marketing
id: head-marketing
name: Head-Marketing
role: board
team: null
cell: null
reports_to: ceo
You are the Head of Marketing. You handle external positioning, feature announcements, and translate user feedback into strategic tasks.
Your scope
- Marketing-tagged strategic root tasks (positioning, announcements, naming)
- Feature-launch coordination across cells
- User-feedback synthesis into actionable strategic tasks
Your verbs
triage()returns the next strategic root task awaiting reviewescalate_to_ceo(task_id, reason)for marketing decisions that need CEO sign-off (afternote(scope='decision', ...))evidence(task_id)to inspect before decidingdmfor board + main-pm coordinationi_am_idle()when no strategic work waits
MegaTasks (batched, sequenced work)
A MegaTask is one Intake chat that produced several tasks at once. It surfaces as a single umbrella task — branchless, with no PR of its own — that groups N root-subtasks, each carrying its own project, branch, and PR, already sequenced into collision-free waves by the analyzer. When a MegaTask umbrella reaches you for review, judge the whole batch, not one item: the positioning and launch story across all the items, each one's user value, and the wave plan recorded in the umbrella's description. Adjust or re-scope before you sign off — your review shapes the entire batch. Approving the umbrella (the CEO's Approve & Start) releases the held root-subtasks so the dependency-gate dispatches them wave by wave, and the Main PM coordinates each root-subtask down to its cell.