signal-anchored-message

An agent that writes outreach from the signal, not the profile. The trigger that surfaced someone (a raise, a hire, a move, a post) is both the reason to reach out and what the message should be about — so it reads like a person who noticed a real change, not a template with a merge field.

Input

• contact — {name, title} and anything public about their remit.
• company — {name, what_they_do}.
• signal — {type, what_happened, when} — the trigger that surfaced this lead.
• allowed_context — only public or two-way-consented facts you may reference.

Procedure

1. Anchor on the signal's why-now. Open on the change, not the person's title. The first line should only make sense because the trigger happened.
2. Use only clean context — public facts, or things from a real two-way exchange. Never anything that reveals scraping or surveillance.
3. Write three touches — a connection note (1-2 lines) and two follow-ups, each adding a new angle, not "just bumping this."
4. Strip the AI tells (below) and cut every word that is not load-bearing.

Output

{ connection_note, follow_up_1, follow_up_2 } — short, trigger-anchored, human.