@sellable/mcp 0.1.204 → 0.1.205

package/agents/post-find-leads-message-scout.md

@@ -44,9 +44,15 @@ the branch input.
 2. Use that prompt as the drafting contract. Do not use any alternate prompt,
    examples-only shortcut, or create-campaign safety/checklist instructions as a
    substitute for the full message prompt.
-3. Draft only from the campaign brief, selected source context, and initial
+3. Follow the prompt's `Reference Asset Loading` section: load the required
+   pre-draft reference pack before drafting, load final-pass references before
+   approval, and report which assets were used and why. If those required
+   assets cannot be loaded, return `blocked` / `retry-needed`; do not draft from
+   the prompt alone. `ai-tells.md` is part of the required pack and is never
+   optional.
+4. Draft only from the campaign brief, selected source context, and initial
    campaign-table execution slice rows supplied by the parent.
-4. Keep the work provisional until the user chooses `Use Template` in Messages.
+5. Keep the work provisional until the user chooses `Use Template` in Messages.
 
 ## Owned Output
 
@@ -54,6 +60,8 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
+- `Reference Asset Loading` note naming the required and conditional assets used
+  and why each was used
 - one rendered good-fill sample for a plausible passing campaign-table row
 - one omit/fallback sample when the row signal is not safe
 - pass/fail notes against the generate-messages quality gates
@@ -125,10 +133,14 @@ reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
 hope this is relevant`, `saw you in a few conversations about [topic], so
 may be off, but this seemed relevant`, `saw you might be interested in [topic],
 so hope this is relevant`, `hope this is relevant if [topic] is on your plate`,
-or `saw you raise your hand for [topic], so figured this was (hopefully) worth sending`.
+or `found you in a thread about [topic], so may be off, but this seemed relevant`.
+Only use `saw you raise your hand for [topic], so figured this was (hopefully)
+worth sending` when the source was an explicit lead-magnet comment, reply, or
+opt-in.
 The cheekier `saw you raise your hand for [topic] (creepy to reach out based
 on that, i know) - but this felt too on the nose to ignore` version is also
-allowed when the sender's voice can carry it. Bad: `you commented on...`, `you reacted
+allowed only for explicit lead-magnet comments, replies, or opt-ins and when the
+sender's voice can carry it. Bad: `you commented on...`, `you reacted
 to...`, `saw you engaging with...`, `your LinkedIn activity...`, `you might
 not remember the thread...`, or `found you through [source] and your role
 looked close...`. Otherwise omit the engagement signal and use role/company/problem context.

package/dist/tools/prompts.js

@@ -330,7 +330,7 @@ export function getPostFindLeadsScoutRegistry() {
                 "basis.workflowTableId",
                 "basis.reviewSampleRowHash or basis.reviewSampleRowIds",
             ],
-            promptRequired: 'get_subskill_prompt({ subskillName: "generate-messages" }); the full generate-messages prompt is required for normal message drafting',
+            promptRequired: 'get_subskill_prompt({ subskillName: "generate-messages" }); the full generate-messages prompt is required for normal message drafting, then follow its Reference Asset Loading step and load the required pre-draft reference pack before drafting. ai-tells.md is required and never optional. If the required assets cannot be loaded, return blocked/retry-needed instead of drafting from the prompt alone.',
             basisFields: [
                 "campaign revision or updatedAt",
                 "brief hash",
@@ -343,6 +343,7 @@ export function getPostFindLeadsScoutRegistry() {
             messageDraftOutputFields: [
                 "templateRecommendation",
                 "tokenFillRules",
+                "referenceAssetLoading",
                 "renderedSample",
                 "concerns",
                 "status",
@@ -357,7 +358,7 @@ export function getPostFindLeadsScoutRegistry() {
         usage: {
             codex: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not spawn returned post-lead scout names before that question. Once the user answers, spawn Message Draft Builder from the same campaign/table basis. If the user chooses filters, also spawn Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
             claude: "After confirm_lead_list copies source rows and the initial campaign-table execution slice exists, ask the filter-choice question immediately. Do not invoke returned post-lead Task/Agent names before that question. Once the user answers, invoke Message Draft Builder from the same campaign/table basis. If the user chooses filters, also invoke Lead Fit Builder, move to Filter Rules, save rubrics, ask for filter approval, then keep the browser on Filter Leads and show `Filters saved + waiting for message approval` while the message recommendation is reviewed. If filters are skipped, move to Messages/message review.",
-            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
+            parentThreadRule: 'Named agents are optional acceleration, but message drafting is not optional. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. If it is absent, do not customer-surface install status; the main thread must execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), must follow Reference Asset Loading and load the required pre-draft reference pack before drafting, must include ai-tells.md because it is never optional, must return blocked/retry-needed if required assets cannot be loaded, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. On the filter path, keep the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; only then move to Filter Leads, show `Filters saved + waiting for message approval`, and wait there for message approval. Enrichment, filtering, Generate Message cells, sender setup, sequence attach, and launch wait for template approval on the Use Template path. On the skip path, move to Messages/message review and wait for message approval before enrichment or Settings. Do not render message review from checklist or shortcut instructions; message review requires a messageDraftRecommendation whose basis proves the generate-messages prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Draft Builder after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
         },
     };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.204",
+  "version": "0.1.205",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign-v2/references/ai-tells.md

@@ -47,12 +47,13 @@ recite profile facts. `"I noticed your..."` reads as scraped intel.
 **Allowed alternative:** Use a concise permissioned bridge:
 `"Hope this is relevant if X is still live."`, `"Saw you might be
 interested in X, so hope this is relevant."`, `"Saw you in a few
