@sellable/mcp 0.1.441 → 0.1.443

package/dist/tools/setup-evergreen-campaigns.js

@@ -23,7 +23,7 @@ export const setupEvergreenCampaignsToolDefinitions = [
                 handoffMode: {
                     type: "string",
                     enum: ["create_campaign_goals"],
-                    description: 'plan mode only. When set to "create_campaign_goals", returns concise per-lane `$sellable:create-campaign` goal prompts and required inputs for simplified worker handoffs without changing verification behavior.',
+                    description: 'plan mode only. When set to "create_campaign_goals", returns concise per-lane `$sellable:create-campaign` goal prompts and required inputs for simplified worker handoffs without changing verification behavior. The matching createCampaignGoals[].goalPrompt is the authoritative campaign task for the lane worker; lane packet fields are operational scope and receipt proof context only.',
                 },
                 yolo: {
                     type: "boolean",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sellable/mcp",
-  "version": "0.1.441",
+  "version": "0.1.443",
   "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

@@ -56,10 +56,12 @@ 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.
 
-Shared evergreen exception: for Shared Signal Discovery, `hope this is
-relevant` and topic-level `saw you in a few conversations about/around X, so
-hope this is relevant` are allowed when evidence-backed and not engagement-
-claiming. `Might be interested` remains blocked because it assumes intent.
+Shared lane handling: for Shared Signal Discovery, a high-level topic bridge is
+allowed and usually preferred when source evidence supports the topic:
+`"Saw you around conversations about X, so hope this is relevant."` Keep it at
+topic level and do not recap the source, reaction, comment, post, author, or
+scraper path. For Shared Cold Fallback, source/conversation language is still a
+tell; start from a cold buyer problem or row-supported observation instead.
 
 **Severity:** REJECT
 

package/skills/create-campaign-v2/references/gold-standard-message-examples.md

@@ -203,60 +203,9 @@ Why it works:
 **Proof ranks used:** rank 1 (mechanism - 1,000+ conditions from one blood
 draw), rank 3 (risk before claims).
 
-### Dotwork Shared Signal Discovery Gold Standard
+Use the Superpower weak-signal hedge pattern as a valid model for Shared Signal Discovery when the source topic is real, third-party, and high-level enough to mention without activity-log phrasing. Shared Cold Fallback must not use this source language.
 
-Use this as the gold standard when a shared Signal Discovery lane has real
-topic evidence, an InMail format, and enough founder/operator proof to make the
-note feel earned.
-
-```text
-Subject: initiatives + business outcomes + one live picture
-
-Hey {{first_name}},
-
-Saw you might be interested in {{signal_topic}}, so hope this is relevant.
-
-I helped build {{credible_prior_company}}, so I've seen firsthand where {{buyer_category}} tools fall short.
-
-{{product}} keeps {{buyer_object_1}}, {{buyer_object_2}}, and {{buyer_object_3}} connected in one live model.
-
-It also gives AI agents structured context to work from, instead of stale exports.
-
-Open to a quick look at how {{company}}'s operating model would map in?
-
-P.S. We're backed by {{proof_point}} as a modern alternative to {{competitor_set}}.
-```
-
-Why it works:
-
-- the subject follows the plus-sign A + B + C pattern: topic + outcome + concrete picture
-- the opener is topic-level and low-certainty without exposing scrape mechanics
-- the credibility line explains why the sender has earned the point of view
-- the product is specific, not three generic product-summary sentences
-- the CTA offers a concrete mapped view for the recipient's company
-- the PS uses proof to answer a category objection, not to brag
-
-Transfer limits:
-
-- Use `Saw you might be interested in [topic], so hope this is relevant` or
-  `Saw you in a few conversations about/around [topic], so hope this is
-  relevant` only for Shared Signal Discovery when the source evidence supports
-  the topic and the line does not claim a reaction, comment, sender-authored
-  post, or other unproven engagement.
-- Do not use `found you in a thread`; that exposes sourcing mechanics.
-- Do not use founder/operator proof unless the brief supports it and every
-  attached sender can credibly send the line.
-- For InMail, keep the body as one cohesive message and use a concrete
-  plus-sign subject like `initiatives + business outcomes + one live picture`.
-
-The Superpower weak-signal hedge can also work for Shared Evergreen Signal
-Discovery when the line is topic-level and evidence-backed. Prefer the Dotwork
-shape above when the brief supports an InMail subject, sender credibility,
-specific product mechanism, company-specific CTA, and PS proof. Use the safe
-pattern below when a concrete signal/problem bridge is stronger than a
-low-certainty source opener.
-
-### Shared Evergreen Signal Discovery Safe Pattern
+### Shared Evergreen Signal Discovery Topic Bridge Pattern
 
 Use when the campaign is a shared evergreen signal lane and the source signal is
 real but not sender-owned.
@@ -264,20 +213,22 @@ real but not sender-owned.
 ```text
 Hey {{first_name}},
 
-The AI-assisted GTM conversations keep coming back to one problem: turning good LinkedIn signal into review-ready pipeline without another outbound dashboard.
+saw you around conversations about agentic AI governance, so hope this is relevant.
+
+Traditional governance often treats AI like predictable software, which leaves a gap between strategy and real-time delivery.
 
-Sellable helps teams find signal-matched prospects, filter for fit, and generate reviewed LinkedIn copy from one workflow.
+Persona is a multi-tenant control plane for auditing agentic identities across complex environments.
 
-Curious if LinkedIn outbound is a channel you're trying to make more reliable this quarter?
+Open to a 15-minute walkthrough?
 ```
 
 Why it works:
 
-- no blocked low-confidence relevance hedge
+- low-confidence relevance is aimed at source/topic fit, not buyer intent
 - no `I'm building` or founder-only first person
 - no internal workflow vocabulary such as Codex, MCP, agent workflows, workflow
   table, lead source, or signal discovery
-- the signal becomes a buyer problem instead of an activity-log opener
+- the signal becomes a buyer problem without a generic LinkedIn-pipeline claim
 - safe for multiple senders attached to the same shared lane
 
 ## Conditional Examples

package/skills/create-campaign-v2/references/gold-standard-message-patterns.md

@@ -199,28 +199,24 @@ Shape:
 Prefer:
 
 - lowercase or casual casing when the motion supports it
-- an honest line like "hope this is relevant" or "so may be off, but this seemed relevant" for Shared Signal Discovery or non-evergreen weak-signal campaigns
+- an honest line like "hope this is relevant" or "so may be off, but this seemed relevant" for non-evergreen weak-signal campaigns; for Shared Signal Discovery, use the high-level topic bridge override below
 - a concrete CTA that names the useful conversation or asset
 - binary options only when the brief explicitly supports two real next steps
 - direct wording over polished marketing language
 
 Shared Evergreen Signal Discovery override:
 
-- `Saw you in a few conversations about/around [topic], so hope this is
-  relevant` is allowed when the source evidence supports the topic and the line
-  does not claim a reaction, comment, sender-authored post, or other unproven
-  engagement.
-- The Dotwork opener `Saw you might be interested in [topic], so hope this is
-  relevant` is also allowed for Shared Signal Discovery when the source
-  evidence supports the topic. Do not use bare `might be interested` as a
-  generic intent claim.
-- Do not use `found you in a thread`; that exposes sourcing mechanics.
+- Shared Signal Discovery may use `saw you around conversations about [topic],
+  so hope this is relevant` when source evidence supports a high-level topic.
+- Keep the topic bridge at business-theme level; do not recap the source,
+  reaction, comment, post, author, or scraper path.
+- Shared Cold Fallback must not use `hope this is relevant`, `might be
+  interested`, or `saw you in a few conversations` as the opener.
 - Do not use `I'm building`, `I've mapped`, `my company`, or `my team`.
-- Prefer the Dotwork shape when the message is InMail: a concrete A + B + C
-  subject, topic-level relevance opener, proof of earned sender perspective,
-  specific product mechanism, company-specific CTA, and optional PS proof.
-- If the source topic cannot support a low-certainty topic bridge, omit the
-  source line and start from a role/company/problem observation.
+- Turn the source topic into a buyer problem bridge only when it is more
+  specific and less presumptive than the topic bridge.
+- If the source topic cannot support a high-level bridge, omit the source line and
+  start from a role/company/problem observation.
 
 Avoid:
 

package/skills/create-campaign-v2/references/sellable-cleanup-rules.md

@@ -74,33 +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 sender-owned LinkedIn post sources, a light first-person
-  acknowledgment is allowed when row data proves a reaction/comment:
-  `"appreciate you showing some love on my post about [topic]"` or `"thanks for
-  showing support on my [topic] post"`. Do not name a comment unless comment
-  text is present. Follow the acknowledgment with a soft relevance bridge
-  before broad pain/product copy, e.g. `"figured this might be relevant if
-  LinkedIn is becoming more of a GTM channel for [company]"`. For Shared Signal
-  Discovery and non-evergreen third-party LinkedIn-post-sourced campaigns, a
-  topic-level bridge is allowed when it explains why the note exists and stays
-  apologetically uncertain: `"saw you might be interested in [topic], so hope
-  this is relevant."`, `"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 `"hope this is relevant if [topic] is
-  still on your plate."` Shared evergreen signal override: Dotwork-style `saw
-  you might be interested` can be used for Shared Signal Discovery when the
-  named Dotwork pattern applies, topic-level and evidence-backed; otherwise
-  prefer the conversation/topic bridge. `found you in a thread` remains blocked
-  because it exposes sourcing mechanics.
-  Shared Cold Fallback should use a concrete signal/problem
-  bridge or omit the source line. Reserve `"raise your hand"` language for
-  explicit lead-magnet comments, replies, or opt-ins. 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 sender-owned LinkedIn post sources, a light first-person acknowledgment is allowed when row data proves a reaction/comment: `"appreciate you showing some love on my post about [topic]"` or `"thanks for showing support on my [topic] post"`. Do not name a comment unless comment text is present. Follow the acknowledgment with a soft relevance bridge before broad pain/product copy, e.g. `"figured this might be relevant if LinkedIn is becoming more of a GTM channel for [company]"`. For Shared Signal Discovery, prefer a high-level topic bridge when source evidence supports the topic: `"saw you around conversations about [topic], so hope this is relevant."` For non-evergreen third-party 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."` The topic must be a business theme, not raw source mechanics or activity-log detail. Shared Cold Fallback must not use this source language. Reserve `"raise your hand"` language for explicit lead-magnet comments, replies, or opt-ins. Translate the signal into natural buyer context or omit it.
 - **sender-owned source rendered as third-party** — hard fail when the source post is sender-owned and the draft says `"found you in a thread"`, `"saw you in a thread"`, `"saw you in conversations"`, or `"saw you in a few conversations"` as if the post were third-party. For sender-owned sources, the copy must either use a light first-person acknowledgment plus a soft relevance bridge, or omit the source line. If multiple senders may send the campaign, or the final sender/source-owner match is ambiguous, do not assume a specific `my post` voice or name a specific sender; omit the sender-owned source line until row-level sender ownership is proven. Neutral low-certainty thread/source language is only for truly third-party sources.
 - **fake line-to-line continuity** — reject line stacks where the source acknowledgment, relevance bridge, product line, and CTA do not actually build on each other. Each line must make the next line feel earned. If two adjacent lines could be swapped, deleted, or joined with `"anyway"` without changing the meaning, the transition is fake. In sender-owned post campaigns, the chain should be: support on my post -> why this topic may matter for the company -> what the product/problem does about that same topic -> low-friction next step.
 - **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 relevant to what you're working on..."`.
@@ -401,11 +375,14 @@ who scraped me."
 - `Hey {{first_name}}, I'm building [X] — [what it does in one plain
 sentence].`
 - `Hey {{first_name}}, hope this is relevant if [buyer context] is
-still on your plate.` Shared Signal Discovery or non-evergreen weak-signal only.
+still on your plate.` Non-evergreen weak-signal only.
 - `Hey {{first_name}}, may be off, but if [workflow] is relevant to what
 you're working on, this might be useful.`
 - `Hey {{first_name}}, saw you might be interested in [topic], so hope
-this is relevant.` Dotwork Shared Signal Discovery or non-evergreen weak-signal only.
+this is relevant.` Non-evergreen weak-signal only.
+- `Hey {{first_name}}, saw you around conversations about [topic], so
+hope this is relevant.` Preferred for Shared Signal Discovery when the
+topic is high-level and source-supported.
 - `Hey {{first_name}}, saw you in a few conversations around [topic],
 so hope this is relevant.` Shared Signal Discovery or non-evergreen weak-signal only.
 - `Hey {{first_name}}, found you in a thread about [topic], so may be

package/skills/create-evergreen-campaigns/SKILL.md

@@ -62,13 +62,15 @@ long-form contract below:
    callable, return `blocked: missing_visible_or_durable_lane_worker_runtime`
    before mutation.
 4. Write one compact prompt file per selected lane using the matching
-   `createCampaignGoals[].goalPrompt`, plus only the receipt path and canonical
-   receipt requirement. Do not paste the full evergreen skill, lane packet,
-   receipt schema, repair history, or verifier checklist into the worker prompt.
-   The worker goal is simple: run `$sellable:create-campaign` normally for that
-   campaign goal, use the evergreen-selected provider/source only as internal
-   sourcing metadata, and write the receipt. The parent does not create campaign
-   shells.
+   `createCampaignGoals[].goalPrompt` as the authoritative campaign task, plus
+   only the lane packet, receipt path, side-effect caps, and canonical receipt
+   requirement. Paste the goal prompt verbatim; do not replace it with a
+   handcrafted `Goal:` paragraph. Do not paste the full evergreen skill, receipt
+   schema, repair history, verifier checklist, or lane-specific copy checklist
+   into the worker prompt. The worker goal is simple: run
+   `$sellable:create-campaign` normally for that campaign goal, use the
+   evergreen-selected provider/source only as internal sourcing metadata, and
+   write the receipt. The parent does not create campaign shells.
 5. Collect fresh durable receipts, verify with the original planRevision and
    selectedActionIds, then run the idempotency plan and show sample messages.
 
@@ -497,10 +499,17 @@ path/thread id, stop with `blocked: parent_mutated_before_worker_receipt` and
 do not continue setup in the parent.
 Short form: dispatch every selected lane worker before shell creation.
 Short form: do not call `setup_evergreen_campaigns` with `mode:"apply"` from the parent.
-Use a compact worker prompt: include lane packet JSON, original selectedActionIds,
-original planRevision, parent postEngagerSenderIds, parent sharedSenderIds,
-receiptArtifactPath, workspace id, sender ids, side-effect caps, and the
-instruction to load packaged prompts through MCP.
+Use a compact worker prompt: include the exact matching
+`createCampaignGoals[].goalPrompt`, lane packet JSON, original
+selectedActionIds, original planRevision, parent postEngagerSenderIds, parent
+sharedSenderIds, receiptArtifactPath, workspace id, sender ids, side-effect
+caps, and the instruction to load packaged prompts through MCP. The worker
+prompt must explicitly state the authority order:
+`createCampaignGoals[].goalPrompt` first, then loaded `$sellable:create-campaign`
+/ `create-campaign-v2` / `generate-messages` prompts and assets, then evergreen
+lane/receipt proof requirements. Evergreen packet fields and receipt rules are
+operational proof context only; they must not become campaign brief copy,
+message-writing instructions, or generated customer-facing text.
 The worker prompt must include the exact filter status rule:
 `filterDecisionReceipt.status:"applied"` only; never `completed`, `confirmed`,
 `done`, or any other alias.
@@ -542,7 +551,9 @@ worker with stdin redirected from that file:
 
 ```
 codex -a never -s danger-full-access exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - <<'WORKER_PROMPT'
-Use $sellable:create-evergreen-campaigns as the governing skill for this one lane worker.
+Use $sellable:create-campaign as the governing campaign workflow for this one lane worker.
+Use the evergreen plan/packet below only for lane scope, source metadata,
+postconditions, side-effect caps, and durable receipt proof.
 
 Workspace id: <workspaceId>
 Parent planRevision: <planRevision>
@@ -558,6 +569,24 @@ If your runtime exposes a goal tool, create or maintain this exact goal:
 complete action <actionId> only when <receiptArtifactPath> exists as valid JSON
 for this lane or when a blocked receipt has been written at that same path.
 
+Create-campaign goal prompt (authoritative; paste verbatim from the matching
+createCampaignGoals[].goalPrompt):
+<createCampaignGoalPrompt>
+
+Authority order:
+1. The create-campaign goal prompt above is the campaign task.
+2. Loaded `$sellable:create-campaign`, `create-campaign-v2`, and
+   `generate-messages` prompts/assets own the campaign brief and message
+   strategy.
+3. The evergreen lane packet and receipt rules below are operational scope and
+   proof requirements only.
+
+Do not paste evergreen lane keys, provider/source names, receipt terms, setup
+plan terminology, verifier fields, or workflow mechanics into the campaign
+brief or generated customer-facing messages. Do not add evergreen-authored
+message-writing rules to the brief; let the loaded create-campaign and
+generate-messages workflow do its job.
+
 Worker lane packet JSON:
 <lane packet JSON>
 
@@ -587,8 +616,9 @@ WORKER_PROMPT
 codex -a never -s danger-full-access exec --skip-git-repo-check -m <worker-model> -C <repo> -o <worker-final-file> - < <worker-prompt-file>
 ```
 
-If any placeholder cannot be filled from the current lane packet, do not inspect
-the filesystem or rerun inventory; stop with `blocked: worker_dispatch_stalled`.
+If any placeholder cannot be filled from the current plan, matching
+`createCampaignGoals[]` entry, or lane packet, do not inspect the filesystem or
+rerun inventory; stop with `blocked: worker_dispatch_stalled`.
 `multi_agent_v1.spawn_agent`, raw `spawn_agent`, or any opaque Task/subagent
 runtime that cannot expose a visible thread id or durable receipt artifact is
 not accepted as command-level UAT proof and must not be used for mutating
@@ -1276,7 +1306,8 @@ Message, and verify current-revision sample messages before final completion.
      Short form: Do not pass the warm template into Shared Signal Discovery or Shared Cold Fallback.
      Short form: Shared lanes must reject generic product-summary samples.
      Short form: Shared lanes must reject three nearly identical samples.
-     Short form: Shared lanes must reject unsupported intent-assumptive hedges; Shared Signal Discovery may use Dotwork-style topic bridges like "saw you might be interested in [topic], so hope this is relevant", "saw you in a few conversations about [topic], so hope this is relevant", or "hope this is relevant if [topic] is part of the plan" when the source evidence supports the topic and the line does not claim engagement or expose source mechanics.
+     Short form: Shared lanes must reject unsupported low-confidence relevance hedges.
+     Short form: Shared lane message quality is owned by the packaged generate-messages prompt and validation; evergreen does not author source-thread bridge phrasing.
      Short form: Shared lanes must reject internal workflow vocabulary.
      Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
@@ -1317,21 +1348,12 @@ Message, and verify current-revision sample messages before final completion.
      product summaries, or repeated structure are bad. If the first generated
      batch violates these rules, rerun, but record that as a repaired UAT path
      rather than the desired zero-shot path.
-     Use the Dotwork gold-standard shape for Shared Signal Discovery samples
-     when the row supports a topic-level weak signal: "saw you might be
-     interested in [topic], so hope this is relevant", "saw you in a few
-     conversations about [topic], so hope this is relevant", or "saw you in a
-     few conversations around [topic], so hope this is relevant". These bridges
-     are allowed only when source evidence supports the topic and the line does
-     not claim a reaction, comment, sender-authored post, or other engagement
-     that is not proven. Do not use "found you in a thread" or other raw
-     source/discovery mechanics.
-     Shared Signal Discovery InMail subjects should follow the Dotwork plus-sign
-     A + B + C pattern: concrete topic + buyer outcome + useful artifact/picture,
-     for example "initiatives + business outcomes + one live picture".
-     Translate source/tool terms into prospect-facing business language; do not
-     put internal workflow
-     vocabulary such as "Codex-style workflow", "MCP", "agent workflows",
+     Shared Signal Discovery samples may use a supported topic bridge such as
+     "saw you around conversations about [high-level topic], so hope this is
+     relevant" when the topic is grounded in source evidence and not
+     activity-log phrasing. Translate source/tool terms into prospect-facing
+     business language; do not put internal workflow vocabulary such as
+     "Codex-style workflow", "MCP", "agent workflows",
      "Claude Code", or "Claude-style agent workflows" in customer-facing
      message one. Also avoid generic product-process nouns such as "dashboard",
      "workflow", "source", "send-ready copy", "reviewed prospect lists",
@@ -1342,7 +1364,8 @@ Message, and verify current-revision sample messages before final completion.
      Short form: Shared Signal Discovery uses no self-intro such as "I'm building Sellable".
      Short form: Shared Signal Discovery uses no self-intro such as "We're building Sellable".
      Short form: Shared Signal Discovery uses no "I've put together".
-     Short form: topic-level bridges, including "saw you might be interested in [topic], so hope this is relevant", "saw you in a few conversations about/around [topic], so hope this is relevant", and "hope this is relevant if [topic] is part of the plan", are allowed for Shared Signal Discovery when evidence-backed and not engagement-claiming; do not use bare "might be interested" as a generic intent claim.
+     Short form: Shared Signal Discovery may use "saw you around conversations about [topic], so hope this is relevant" when source-supported.
+     Short form: topic-level bridge rules are owned by the packaged generate-messages prompt and validation, not by the evergreen wrapper.
      Short form: no internal workflow vocabulary such as "Codex-style workflow", "MCP", "agent workflows", "Claude Code", or "Claude-style agent workflows".
    - **Shared Cold Fallback** first-message style: cold, direct, and cohesive.
      It must not pretend there was engagement, must not say "saw you pop up",
@@ -1358,14 +1381,15 @@ Message, and verify current-revision sample messages before final completion.
      Sellable/Codex/Claude-Code feature summary
      across prospects. This is a single-message cold path unless the approved
      create-campaign message workflow proves a better delivery format.
-     Do not use source-thread hedges such as "hope this is relevant", "might be
-     interested", or "saw you in a few conversations" in Shared Cold Fallback.
-     Start from a concrete role, company, or buyer-problem observation instead.
-     Do not use a repeated
-     product-definition paragraph such as "Sellable is a GTM system" across
-     samples; every reviewed cold sample should be specific enough to the role,
-     company, or problem that the three sample messages do not share the same
-     body skeleton.
+     Do not open with "hope this is relevant" or a similar low-confidence
+     relevance hedge in Shared Cold Fallback. Do not use a repeated product-definition paragraph such
+     as "Sellable is a GTM system" across samples; every reviewed cold sample
+     should be specific enough to the role, company, or problem that the three
+     sample messages do not share the same body skeleton.
+     Do not use source-thread hedges such as "might be interested", "saw you
+     around conversations about...", or "saw you in a few conversations" in
+     Shared Cold Fallback. Start from a concrete role, company, or buyer-problem
+     observation instead.
      Do not use mechanical Sellable process language such as "campaign idea into
      prospects, filters, messages, and sequence setup", "sequence-prospects",
      "dashboard overhead", "campaign map", "send-ready copy", or "reviewed
@@ -1382,7 +1406,8 @@ Message, and verify current-revision sample messages before final completion.
      Short form: Shared Cold Fallback uses no "I've put together".
      Short form: Shared Cold Fallback uses no opt-out shrug such as "If this isn't relevant, ignore me".
      Short form: Shared Cold Fallback uses no product-stack dump.
-     Short form: no "hope this is relevant", "might be interested", or "saw you in a few conversations" in Shared Cold Fallback; Shared Signal Discovery has the topic-level conversation-bridge exception above.
+     Short form: Shared Cold Fallback uses no low-confidence relevance hedge such as "hope this is relevant".
+     Short form: no "hope this is relevant", "might be interested", "saw you around conversations about", or "saw you in a few conversations" in Shared Cold Fallback; Shared Signal Discovery has the topic-level conversation-bridge exception above.
      Short form: no repeated product-definition paragraph such as "Sellable is a GTM system".
     - Customer-visible evergreen lanes must enable ICP filtering before Message
       Drafting. This applies to Post Engagers, Shared Signal Discovery, and
@@ -1483,13 +1508,18 @@ Message, and verify current-revision sample messages before final completion.
       or a product-stack dump that repeats the same
       Sellable/Codex/Claude-Code feature summary across prospects. For all
       shared lanes, reject generic product-summary samples, repeated
-      near-identical samples, intent-assumptive hedges such as "might be
-      interested", source-context mismatches such as "saw you in a few
-      conversations" in Shared Cold Fallback, internal workflow vocabulary, any
-      sample with non-empty `issues`, and any preserved Post Engagers opener;
-      revise or rerun the packaged create-campaign/generate-messages path before
-      reporting completion. Do not approve or final-report samples
-      with `verdict:"passed"` and non-empty `issues`.
+      near-identical samples, unsupported low-confidence relevance hedges, internal
+      workflow vocabulary, any sample with non-empty `issues`, and any preserved
+      Post Engagers opener; revise or rerun the packaged
+      create-campaign/generate-messages path before reporting completion. Do not
+      approve or final-report samples with `verdict:"passed"` and non-empty
+      `issues`.
+      Shared Signal Discovery samples may use `"saw you around conversations
+      about [high-level topic], so hope this is relevant"` when the topic is
+      supported by source evidence and not activity-log phrasing. Shared Cold
+      Fallback samples must still reject source/conversation hedges such as
+      `"hope this is relevant"`, `"might be interested"`, or `"saw you in a few
+      conversations"`.
    - The first review batch exists and at least 3 review rows have generated
      messages from the approved brief. If fewer than 3 usable rows exist, report
      the actual count and why.

package/skills/generate-messages/SKILL.md

@@ -246,6 +246,12 @@ says `generate-messages` loaded or because generated cells exist. The samples
 must read like final create-campaign/generate-messages output.
 
 - Start from a concrete row-supported role/company/problem observation.
+- Do not turn a company category into a certainty claim about the buyer's
+  channel strategy. Reject lines shaped like `Building [product/category] for
+  [buyers] means LinkedIn attention maps to pipeline`, `because you sell to
+  enterprise, LinkedIn is obviously a pipeline lever`, or other inferred
+  inevitability claims unless the row explicitly states that fact. A company
+  category can inform targeting; it is not buyer-facing proof.
 - Ask one clear buyer problem question.
 - Keep the product line minimal and buyer-readable; do not turn the note into a
   product-stack dump.
@@ -269,15 +275,15 @@ must be safer than the legacy weak-signal examples. These lanes are reused by
 multiple senders, so the first line cannot sound like a scraped-activity excuse
 or a founder self-intro.
 
-- For Shared Signal Discovery, low-certainty topic bridges are allowed when
-  evidence-backed: `saw you might be interested in [topic], so hope this is
-  relevant`, `saw you in a few conversations about/around [topic], so hope this
-  is relevant`, and `hope this is relevant if [topic] is part of the plan`. The
-  line must not claim a reaction, comment, sender-authored post, or other
-  engagement that is not proven.
-- `found you in a thread` is blocked for Shared Signal Discovery because it
-  exposes source mechanics. Shared Cold Fallback should use concrete
-  role/company/problem context instead of source-thread phrasing.
+- Shared Signal Discovery may use a soft, high-level topic bridge when source
+  evidence supports the topic: `saw you around conversations about
+  {{signal_topic}}, so hope this is relevant`. Keep the topic broad and
+  business-relevant; do not recap the source, reaction, comment, post, author,
+  or scraper path.
+- Shared Cold Fallback must not use Signal Discovery source language such as
+  `saw you around conversations about...`, `saw you in a few conversations...`,
+  `might be interested`, or `hope this is relevant`. It is a true cold lane and
+  should start from a buyer problem or row-supported observation.
 - do not write first-person singular founder language such as `I'm building`,
   `I've mapped`, `my company`, or `my team` unless exactly one sender can
   credibly say it and the lane is not shared.
@@ -288,24 +294,18 @@ or a founder self-intro.
   `source`, `sequence`, `send-ready copy`, or `reviewed prospect list` as
   buyer-facing explanation in shared evergreen samples unless the buyer's own
   company/product category uses that exact word and the line still sounds human.
-- Write a concrete signal/problem bridge instead of a rejected relevance hedge.
-  Good shapes are `the AI-assisted GTM conversations keep coming back to [buyer
-  problem]`, `teams trying to turn LinkedIn signal into pipeline usually hit
-  [problem]`, or `when [observable business moment] is live, [buyer workflow]
-  gets harder to run consistently`.
-- If the row evidence is too weak to write a concrete bridge, omit the source
+- Use a concrete signal/problem bridge only when it is less presumptive than the
+  topic bridge. Do not force a generic `LinkedIn signal into pipeline` line just
+  because the lane is shared.
+- If the row evidence is too weak to name a high-level topic, omit the source
   line and start from a buyer problem, event, role, or company observation.
 - Shared evergreen lanes must pass this gate before `confirmed`, before saving a
   reusable template, and before any route-proof approval.
 
-Short form: shared evergreen copy must start from buyer context or an
-evidence-backed topic bridge, not assumed intent.
-Short form: Shared Signal Discovery may use `saw you might be interested in
-[topic], so hope this is relevant`, `saw you in a few conversations
-about/around [topic], so hope this is relevant`, or `hope this is relevant if
-[topic] is part of the plan` when it is topic-level and evidence-backed.
+Short form: Shared Signal Discovery can use `saw you around conversations about {{signal_topic}}, so hope this is relevant`.
+Short form: Shared Cold Fallback cannot use Signal Discovery source language.
 Short form: shared evergreen copy cannot use `I'm building`.
-Short form: write a concrete signal/problem bridge instead of a rejected relevance hedge.
+Short form: do not force generic LinkedIn-pipeline assumptions when a topic bridge is safer.
 
 ### Rich Personalization Contract
 
@@ -325,16 +325,15 @@ conditional good/bad fill reference.
   `[PERSONALIZATION_LINE — Intent: write one short sentence that anchors the
 note to why this might matter now. DO: connect one observable role/company/
 activity signal to the buyer problem or offer with a permissioned bridge. For
-shared evergreen lanes, do not use source-thread disclaimers that expose
-mechanics. For Shared Signal Discovery, `saw you might be interested in [topic],
-so hope this is relevant`, `saw you in a few conversations about/around [topic],
-so hope this is relevant`, and topic-backed `hope this is relevant` bridges are
-allowed when topic-level and evidence-backed. Use a concrete buyer/problem
-bridge when that is stronger. Low-certainty language like
-"so may be off, but this seemed relevant" can be considered only for
-non-evergreen weak-signal campaigns when the source is otherwise awkward. DON'T: recap their resume, list companies, compliment their
-background, name a product their company sells, use source-citation phrasing, or
-use generic nouns like "your work".
+  Shared Signal Discovery, prefer `saw you around conversations about [high-level
+  topic], so hope this is relevant` when source evidence supports the topic.
+  For Shared Cold Fallback, do not use source/conversation language; start from a
+  buyer problem or row-supported observation. Legacy low-certainty language like
+  "so may be off, but this seemed relevant" can be considered for non-evergreen
+  weak-signal campaigns when the source is otherwise awkward. DON'T: recap their
+  resume, list companies, compliment their
+  background, name a product their company sells, use source-citation phrasing,
+  or use generic nouns like "your work".
 FALLBACK: if unsupported, omit the entire line.]`
 - The rendered personalization line should usually be 6-14 words. If it needs
   two clauses, multiple companies, or abstract tags like `GTM`, `international
@@ -486,17 +485,19 @@ artifact.**
    - `your {{role}} role at {{company}} looked close to this problem`
    - `your {{role}} role at {{company}} looked close to this outbound campaign problem`
    - `saw you on {{recent_signal}}`
-   - `saw you around {{recent_signal}}`
+   - `saw you around {{recent_signal}}` when `recent_signal` is raw
+     post/source/activity text instead of a high-level topic
    - `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:
 
-   - `hope this is relevant if {{signal_topic}} is part of the plan` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
-   - `saw you might be interested in {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
-   - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery or non-evergreen weak-signal campaigns only
-   - `saw you in a few conversations about {{signal_topic}}, so may be off, but this seemed relevant` for non-evergreen weak-signal campaigns only
+   - `hope this is relevant if {{signal_topic}} is part of the plan` for non-evergreen weak-signal campaigns
+   - `saw you might be interested in {{signal_topic}}, so hope this is relevant` for non-evergreen weak-signal campaigns
+   - `saw you around conversations about {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery and other third-party weak-signal campaigns when the topic is high-level and supported by source evidence
+   - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant` for Shared Signal Discovery and other third-party weak-signal campaigns when the topic is high-level and supported by source evidence
+   - `saw you in a few conversations about {{signal_topic}}, so may be off, but this seemed relevant` for non-evergreen weak-signal campaigns
    - `appreciate you showing some love on my post about {{signal_topic}}` only when the sender/client authored the source post and the row proves a reaction or comment
    - `thanks for showing support on my {{signal_topic}} post` only when the sender/client authored the source post and the row proves a reaction or comment
    - `figured this might be relevant if {{channel_context}} is becoming more of a {{workflow_context}} for {{company_context}}` as the bridge after a sender-owned post acknowledgment
@@ -504,7 +505,7 @@ artifact.**
    - `if {{workflow_signal}} is not relevant to what you're working on, ignore me`
    - `figured this might matter if {{workflow_signal}} is live at {{company}}`
    - `thought of {{company}} because {{observable_signal}} points at {{problem_context}}`
-   - `found you in a thread about {{signal_topic}}, so may be off, but this seemed relevant`
+   - `found you in a thread about {{signal_topic}}, so may be off, but this seemed relevant` for non-evergreen weak-signal campaigns only
    - `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
 
@@ -558,27 +559,26 @@ artifact.**
    For third-party LinkedIn-post-sourced campaigns (commenters, reactors, lead
    magnet replies, or scraped conversations), it is acceptable to reference the
    conversation when it explains why the note exists. Keep it topic-level, not
-   activity-log-level. `saw you commented on {{post_context}}` and `your
-   LinkedIn activity around...` are not acceptable. Reserve `raise your hand`
-   phrasing for explicit lead-magnet comments, replies, or opt-ins. For ordinary
-   shared evergreen thread discovery, Shared Signal Discovery may use
-   `saw you might be interested in {{signal_topic}}, so hope this is relevant`
-   or `saw you in a few conversations about/around {{signal_topic}}, so hope this
-   is relevant` when evidence-backed.
-   Shared Cold Fallback should translate the source topic into a concrete
-   buyer/problem bridge or omit the source line.
+   activity-log-level: `saw you around conversations about {{signal_topic}}, so
+   hope this is relevant` is preferred for Shared Signal Discovery when the
+   topic is high-level and supported by source evidence. `saw you in a few
+   conversations around {{signal_topic}}, so hope this is relevant` is also
+   acceptable when it reads more natural. `saw you commented on
+   {{post_context}}` and `your LinkedIn activity around...` are not acceptable.
+   Reserve `raise your hand` phrasing for explicit lead-magnet comments,
+   replies, or opt-ins. For Shared Cold Fallback, omit the source line and start
+   from a buyer problem or row-supported cold observation.
 
    Keep the apologetic nature, but aim it at uncertainty, not surveillance.
    Good for non-evergreen weak-signal campaigns: `saw you in a few
    conversations about outbound, so may be off, but this seemed relevant`, `may
    be off, but if outbound is relevant to what you're working on...`, or `hope
-   this is relevant if...`. For Shared Signal Discovery, topic-backed `hope this
-   is relevant`, `saw you might be interested in...`, and `saw you in a few
-   conversations about/around...` are allowed when topic-level and
-   evidence-backed. For
-   Shared Cold Fallback, use a concrete signal/problem bridge. Bad: `your role
-   at {{company}} looked close...`, because it asserts fit from a title and
-   tells the buyer about themselves.
+   this is relevant if...`. For Shared Signal Discovery, prefer `saw you around
+   conversations about [high-level topic], so hope this is relevant` when the
+   source topic is supported. For Shared Cold Fallback, these source hedges are
+   blocked; use cold buyer-context copy instead. Bad:
+   `your role at {{company}} looked close...`, because it asserts fit from a
+   title and tells the buyer about themselves.
 
    Block wordier source narration such as `you might not remember the thread,
    but I found you through a {{signal_topic}} discussion and your
@@ -1575,11 +1575,11 @@ Before `confirmed`, run the selected winner against these gates:
   the lead sample. If desire is inferred, use tentative framing like
   `hope this is relevant if...`, `saw you might be interested in...`,
   `saw you in a few conversations around...`, `figured this might matter if...`,
-  or `if you've ever wanted...`. Exception: for Shared Signal Discovery,
-  topic-backed `hope this is relevant`, `saw you might be interested in...`, and
-  `saw you in a few conversations around...` are allowed when topic-level and
-  evidence-backed. Other shared evergreen lanes should start from the
-  public business theme, row role/company context, or buyer problem.
+  or `if you've ever wanted...`. For Shared Signal Discovery, the preferred
+  opener is a high-level topic bridge such as `saw you around conversations
+  about [topic], so hope this is relevant` when source evidence supports the
+  topic. For Shared Cold Fallback, do not use source/conversation language; use
+  a cold buyer-problem opener instead.
 - **Buyer-first opener:** after the greeting, the first substantive line
   should usually enter the buyer's world: a real signal, current-state
   pain, buyer-owned priority, or useful artifact. Sender-origin can come
@@ -1875,18 +1875,18 @@ infrastructure signal`, or `rails can match` unless that exact buyer
 about`, or `clearly relevant` are BLOCKED. Source-y phrases such as
   `saw you on...`, bare `saw you around...`, and `saw you engaging with...`
   are also blocked unless the archived winner explicitly depends on that
-  self-aware signal style. Translate the signal into low-certainty buyer
-  context instead: `hope this is relevant if [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`, `found you
-  in a few conversations about [topic], so may be off, but this seemed
-  relevant`, `figured this might matter if [workflow] is live at [company]`, or
-  a similarly natural line. For Shared Signal Discovery, topic-backed `hope this
-  is relevant`, `saw you might be interested ... hope this is relevant`, and
-  `saw you in a few conversations ... hope this is relevant` are allowed when
-  they stay topic-level and avoid false engagement claims. Other shared evergreen lanes should use
-  the concrete bridge version. Longer
-  source-recap forms such as `you
+  self-aware signal style. For non-evergreen weak-signal campaigns, translate
+  the signal into low-certainty buyer context instead: `hope this is relevant if
+  [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`, `found you in a few conversations about [topic], so may be
+  off, but this seemed relevant`, `figured this might matter if [workflow] is
+  live at [company]`, or a similarly natural line. For Shared Signal Discovery,
+  keep the source bridge at high-level topic only:
+  `saw you around conversations about [topic], so hope this is relevant`. For
+  Shared Cold Fallback, skip the `hope this is relevant` / `might be interested`
+  / `saw you in a few conversations` versions and use cold buyer-context copy.
+  Longer source-recap forms such as `you
   might not remember the thread,
   but I found you through a [topic] discussion...` are BLOCKED; they narrate
   the scrape path instead of creating buyer relevance.
@@ -2032,10 +2032,11 @@ matters to the buyer, why this might be relevant, or the operator-reality that
 led to it. Acceptable openers:
 
 - `Hey {{first_name}}, [one plain sentence about what we built].`
-- `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
-- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
-- `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.` For Shared Signal Discovery or non-evergreen weak-signal campaigns only.
-- `Hey {{first_name}}, found you in a thread about [topic], so may be off, but this seemed relevant.`
+- `Hey {{first_name}}, hope this is relevant if [buyer context] is still on your plate.` Non-evergreen weak-signal only.
+- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` Non-evergreen weak-signal only.
+- `Hey {{first_name}}, saw you around conversations about [topic], so hope this is relevant.` Preferred for Shared Signal Discovery when source evidence supports a high-level topic.
+- `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.` Allowed for Shared Signal Discovery when it stays high-level and not activity-log-like.
+- `Hey {{first_name}}, found you in a thread about [topic], so may be off, but this seemed relevant.` Non-evergreen weak-signal only.
 - `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
@@ -2295,11 +2296,12 @@ Rules:
 - if `lead-sample.json` carries **any** per-lead signal for this lead — a recent post, a recent hire, a visible tool in the headline, a topic engagement, a public initiative — the **message must reference it specifically**. Category-level copy is rejected.
 - default placement is **Block 3**, not Block 1. Keep Block 1 substance-first unless the archived motion clearly earns a signal-led opener without falling into source-citation / talk-at phrasing.
 - acceptable signal use by default:
-  - `"Hope this is relevant if [topic] is part of the plan."`
-  - `"Saw you might be interested in [topic], so hope this is relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
-  - `"Saw you in a few conversations around [topic], so hope this is relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
-  - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."` Shared Signal Discovery or non-evergreen weak-signal only.
-  - `"Found you in a thread about [topic], so may be off, but this seemed relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
+  - `"Hope this is relevant if [topic] is part of the plan."` Non-evergreen weak-signal only.
+  - `"Saw you might be interested in [topic], so hope this is relevant."` Non-evergreen weak-signal only.
+  - `"Saw you around conversations about [topic], so hope this is relevant."` Preferred for Shared Signal Discovery when source evidence supports a high-level topic.
+  - `"Saw you in a few conversations around [topic], so hope this is relevant."` Allowed for Shared Signal Discovery when it stays high-level and not activity-log-like.
+  - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."` Non-evergreen weak-signal only.
+  - `"Found you in a thread about [topic], so may be off, but this seemed relevant."` Non-evergreen weak-signal only.
   - `"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."` Only for explicit lead-magnet comments, replies, or opt-ins.
@@ -2314,32 +2316,26 @@ Rules:
   - `"Saw you engaging with [topic]."`
   - `"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 Shared Signal Discovery and non-evergreen LinkedIn-post-sourced campaigns, source bridges such as `"saw you in a few conversations around [topic], so hope this is relevant"` or `"saw you in a few conversations about [topic], so may be off, but this seemed relevant"` can be used 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.
-- For Shared Evergreen Signal Discovery, topic-backed weak signal-led openers
-  such as `hope this is relevant if [topic] is part of the plan`, `saw you
-  might be interested in [topic], so hope this is relevant`, and `saw you in a
-  few conversations about/around [topic], so hope this is relevant` are allowed
-  when evidence-backed and not engagement-claiming. Translate the source into a
-  concrete problem bridge when that is stronger, e.g.
-  `"The AI-assisted GTM conversations keep coming back to one problem: turning
-  good LinkedIn signal into review-ready pipeline without another dashboard."`
-  Then connect the product in buyer language.
+- 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 Shared Signal Discovery, prefer `"saw you around conversations about [topic], so hope this is relevant"` when source evidence supports a high-level topic. For non-evergreen LinkedIn-post-sourced campaigns, `"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"` can be used 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.
+- For Shared Signal Discovery, prefer the high-level topic bridge above when it
+  is supported by source evidence. Use a concrete problem bridge only when it is
+  more specific and less presumptive than the topic bridge.
 - 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
-  low-certainty. Prefer a concise bridge such as `hope this is relevant if
-[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 `found you in a thread about [topic], so may be
-off, but this seemed relevant`. For Shared Signal Discovery, topic-backed `hope
-this is relevant`, `saw you might be interested ... hope this is relevant`, and
-`saw you in a few conversations ... hope this is relevant` are allowed when
-topic-level and evidence-backed. Other shared evergreen lanes should use a concrete signal/problem bridge. 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
+  low-certainty. For Shared Signal Discovery, prefer `saw you around
+  conversations about [topic], so hope this is relevant`. For non-evergreen
+  weak-signal campaigns, use `hope this is relevant if [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 `found you in a thread about [topic], so may be off, but this
+  seemed relevant`. For Shared Cold Fallback, those weak signal bridges are
+  blocked; use cold buyer-context copy instead. 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.