lead-sharing
Settles who gets which leads, which fields travel with them and on what basis, then applies that rule when the leads arrive and delivers each side its share. Use it when running `ref/mkt/co-marketing-
SKILL.mdplugins/partner-manager/skills/lead-sharing/SKILL.md
GitHubLead sharing
What it does
Settles who gets which leads, which fields travel with them and on what basis, then applies that rule when the leads arrive and delivers each side its share.
Where it happens
The agent does this in two activities across one reference process. Each one names the activity as that process words it.
- Settle the Lead Terms
ref/mkt/co-marketing-campaign, activity 2 - Run Co-Marketing Campaign
- Split and Hand over the Leads
ref/mkt/co-marketing-campaign, activity 14 - Run Co-Marketing Campaign
What to record
The partner record at a version, naming the agreement it rests on, the tier the partner holds, the date that tier was set and who set it. For everything the partner was given, the version it was at and the date it went to them. For every person the partner put through training, what they were trained on and the date they finished. A dated line for each obligation as it comes due, saying whether it was met and by whom. What the partner delivered back, counted against what the agreement asked for, at the cadence the process sets. The CONVENED and DONE records of everything it convenes, and the approval record behind every release and every tier change.
That contract covers every activity this abstract agent takes on, and it
is repeated in com.agentcatalog.agent/RECORDS.md. What the abstract
agent does not do is in com.agentcatalog.agent/NOT.md.