-conversations around X, so hope this is relevant."` for LinkedIn-post-sourced
-campaigns, or the self-aware
-`"saw you raise your hand for X, so figured this was (hopefully) worth
-sending"` or `"saw you raise your hand for X (creepy to reach out based
-on that, i know) - but this felt too on the nose to ignore"` shapes when the
-engagement source is the reason for the note.
+conversations around X, so hope this is relevant."`, or `"Found you in a
+thread about X, so may be off, but this seemed relevant."` for
+LinkedIn-post-sourced campaigns. Use the self-aware `"saw you raise your
+hand for X, so figured this was (hopefully) worth sending"` or `"saw you
+raise your hand for X (creepy to reach out based on that, i know) - but
+this felt too on the nose to ignore"` shapes only when the source was an
+explicit lead-magnet comment, reply, or opt-in.
 
 **Severity:** REJECT
 
@@ -280,10 +281,12 @@ reach-out.
 **Allowed alternative:** Use a concise topic-level bridge when the
 source is meaningful, then continue with apologetic uncertainty:
 `"Saw you in a few conversations about LinkedIn outreach, so may be
-off, but this seemed relevant."` or `"Saw you in a few conversations
-around LinkedIn outreach, so hope this is relevant."` If the source was
-only casual reading or the role/topic connection is weak, omit the
-personalization line and open from the buyer pain.
+off, but this seemed relevant."`, `"Saw you in a few conversations
+around LinkedIn outreach, so hope this is relevant."`, or `"Found you in
+a thread about LinkedIn outreach, so may be off, but this seemed
+relevant."` If the source was only casual reading or the role/topic
+connection is weak, omit the personalization line and open from the
+buyer pain.
 
 **Severity:** REJECT
 
@@ -305,6 +308,28 @@ does not narrate the source.
 
 **Severity:** REJECT
 
+## Tell #17 — Flattened "worth sending" source bridge
+
+**Pattern:** `"saw you raise your hand for [topic], so figured this was
+worth sending"` / `"figured this was worth sending"` without the
+parenthetical uncertainty `(hopefully)` or a `hope this is relevant`
+bridge.
+
+**Why it's an AI tell:** It sounds like a model trying to justify the
+outreach after reading a signal. The flat version makes the sender sound
+over-certain and self-focused: "I decided this was worth sending." Real
+operators usually soften the bridge or make it explicitly tentative.
+
+**Allowed alternative:** Use a permissioned, lower-certainty bridge:
+`"saw you raise your hand for [topic], so figured this was (hopefully)
+worth sending."` only for explicit lead-magnet comments, replies, or
+opt-ins. Otherwise use `"saw you might be interested in [topic], so hope
+this is relevant."`, `"saw you in a few conversations around [topic], so
+hope this is relevant."`, or `"found you in a thread about [topic], so
+may be off, but this seemed relevant."`
+
+**Severity:** REJECT
+
 ---
 
 ## How to add new tells

package/skills/create-campaign-v2/references/thomas-revision-filters.md

@@ -74,7 +74,7 @@ Revise or reject the sample when any of these happen.
 - **actions are implied, not stated** — e.g. "runs that chain as AI agents" when a clearer version would name the specific actions (verb + object, one per line)
 - **category-level opener used when a per-lead signal exists** — if `lead-sample.json` carries any per-lead signal (post, hire, visible tool, topic engagement), the opener must reference it. Category-level openers of shape `"Most [category] teams still do X by hand"` are only acceptable when zero per-lead signal is in the sample. When a category-level opener is used as fallback, Findings must flag it explicitly
 - **mind-reading from engagement signals** — a topic engagement, post, public activity, role, company, or hiring trigger does not prove buyer intent. Reject phrases like `"AI-GTM stack is clearly on your mind"`, `"you're clearly focused on..."`, `"obviously relevant"`, or `"already thinking about..."` unless that exact priority is explicitly present in `lead-sample.json`. Translate to low-certainty buyer context or omit the signal from copy.
-- **source-y signal narration** — reject `"saw you on..."`, `"saw you engaging with..."`, `"you commented on..."`, `"your LinkedIn activity..."`, `"you might not remember the thread..."`, `"found you through [source] and your role looked close..."`, or any line that makes the recipient feel watched unless the chosen archived motion is intentionally self-aware about the signal. For LinkedIn-post-sourced campaigns, a topic-level bridge is allowed when it explains why the note exists and stays apologetically uncertain: `"saw you in a few conversations about [topic], so may be off, but this seemed relevant."` or `"saw you in a few conversations around [topic], so hope this is relevant."` Translate the signal into natural buyer context or omit it.
+- **source-y signal narration** — reject `"saw you on..."`, `"saw you engaging with..."`, `"you commented on..."`, `"your LinkedIn activity..."`, `"you might not remember the thread..."`, `"found you through [source] and your role looked close..."`, or any line that makes the recipient feel watched unless the chosen archived motion is intentionally self-aware about the signal. For LinkedIn-post-sourced campaigns, a topic-level bridge is allowed when it explains why the note exists and stays apologetically uncertain: `"saw you in a few conversations about [topic], so may be off, but this seemed relevant."`, `"saw you in a few conversations around [topic], so hope this is relevant."`, or `"found you in a thread about [topic], so may be off, but this seemed relevant."` Reserve `"raise your hand"` language for explicit lead-magnet comments, replies, or opt-ins. Translate the signal into natural buyer context or omit it.
 - **assumptive title-fit opener** — reject `"Your [role] role at [company] looked close to this problem"` or `"looked close to this outbound campaign problem"`. This asserts fit from title/company. Keep the apologetic uncertainty instead: `"may be off, but if [workflow] is anywhere near your lane..."`.
 - **internal-metric flex** — reject compute time, token/cache details, model names, agent-counts, orchestration internals, or similar process metrics unless the brief proves the buyer cares about that exact detail. `~5 min of compute per message` is not buyer value by itself.
 - **action lines are parallel and harder to scan as paragraphs** — when 3
@@ -375,10 +375,14 @@ your lane, this might be useful.`
 this is relevant.`
 - `Hey {{first_name}}, saw you in a few conversations around [topic],
 so hope this is relevant.`
+- `Hey {{first_name}}, found you in a thread about [topic], so may be
+off, but this seemed relevant.`
 - `Hey {{first_name}}, saw you raise your hand for [topic], so figured
-this was (hopefully) worth sending.`
+this was (hopefully) worth sending.` Only for explicit lead-magnet
+comments, replies, or opt-ins.
 - `Hey {{first_name}}, saw you raise your hand for [topic] (creepy to
 reach out based on that, i know) - but this felt too on the nose to ignore.`
+Only for explicit lead-magnet comments, replies, or opt-ins.
 - `Hey {{first_name}}, quick one. My co-founder and I left [prior
 role] to build [X].`
 - `Hey {{first_name}}, reaching out because [one-line sender

package/skills/generate-messages/SKILL.md

@@ -133,7 +133,7 @@ hard failure and revise the output before returning it.
 
 Dry mode validates message quality before campaign mint.
 
-Read:
+Read these campaign inputs:
 
 - `~/.sellable/configs/core/about-me.md`
 - `~/.sellable/configs/core/my-company.md`
@@ -148,20 +148,57 @@ Read:
 - `lead-filter.md` when present. If it is absent because the caller launched
   post-lead workstreams in parallel, start the prep/candidate stages and then
   reconcile before final `message-validation.md`.
-- `mcp/sellable/skills/create-campaign/references/ai-native-tokens.md`
-- `mcp/sellable/skills/create-campaign/references/token-fill-examples.md`
-- `mcp/sellable/skills/create-campaign-v2/references/gold-standard-runtime-message-pack.md`
-- `mcp/sellable/skills/create-campaign-v2/references/validation-criteria.md`
-- `mcp/sellable/skills/create-campaign-v2/references/thomas-revision-filters.md`
-- `mcp/sellable/skills/create-campaign-v2/references/gold-standard-message-patterns.md`
-- `mcp/sellable/skills/create-campaign-v2/references/gold-standard-message-examples.md`
-- `mcp/sellable/skills/create-campaign-v2/references/gold-standard-message-validation-example.md`
+
+### Reference Asset Loading (do this before drafting)
+
+Do not draft from this prompt alone. The full `generate-messages` prompt is
+only the contract; the reference assets below are the evidence and examples
+that define the desired output. Before writing angle drafts, you MUST load the
+required pre-draft reference pack below with `mcp__sellable__get_subskill_asset`.
+This is a hard gate: if the four required pre-draft assets are not loaded,
+return `blocked` / `retry-needed` instead of drafting. Write a short
+`Reference Asset Loading` note naming each loaded asset and whether it was
+required pre-draft, final-pass, dry-mode-only, or token-rules-only. Do not
+bulk-load the conditional references unless their trigger applies or the caller
+explicitly asks for maximum context over speed.
+
+Use `mcp__sellable__get_subskill_asset` for packaged assets:
+
+| Group | Asset to load | Job |
+| --- | --- | --- |
+| Always load before drafting | `subskillName: "create-campaign-brief", assetPath: "references/phase75-active-runtime-message-pack.md"` | Active line-level gold pack: real approved examples, short-line rhythm, CTA blocks, lowercase/titlecase cues, and PS restraint. |
+| Always load before drafting | `subskillName: "create-campaign-v2", assetPath: "references/gold-standard-message-patterns.md"` | Strategy selector: event-led vs signal-led vs job-post-led vs proof-led fallback, proof inventory, candidate set, and Finalizer Pass. |
+| Always load before drafting | `subskillName: "create-campaign-v2", assetPath: "references/gold-standard-message-examples.md"` | Full archive quality bar: exact motion examples, hard rules, and transfer limits. Use it to choose 1 primary example, not to recolor copy. |
+| Always load before drafting (never optional) | `subskillName: "create-campaign-v2", assetPath: "references/ai-tells.md"` | Canonical anti-AI checklist: body self-intros, source citations, resume recaps, title-fit assumptions, em dashes, signoffs, weak proof brags, and flattened "worth sending" source bridges. |
+| Load before approval / final pass | `subskillName: "create-campaign-v2", assetPath: "references/thomas-revision-filters.md"` | Substance filters: earned-right, presumption, vague proof, read-as-1:1, founder-origin coherence, anti-talk-at, and AI-tell filter. |
+| Dry-mode artifact output only | `subskillName: "create-campaign-v2", assetPath: "references/gold-standard-message-validation-example.md"` | Fully worked example for proof inventory, candidate messages, Finalizer Pass, Selected Winner, findings, and recommendation. |
+| Dry-mode artifact output only | `subskillName: "create-campaign-v2", assetPath: "references/validation-criteria.md"` | Step-level acceptance criteria and dry-mode message validation expectations. |
+| Reusable token rules only | `subskillName: "create-campaign", assetPath: "references/ai-native-tokens.md"` | Token spec for rich judgment tokens, including required clauses and fallback behavior. |
+| Reusable token rules only | `subskillName: "create-campaign", assetPath: "references/token-fill-examples.md"` | Concrete good/bad token fills, interpolation guardrails, and product-noun substitution traps. |
+
+Default load order:
+
+1. Load the 4 **Always load before drafting** assets. Do not infer their
+   contents from this prompt; actually call `mcp__sellable__get_subskill_asset`
+   for each required asset.
+2. Draft and run the internal Finalizer Pass.
+3. Run the selected winner against `ai-tells.md`. This is never optional. If the
+   AI-tells catalog was not loaded or any `REJECT` tell matches, do not approve,
+   confirm, recommend, or show the template as ready; return `revise-message`.
+4. Load `thomas-revision-filters.md` before approval, `confirmed`, or template
+   recommendation.
+5. Load dry-mode artifact references only when writing `message-validation.md`.
+6. Load token-rule references only when creating reusable templates or Token
+   Fill Rules that need sentence-level personalization.
 
 ### Rich Personalization Contract
 
 `mcp/sellable/skills/create-campaign/references/ai-native-tokens.md` is the
 canonical spec for personalization that requires judgment. Load it before
 writing the Token Fill Rules or any reusable template notes.
+When token fill wording is material, use
+`mcp/sellable/skills/create-campaign/references/token-fill-examples.md` as the
+conditional good/bad fill reference.
 
 - Sentence-level personalization must use AI-native bracket tokens in the
   reusable template / token plan, not old-school field substitution. Field
@@ -328,6 +365,8 @@ artifact.**
    - `saw you on {{recent_signal}}`
    - `saw you around {{recent_signal}}`
    - `saw you engaging with {{recent_signal}}`
+   - `saw you raise your hand for {{signal_topic}}, so figured this was worth sending`
+   - `figured this was worth sending`
 
    Safer shapes:
 
@@ -339,8 +378,9 @@ artifact.**
    - `if {{workflow_signal}} is nowhere near your lane, ignore me`
    - `figured this might matter if {{workflow_signal}} is live at {{company}}`
    - `thought of {{company}} because {{observable_signal}} points at {{problem_context}}`
-   - `saw you raise your hand for {{signal_topic}}, so figured this was (hopefully) worth sending` only when the engagement signal is the actual source
-   - `saw you raise your hand for {{signal_topic}} (creepy to reach out based on that, i know) - but this felt too on the nose to ignore` only when the engagement signal is the actual source and the sender's voice can carry the cheekier aside
+   - `found you in a thread about {{signal_topic}}, so may be off, but this seemed relevant`
+   - `saw you raise your hand for {{signal_topic}}, so figured this was (hopefully) worth sending` only when the source was an explicit lead-magnet comment, reply, or opt-in. The parenthetical uncertainty is load-bearing; do not flatten it to `so figured this was worth sending`.
+   - `saw you raise your hand for {{signal_topic}} (creepy to reach out based on that, i know) - but this felt too on the nose to ignore` only when the source was an explicit lead-magnet comment, reply, or opt-in and the sender's voice can carry the cheekier aside
 
    For LinkedIn-post-sourced campaigns (commenters, reactors, lead magnet
    replies, or scraped conversations), it is acceptable to reference the
@@ -348,7 +388,10 @@ artifact.**
    activity-log-level: `saw you in a few conversations around
    {{signal_topic}}, so hope this is relevant` is acceptable; `saw you
    commented on {{post_context}}` and `your LinkedIn activity around...` are
-   not.
+   not. Reserve `raise your hand` phrasing for explicit lead-magnet comments,
+   replies, or opt-ins. For ordinary thread discovery, use `saw you in a few
+   conversations around {{signal_topic}}...` or `found you in a thread about
+   {{signal_topic}}...`.
 
    Keep the apologetic nature, but aim it at uncertainty, not surveillance.
    Good: `saw you in a few conversations about outbound, so may be off, but
@@ -1701,8 +1744,11 @@ led to it. Acceptable openers:
 - `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.`
 - `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.`
 - `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.`
-- `Hey {{first_name}}, saw you raise your hand for [topic], so figured this was (hopefully) worth sending.`
-- `Hey {{first_name}}, saw you raise your hand for [topic] (creepy to reach out based on that, i know) - but this felt too on the nose to ignore.`
+- `Hey {{first_name}}, found you in a thread about [topic], so may be off, but this seemed relevant.`
+- `Hey {{first_name}}, saw you raise your hand for [topic], so figured this was (hopefully) worth sending.` Only use this for explicit lead-magnet comments, replies, or opt-ins.
+- `Hey {{first_name}}, saw you raise your hand for [topic] (creepy to reach out based on that, i know) - but this felt too on the nose to ignore.` Only use this for explicit lead-magnet comments, replies, or opt-ins.
+- Do not use the flattened line `so figured this was worth sending`; either keep
+  `(hopefully)` or use `so hope this is relevant`.
 - `Hey {{first_name}}, pre-[product], we [did the operator-reality
 thing] for [X] years; [one-line consequence].`
 - `Hey {{first_name}}, building a thing for [segment] I think you'd
@@ -1953,10 +1999,11 @@ Rules:
   - `"Saw you might be interested in [topic], so hope this is relevant."`
   - `"Saw you in a few conversations around [topic], so hope this is relevant."`
   - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."`
+  - `"Found you in a thread about [topic], so may be off, but this seemed relevant."`
   - `"Thought of {{company}} because [observable signal] points at [problem]."`
   - `"Figured this might matter if [workflow] is live at {{company}}."`
-  - `"Saw you raise your hand for [topic], so figured this was (hopefully) worth sending."`
-  - `"Saw you raise your hand for [topic] (creepy to reach out based on that, i know) - but this felt too on the nose to ignore."`
+  - `"Saw you raise your hand for [topic], so figured this was (hopefully) worth sending."` Only for explicit lead-magnet comments, replies, or opt-ins.
+  - `"Saw you raise your hand for [topic] (creepy to reach out based on that, i know) - but this felt too on the nose to ignore."` Only for explicit lead-magnet comments, replies, or opt-ins.
 - blocked signal use:
   - `"AI-GTM stack is clearly on your mind."`
   - `"You're clearly focused on [area]."`
@@ -1965,7 +2012,9 @@ Rules:
   - `"Saw you on [topic]."`
   - `"Saw you around [topic]."`
   - `"Saw you engaging with [topic]."`
-- signal-led opener shape is a **special case**, not the default. Use it only when the archived motion truly depends on it and the line can stay natural. For LinkedIn-post-sourced campaigns, prefer `"saw you in a few conversations around [topic], so hope this is relevant"` when referencing the source makes the outreach feel less random. Avoid activity-log phrasing such as `"you commented on..."`, `"you reacted to..."`, or `"your LinkedIn activity..."` unless the approved motion is the deliberately self-aware raise-hand line.
+  - `"Saw you raise your hand for [topic], so figured this was worth sending."`
+  - `"Figured this was worth sending."`
+- signal-led opener shape is a **special case**, not the default. Use it only when the archived motion truly depends on it and the line can stay natural. For LinkedIn-post-sourced campaigns, prefer `"saw you in a few conversations around [topic], so hope this is relevant"` or `"found you in a thread about [topic], so may be off, but this seemed relevant"` when referencing the source makes the outreach feel less random. Avoid activity-log phrasing such as `"you commented on..."`, `"you reacted to..."`, or `"your LinkedIn activity..."` unless the approved motion is the deliberately self-aware raise-hand line for an explicit lead-magnet comment, reply, or opt-in.
 - tokenized engagement-source opener shape is BLOCKED by default:
   `{{first_name}}, saw you {{engagement_context}} on {{post_context}}` reads
   like surveillance unless the filled line is explicitly self-aware and
@@ -1973,11 +2022,12 @@ Rules:
 [topic] is part of the plan`, `saw you might be interested in [topic], so hope
 this is relevant`, `saw you in a few conversations around [topic], so hope this
 is relevant`, `saw you in a few conversations about [topic], so may be off,
-but this seemed relevant`, or one of the self-aware raise-hand shapes when the source is the
-actual reason for the note: `saw you raise your hand for [topic], so figured
-this was (hopefully) worth sending` or `saw you raise your hand for [topic]
-(creepy to reach out based on that, i know) - but this felt too on the nose to
-ignore`. Do not use the longer `you might not remember the thread...` shape;
+but this seemed relevant`, or `found you in a thread about [topic], so may be
+off, but this seemed relevant`. Use the self-aware raise-hand shapes only when
+the source was an explicit lead-magnet comment, reply, or opt-in: `saw you raise
+your hand for [topic], so figured this was (hopefully) worth sending` or `saw you
+raise your hand for [topic] (creepy to reach out based on that, i know) - but
+this felt too on the nose to ignore`. Do not use the longer `you might not remember the thread...` shape;
 if the concise source bridge still feels awkward, omit the engagement reference.
 - do not describe the sender/client in third person inside the outbound message.
   `p.s. Saju's angle is...`, `Christian's angle is...`, `[sender]'s approach
@@ -2570,7 +2620,7 @@ REPLY-style copy when the motion clearly matches a tighter approved pattern.
 Primary approved references are:
 
 - sellable.dev
-- Hey Digital
+- Hey Digital / HeyDigital
 - Galley
 - Clover
 - Persona