@sellable/mcp 0.1.212 → 0.1.213

package/README.md

@@ -334,12 +334,12 @@ with outcomes, and tracked people (LinkedIn profiles), all scoped by workspace.
 
 - Auth + active workspace: `~/.sellable/config.json` (or `SELLABLE_CONFIG_PATH`; old `$CODEX_HOME/sellable.json`, `~/.codex/sellable.json`, and `~/.claude/sellable.json` files remain compatibility fallbacks)
 - Engage memory (style guide + searches + tracked people): `sellable.engage.json` (or `SELLABLE_ENGAGE_MEMORY_PATH`)
-- Team-editable, project-local configs (recommended to edit in git):
-  - `./.sellable/configs/writing/styleguide.md`
-  - `./.sellable/configs/audience/icp-filters.md`
-  - `./.sellable/configs/proof/claims.md`
-  - `./.sellable/configs/discovery/influencers.md`
-  - `./.sellable/configs/discovery/post-filters.md`
+- Team-editable durable configs (home-level source of truth):
+  - `~/.sellable/configs/writing/styleguide.md`
+  - `~/.sellable/configs/audience/icp-filters.md`
+  - `~/.sellable/configs/proof/claims.md`
+  - `~/.sellable/configs/discovery/influencers.md`
+  - `~/.sellable/configs/discovery/post-filters.md`
 
 Files under `mcp/sellable/skills/**/core/*` are **package repo files**, not the intended user config surface.
 
@@ -352,7 +352,7 @@ Primary public entrypoint for the approval-gated campaign creation flow.
 ### interview
 
 Public identity/company memory interview. Builds durable core files under
-`./.sellable/configs/core/**`, raw archives under `./.sellable/interviews/**`,
+`~/.sellable/configs/core/**`, raw archives under `~/.sellable/interviews/**`,
 and reusable answer/proof/story/transcript/reference memory for downstream
 Sellable writing workflows.
 

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

@@ -60,9 +60,11 @@ required message reference cannot be loaded through the MCP asset loader, return
    `get_subskill_prompt({ subskillName: "generate-messages" })`
 
 3. Load every packaged reference asset required by that prompt's Reference Asset
-   Loading section with `get_subskill_asset`. If a required asset cannot load
-   through the MCP asset loader, return `blocked` or `retry-needed` instead of
-   drafting from memory.
+   Loading section with `get_subskill_asset`: load the required pre-draft reference pack before
+   drafting, load final-pass references before approval, and `ai-tells.md` is part of the required pack
+   and never optional. If a required asset cannot
+   load through the MCP asset loader, return `blocked` / `retry-needed`; do not draft from
+   memory or from the prompt alone.
 4. Build positioning in a compact working note: buyer, pain, product, mechanism,
    proof boundary, source-use rule, and CTA.
 5. Draft 3 distinct first-message options: signal-led, product/mechanism-led,
@@ -89,6 +91,7 @@ Return the following to the parent thread:
 
 - proposed first-message template using supported `{{...}}` tokens
 - token fill rules and fallbacks
+- `Reference Asset Loading` note naming which assets were used and why
 - one rendered good-fill sample for a plausible passing campaign-table row
 - message-draft runtime status: `ready`, `blocked`, `retry-needed`, or `stale`
 - approve-or-revise recommendation
@@ -178,16 +181,33 @@ own revision. The parent renders the revised template and waits for
 - Engagement-source personalization is a special case, not the default opener.
   Do not write `saw you {{engagement_context}} on {{post_context}}`, `saw you
 reacted to`, `saw you engaging with`, or equivalent source-citation copy as a
-  default hook. For LinkedIn-post-sourced campaigns, you may reference the
-  source when it explains why the note exists, but keep it topic-level, not
-  activity-log-level. Good: `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`, `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`.
+  default hook. Sender-owned post sources are different: if the source post was
+  authored by the sender/client and the row proves a reaction/comment, prefer a
+  light first-person acknowledgment such as `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 the row proves comment text, and do not infer
+  buyer intent from the reaction. Follow that acknowledgment with a soft
+  relevance bridge before any broad problem or product line. Good:
+  `figured this might be relevant if [channel/workflow] is becoming more of a
+  [GTM/pipeline/content] channel for [company/team]`. Bad: jumping directly
+  from `appreciate you showing some love...` to `a lot of B2B teams...` or
+  `most teams...`; that reads stitched together. Every line must make the next
+  line feel earned: source/post signal -> relevance bridge -> product/problem
+  -> next step. If adjacent lines could be swapped, deleted, or joined with
+  `anyway` without changing the meaning, rewrite the bridge or cut the orphan
+  line. For third-party LinkedIn-post-sourced
+  campaigns, keep the source topic-level. Good: `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`, `saw you might be
+interested in [topic], so hope this is relevant`, `hope this is relevant if
+[topic] is on your plate`, 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.
@@ -196,9 +216,9 @@ looked close...`. Otherwise omit the engagement signal and use role/company/prob
   topic looked close` are blocked. If the source is too weak, omit it.
 - Do not assert fit from title/company. `Your [role] role at [company] looked
   close to this problem` is blocked. Keep the apologetic uncertainty instead:
-  `may be off, but if [workflow] is anywhere near your lane...`.
+  `may be off, but if [workflow] is relevant to what you're working on...`.
 - Low-pressure relevance opt-outs are allowed when they do not defend the
-  source: `p.s. if this is nowhere near your outbound workflow, ignore me`.
+  source: `p.s. if this is not relevant to your outbound workflow, ignore me`.
 - Do not use `Caught` as opener language. It reads unnatural in LinkedIn
   outreach.
 - Do not describe the sender in third person inside the outbound message.

package/dist/engage-memory.js

@@ -8,11 +8,6 @@ function resolveConfigsDir() {
     if (process.env.SELLABLE_CONFIGS_DIR) {
         candidates.push(path.resolve(process.env.SELLABLE_CONFIGS_DIR));
     }
-    // Same resolution strategy as skills.ts
-    if (process.argv[1]) {
-        candidates.push(path.resolve(path.dirname(process.argv[1]), "../../.sellable/configs"));
-    }
-    candidates.push(path.resolve(process.cwd(), ".sellable/configs"));
     candidates.push(path.resolve(os.homedir(), ".sellable/configs"));
     for (const candidate of candidates) {
         if (fs.existsSync(candidate)) {

package/dist/identity-memory.js

@@ -20,10 +20,6 @@ export function resolveIdentityConfigsDir() {
     if (process.env.SELLABLE_CONFIGS_DIR) {
         candidates.push(path.resolve(process.env.SELLABLE_CONFIGS_DIR));
     }
-    if (process.argv[1]) {
-        candidates.push(path.resolve(path.dirname(process.argv[1]), "../../.sellable/configs"));
-    }
-    candidates.push(path.resolve(process.cwd(), ".sellable/configs"));
     candidates.push(path.resolve(os.homedir(), ".sellable/configs"));
     for (const candidate of candidates) {
         if (fs.existsSync(candidate)) {

package/dist/tools/engage-memory.js

@@ -2,7 +2,7 @@ import { copySenderConfig, getEngageMemory, migrateFlatConfigs, recordProvenSear
 export const engageMemoryToolDefinitions = [
     {
         name: "get_engage_memory",
-        description: "Load backward-compatible engage memory from .sellable/configs/: style guide, proven search keywords, tracked people, plus optional core identity/company memory. All data lives in readable markdown files the user can also edit directly. When senderId is provided, reads compatibility overrides from senders/{senderId}/ with flat-path fallback.",
+        description: "Load backward-compatible engage memory from ~/.sellable/configs/: style guide, proven search keywords, tracked people, plus optional core identity/company memory. All data lives in readable markdown files the user can also edit directly. When senderId is provided, reads compatibility overrides from senders/{senderId}/ with flat-path fallback.",
         inputSchema: {
             type: "object",
             properties: {
@@ -17,7 +17,7 @@ export const engageMemoryToolDefinitions = [
     },
     {
         name: "set_engage_style_guide",
-        description: "Write the user's commenting style guide. When senderId is provided, writes to .sellable/configs/senders/{senderId}/styleguide-core.md. Otherwise writes to .sellable/configs/writing/styleguide-core.md.",
+        description: "Write the user's commenting style guide. When senderId is provided, writes to ~/.sellable/configs/senders/{senderId}/styleguide-core.md. Otherwise writes to ~/.sellable/configs/writing/styleguide-core.md.",
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/leads.js

@@ -1365,7 +1365,7 @@ export const leadToolDefinitions = [
                 },
                 limit: {
                     type: "number",
-                    description: "Max posts (default 25, max 50). Used for profile search.",
+                    description: "Max posts (default 25, max 50). Used for profile or company search.",
                 },
                 headlineICPCriteria: {
                     type: "array",
@@ -3177,7 +3177,9 @@ export async function selectPromisingPosts(input) {
     const { campaignOfferId, selections, headlineICPCriteria, selectionMode, mode, scrapePlanMode, targetEngagerCount, maxPostsToScrape, } = input;
     const effectiveMode = selectionMode ?? mode ?? "replace";
     const effectiveScrapePlanMode = scrapePlanMode ??
-        (targetEngagerCount || maxPostsToScrape ? "capacity-target" : "all-selected");
+        (targetEngagerCount || maxPostsToScrape
+            ? "capacity-target"
+            : "all-selected");
     if (selections.length > MAX_SIGNAL_DISCOVERY_POSTS) {
         return {
             success: false,
@@ -3249,7 +3251,9 @@ export async function selectPromisingPosts(input) {
         }
         const recommendation = buildSignalDiscoverySourceRecommendation({
             selectedPosts: Array.from(selectedByUrl.values()),
-            targetEngagerCount: effectiveScrapePlanMode === "capacity-target" ? targetEngagerCount : null,
+            targetEngagerCount: effectiveScrapePlanMode === "capacity-target"
+                ? targetEngagerCount
+                : null,
             maxPostsToScrape: effectiveScrapePlanMode === "capacity-target" ? maxPostsToScrape : null,
         });
         sourceRecommendation = recommendation.message;

package/dist/tools/prompts.js

@@ -328,7 +328,7 @@ export function getPostFindLeadsScoutRegistry() {
                 "basis.workflowTableId",
                 "basis.sampleRowIds",
             ],
-            promptRequired: 'Load current campaign brief/table state through scoped tools, then get_subskill_prompt({ subskillName: "generate-messages" }) for all chunks. Load every asset named in the generate-messages Reference Asset Loading pack through get_subskill_asset. Before returning, load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) and use it as the final internal message-validation gate. Do not use shell/local filesystem reads, repo paths, plugin-cache paths, or /Users paths for message references. If required prompts/assets cannot be loaded through MCP tools, return blocked/retry-needed instead of drafting from memory.',
+            promptRequired: 'Load current campaign brief/table state through scoped tools, then get_subskill_prompt({ subskillName: "generate-messages" }) for all chunks. Follow its Reference Asset Loading step and load the Reference Asset Loading pack: the required pre-draft reference pack plus every required final-pass asset through get_subskill_asset; ai-tells.md is required and never optional. Before returning, load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) and use it as the final internal message-validation gate. Do not use shell/local filesystem reads, repo paths, plugin-cache paths, or /Users paths for message references. If required prompts/assets cannot be loaded through MCP tools, return blocked/retry-needed instead of drafting from memory; fail closed instead of drafting from the prompt alone.',
             basisFields: [
                 "campaignId",
                 "workflowTableId",
@@ -340,6 +340,7 @@ export function getPostFindLeadsScoutRegistry() {
             messageDraftOutputFields: [
                 "templateRecommendation",
                 "tokenFillRules",
+                "referenceAssetLoading",
                 "renderedGoodSample",
                 "revisionNotes when user feedback triggered a revision",
                 "status",
@@ -356,7 +357,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 anything before that question. After the answer, launch only Message Drafting whenever Codex agent-launch policy is satisfied. If filters are chosen, the parent stays on Filter Rules and drafts/saves rubrics with MCP tools while Message Drafting runs in the background. If filters are skipped, move to Messages/message review after Message Drafting is ready. Treat YOLO/autonomous mode as campaign-scoped permission for this single post-import worker. If the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once before loading the long message prompt in the parent. If permission is granted and the named Message Drafting custom agent is unavailable, spawn a generic gpt-5.5 xhigh Message Drafting background agent with the same lean campaign/table basis.",
             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 any Task/Agent before that question. After the answer, invoke only Message Drafting. If filters are chosen, parent drafts/saves rubrics with MCP tools while Message Drafting runs, asks filter approval, then joins Message Drafting. If filters are skipped, invoke only Message Drafting and move to Messages/message review.",
-            parentThreadRule: 'The only normal background worker is Message Drafting; source work and filter work stay in the parent thread with MCP tools. After the filter-choice answer, launch post-find-leads-message-scout only. If filters are chosen, the parent thread remains the filter writer: keep the browser on Filter Rules, load the filter reference, draft/save rubrics through MCP tools, ask filter approval, then move to Filter Leads while waiting for Message Drafting if needed. Do not move into message review, queue cells, or call update_campaign_brief until saved filters are approved when filters are enabled and messageDraftRecommendation is ready. If filters are skipped, launch only Message Drafting. In Codex, YOLO/autonomous mode counts as campaign-scoped permission for this single post-import worker; if the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once for permission before loading the long message prompt in the parent. If Message Drafting is allowed but the named worker is unavailable, use a generic gpt-5.5 xhigh Message Drafting background agent. Do not silently fall back to parent-thread message drafting. The Message Drafting handoff must be lean: campaignId, workflowTableId, brief summary, source summary/source-use rule, and 3-5 sample workflow-table rows with rowId/name/title/company/signal; optional campaignName, selectedLeadListId, and filter choice are allowed. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the message spawn prompt. The message branch must load current campaign brief/context, provided sample rows, the full generate-messages prompt, every referenced asset through get_subskill_asset, and before returning get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) for the internal validation gate. Local markdown/json files are not normal-path inputs. Message reference assets must be loaded with get_subskill_asset from the installed MCP package; do not use shell/local filesystem reads, repo paths, plugin-cache paths, or /Users paths to satisfy message references. The filter-choice question is the first post-import user gate; do not load this registry or filter references before it. Message drafting starts after the filter-choice answer and must reject mismatched workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. User copy feedback, message QA, or rewrite requests before approve-message must be routed back to Message Drafting with the current recommendation, lean campaign/table basis, and latest user text; the parent must not rewrite or QA the template from memory and must not call update_campaign_brief before approve-message. The worker validates internally and returns only templateRecommendation, tokenFillRules, renderedGoodSample, status, approveOrReviseRecommendation, validationStatus, outputAt, outputHash, and blocked/retry detail. Do not render renderedFallbackSample, concerns, or a qaReceipt on the normal happy path. On the filter path, the parent thread keeps 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, assets, and validation prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting after filters/enrichment finish; show the initial draft by default and offer an enriched rewrite only with explicit user opt-in.',
+            parentThreadRule: 'The only normal background worker is Message Drafting; source work and filter work stay in the parent thread with MCP tools. After the filter-choice answer, launch post-find-leads-message-scout only. If filters are chosen, the parent thread remains the filter writer: keep the browser on Filter Rules, load the filter reference, draft/save rubrics through MCP tools, ask filter approval, then move to Filter Leads while waiting for Message Drafting if needed. Do not move into message review, queue cells, or call update_campaign_brief until saved filters are approved when filters are enabled and messageDraftRecommendation is ready. If filters are skipped, launch only Message Drafting. In Codex, YOLO/autonomous mode counts as campaign-scoped permission for this single post-import worker; if the user has not enabled YOLO and has not explicitly asked for background agents/subagents/parallel agents/delegation/message bg agent in this campaign, ask once for permission before loading the long message prompt in the parent. If Message Drafting is allowed but the named worker is unavailable, use a generic gpt-5.5 xhigh Message Drafting background agent. Do not silently fall back to parent-thread message drafting. The Message Drafting handoff must be lean: campaignId, workflowTableId, brief summary, source summary/source-use rule, and 3-5 sample workflow-table rows with rowId/name/title/company/signal; optional campaignName, selectedLeadListId, and filter choice are allowed. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the message spawn prompt. The message branch must load current campaign brief/context, provided sample rows, the full generate-messages prompt, follow Reference Asset Loading, load the required pre-draft reference pack before drafting, load every referenced asset through get_subskill_asset, include ai-tells.md because it is never optional, and before returning get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) for the internal validation gate. The branch must return blocked/retry-needed if required assets cannot be loaded. Local markdown/json files are not normal-path inputs. Message reference assets must be loaded with get_subskill_asset from the installed MCP package; do not use shell/local filesystem reads, repo paths, plugin-cache paths, or /Users paths to satisfy message references. The filter-choice question is the first post-import user gate; do not load this registry or filter references before it. Message drafting starts after the filter-choice answer and must reject mismatched workflowTableId/campaign/workspace input. Do not use any alternate or examples-only message prompt. User copy feedback, message QA, or rewrite requests before approve-message must be routed back to Message Drafting with the current recommendation, lean campaign/table basis, and latest user text; the parent must not rewrite or QA the template from memory and must not call update_campaign_brief before approve-message. The worker validates internally and returns only templateRecommendation, tokenFillRules, referenceAssetLoading, renderedGoodSample, status, approveOrReviseRecommendation, validationStatus, outputAt, outputHash, and blocked/retry detail. Do not render renderedFallbackSample, concerns, or a qaReceipt on the normal happy path. On the filter path, the parent thread keeps 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, assets, and validation prompt ran for the current campaign/table execution slice. Do not automatically rerun Message Drafting 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.212",
+  "version": "0.1.213",
   "type": "module",
   "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
   "main": "dist/index.js",

package/skills/create-campaign/context/learnings.md

@@ -4,7 +4,7 @@ This log captures what has worked in real campaigns.
 
 Entries should be short, specific, and based on observed outcomes.
 
-**Cross-skill learnings** that would help other skills (engage, create-post) should ALSO be written to `.sellable/insights/cross-skill.md` so the entire system learns.
+**Cross-skill learnings** that would help other skills (engage, create-post) should ALSO be written to `~/.sellable/insights/cross-skill.md` so the entire system learns.
 
 ## Log
 

package/skills/create-campaign/references/brief-template.md

@@ -41,8 +41,8 @@ Example: "In a 15-minute call, we will audit your top 10 accounts and show where
 - **Bridge to:** [How it connects to their pain]
 - **Avoid:** [Generic phrases to skip - "best-in-class", "industry-leading", etc.]
 - **Voice:** [Reference core memory / composed engage memory first. Use legacy writing memory only as fallback.]
-- **Outbound rules:** [Reference `.sellable/configs/writing/outbound.md` if loaded -- observation -> relevance -> ask]
-- **Proof boundaries:** [Reference `.sellable/configs/core/proof-ledger.md` and `.sellable/configs/core/wins-ledger.md` if loaded. Do not upgrade or invent claims.]
+- **Outbound rules:** [Reference `~/.sellable/configs/writing/outbound.md` if loaded -- observation -> relevance -> ask]
+- **Proof boundaries:** [Reference `~/.sellable/configs/core/proof-ledger.md` and `~/.sellable/configs/core/wins-ledger.md` if loaded. Do not upgrade or invent claims.]
 
 ## Do NOT Target
 

package/skills/create-campaign-brief/references/brief-template.md

@@ -15,7 +15,7 @@ assistant message directly from the `result.result` stream-json payload —
 it does not read a file off disk.
 
 If you find yourself emitting a TodoWrite step like "Write brief.md v1
-to disk" or "Save brief to .sellable/..." — DELETE that step and return
+to disk" or "Save brief to ~/.sellable/..." — DELETE that step and return
 the brief inline instead. The tools `Write`, `Edit`, and `Bash` are
 intentionally not in the Phase 83 harness allowlist; attempting them
 will cause a ToolSearch loop that deadlocks the turn.
@@ -37,7 +37,7 @@ offer is, why it should work, and what must be true before we launch. Do not
 prescribe message structure, opener order, or final copy here.]
 
 Draft path:
-`.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
+`~/.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
 
 ## Product
 

package/skills/create-campaign-brief/references/draft-lifecycle.md

@@ -2,7 +2,7 @@
 
 Phase 83 writes one Markdown file:
 
-`.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
+`~/.sellable/create-campaign-brief/drafts/{workspace-slug}/{campaign-slug}/brief.md`
 
 ## Rules
 

package/skills/create-campaign-brief/references/examples/briefs/gelee.md

@@ -58,7 +58,7 @@ _Personalization: References their previous exit or current venture by name + th
 
 Hi {{first_name}}, let me know if i'm off, but {{seems_like_you}}.
 
-saw you were active in some {{signal_topic}} conversations recently and figured this might be relevant.
+saw you in a few conversations around {{signal_topic}}, so hope this is relevant.
 
 we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
 
@@ -131,7 +131,7 @@ is this worth a look or should i send a short overview?
 
 Hi sarah, let me know if i'm off, but seems like you started building something new in the pharma space after the Benchling exit.
 
-saw you were active in some founder-led growth conversations recently and figured this might be relevant.
+saw you in a few conversations around founder-led growth, so hope this is relevant.
 
 we work with about 30 exited founders right now (yc, techstars, sequoia backed) handling their entire linkedin with ai + human review.
 

package/skills/create-campaign-brief/references/examples/briefs/superpower.md

@@ -35,70 +35,82 @@ Signal-based outreach using peer-to-peer tone. Positioning Superpower as early d
 
 **VARIANT 1 — Subject: jeff/{{first name}} intro**
 
-hey {{first name}}, saw you were active around some {{topic}} stuff recently and figured this might actually be relevant
+hey {{first name}},
 
-any chance you're exploring early detection or preventive health programs at {{company}}?
+saw you in a few conversations around {{topic}}, so hope this is relevant.
 
-we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
+if preventive health is anywhere near the benefits plan at {{company}}, Superpower may be worth a look.
 
-basically your team gets to see what's coming instead of just reacting to it
+it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
 
-can I send over some more info?
+basically your team gets to see what's coming instead of only reacting to it.
+
+should i send over the short version?
 
 **VARIANT 2 — Subject: jeff/{{first name}} intro**
 
-hey {{first name}}. saw you were active in some {{topic}} conversations recently and wanted to run something by you
+hey {{first name}},
+
+saw you in a few conversations around {{topic}}, so hope this is relevant.
 
 most annual physicals test 15 biomarkers max.
 
-there's over 100 that actually matter and the gap between those two numbers is where the expensive claims tend to sit
+Superpower looks at 100+ biomarkers and screens for 1,000+ conditions from one draw.
 
-teams like Lyft and Notion are already exploring this. one draw, 1,000+ conditions, $199 a person.
+teams like Lyft and Notion are already exploring this at $199 a person.
 
-if your claims costs have been going up and you're not sure where it's coming from... that gap may be a good place to start looking
+if preventive health is nowhere near your lane, ignore me.
 
-can I send over some more info?
+should i send over the short version?
 
 ## Examples
 
 **Example 1 (Variant 1 — self-insured health plans):**
 Subject: susana/prab intro
 
-hey susana, saw you were active around self-insured health plan content recently and figured this might actually be relevant
+hey susana,
+
+saw you in a few conversations around self-insured health plans, so hope this is relevant.
 
-any chance you're exploring preventive health programs at Quantum Health?
+if preventive health is anywhere near the benefits plan at Quantum Health, Superpower may be worth a look.
 
-we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
+it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
 
-basically your team gets to see what's coming instead of just reacting to it
+basically your team gets to see what's coming instead of only reacting to it.
 
-can I send over some more info?
+should i send over the short version?
 
 **Example 2 (Variant 2 — employee wellness programs):**
 Subject: lisa/prab intro
 
-hey lisa. saw you were active in some employee wellness programs conversations recently and wanted to run something by you
+hey lisa,
+
+saw you in a few conversations around employee wellness programs, so hope this is relevant.
 
 most annual physicals test 15 biomarkers max.
 
-there's over 100 that actually matter and the gap is driving the surprise expensive claims every year
+Superpower looks at 100+ biomarkers and screens for 1,000+ conditions from one draw.
+
+teams like Lyft and Notion are already exploring this at $199 a person.
 
-teams like Lyft and Notion are already exploring this. one test, 1,000+ conditions, $199 a person
+if preventive health is nowhere near your lane, ignore me.
 
-can I send over some more info?
+should i send over the short version?
 
 **Example 3 (Variant 1 — employee wellness programs):**
 Subject: princess/prab intro
 
-hey princess, saw you were active around employee wellness programs content recently and figured this might actually be relevant
+hey princess,
+
+saw you in a few conversations around employee wellness programs, so hope this is relevant.
 
-any chance you're exploring preventive health programs at Marriott?
+if preventive health is anywhere near the benefits plan at Marriott, Superpower may be worth a look.
 
-we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
+it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
 
-basically your team gets to see what's coming instead of just reacting to it
+basically your team gets to see what's coming instead of only reacting to it.
 
-can I send over some more info?
+should i send over the short version?
 
 ## Social Proof
 
@@ -112,7 +124,8 @@ Teams like Lyft and Notion are exploring Superpower's early detection platform.
 - **ICP filtering:** All prospects filtered against ICP criteria before entering send queue
 - **Positioning:** Early detection tool for claims prevention, not a wellness benefit
 - **Tone:** All lowercase, casual, peer-to-peer - building relationship before asking
-- **Two approved variants:** Testing different hooks (exploratory vs. problem-aware)
+- **Two approved variants:** Testing a low-certainty signal bridge vs. proof-led
+  benefits mechanism
 
 ### Rubric Markdown
 
@@ -212,8 +225,8 @@ Teams like Lyft and Notion are already using early detection screening. One bloo
 
 **Subject: Prab/{{first_name}} intro**
 
-Hey {{first_name}}, not sure if you've looked into this but felt it may be relevant to your work.
+Hey {{first_name}},
 
-have you ever looked into early detection or preventive health programs for {{company}}?
+hope this is relevant if preventive health is anywhere near the benefits plan at {{company}}.
 
-we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
+Superpower screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.

package/skills/create-campaign-brief/references/phase75-active-runtime-message-pack.md

@@ -14,7 +14,8 @@ Included as primary gold examples:
 - `Galley`
 - `Clover`
 - `Persona`
-- `Superpower`
+- `Superpower` — domain-language reference only; use the cleaned low-certainty
+  opener, not retired engagement-source phrasing
 
 Not included in runtime inspiration:
 
@@ -33,6 +34,9 @@ Not included in runtime inspiration:
 
 - Feed only endorsed examples into generation.
 - Keep bad lines only if they are explicitly labeled `BAD` and paired with a `BETTER` version.
+- Treat sellable.dev, Hey Digital, Persona, Galley, and Clover as the primary
+  line-level quality anchors. Superpower is useful for benefits/healthcare
+  mechanism language, but it must not outrank those examples on opener style.
 - Default to one approved message in the generated brief unless the ICP is genuinely broad.
 - A/B CTA is optional. Use it only when the second option is truly strong.
 - If there is a great low-friction proof asset or case study, that is often the best Option B.
@@ -213,22 +217,21 @@ Why included:
 
 - simple language in a hard domain
 - useful plain-language healthcare constraint example
-- why it works: it asks about the buyer's existing benefits priority, explains
-  the mechanism in plain language, and keeps the ask tiny instead of forcing a
-  call
+- why it works: it uses a low-certainty signal bridge, explains the mechanism
+  in plain language, and keeps the ask tiny instead of forcing a call
 
 ```md
 Hey {{first_name}},
 
-not sure if you've looked into this but felt it may be relevant to your work.
+saw you in a few conversations around {{topic}}, so hope this is relevant.
 
-have you ever looked into early detection or preventive health programs for {{company}}?
+if preventive health is anywhere near the benefits plan at {{company}}, Superpower may be worth a look.
 
-we screen for 1,000+ conditions from a single blood draw and surface risks before they ever become claims.
+it screens for 1,000+ conditions from a single blood draw and surfaces risks before they become claims.
 
-basically your team gets to see what's coming instead of just reacting to it
+basically your team gets to see what's coming instead of only reacting to it.
 
-can I send over some more info?
+should i send over the short version?
 ```
 
 Locked production variant from the same Superpower campaign:

package/skills/create-campaign-v2/SKILL.md

@@ -27,6 +27,10 @@ handoff read campaign state first: `campaignId`, `watchUrl`, `campaignBrief`,
 `leadScoringRubrics`, `approvedMessageTemplate`, `senderIds`,
 `sequenceTemplate`, and running state. Local draft files are debug-only.
 
+There is no normal approval-packet, commit-gate, or atomic-mint path in the
+active flow. Legacy packet/mint artifacts stay in
+`create-campaign-v2-validation` and rehearsal material only.
+
 ## Normal Flow
 
 1. Bootstrap and tell the user the active Sellable workspace.

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
 
@@ -277,13 +278,25 @@ creating relevance. The message sounds like a lead scraper explaining
 why it picked the recipient, then asking the recipient to forgive the
 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.
+**Allowed alternative:** If the source is the sender's own LinkedIn post and
+row data proves a reaction/comment, a light first-person acknowledgment can be
+natural: `"appreciate you showing some love on my post about LinkedIn
+outreach"` or `"thanks for showing support on my LinkedIn outreach post."`
+Do not name a comment unless comment text is present. Follow the acknowledgment
+with a soft relevance bridge before broad pain or product copy, for example:
+`"figured this might be relevant if LinkedIn is becoming more of a GTM channel
+for Acme."` The next line must then connect to that same channel/workflow,
+not pivot into a generic pain claim. If the sequence reads like
+`thanks for the post support` -> `anyway, most teams...`, it is an AI tell
+because the lines are adjacent but not connected. For third-party post
+sources, 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."`
+`"Found you in a thread about LinkedIn outreach, so may be off, but this seemed
+relevant."` is allowed only when it stays topic-level and does not explain
+sourcing mechanics. 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
 
@@ -298,13 +311,35 @@ claim the recipient did not make. The line tells the buyer about
 themselves and assumes the workflow belongs to them.
 
 **Allowed alternative:** Keep the apologetic uncertainty without
-asserting fit: `"May be off, but if outbound is anywhere near your
-lane, this might be useful."` A low-pressure PS such as `"p.s. if this
-is nowhere near your outbound workflow, ignore me"` is allowed when it
+asserting fit: `"May be off, but if outbound is relevant to what you're
+working on, this might be useful."` A low-pressure PS such as `"p.s. if this
+is not relevant to your outbound workflow, ignore me"` is allowed when it
 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/approval-gate-framing.md

@@ -413,7 +413,7 @@ queue, attach sequence, or start. If a draft shell exists, leave it paused/
 non-sendable for operator cleanup instead of silently deleting a workspace row.
 
 Draft effect: move the draft directory to
-`.sellable/create-campaign-v2/drafts/{workspace-slug}/.aborted/{campaign-slug}-{timestamp}/`.
+`~/.sellable/create-campaign-v2/drafts/{workspace-slug}/.aborted/{campaign-slug}-{timestamp}/`.
 Legacy no-shell runs touch no DB rows and create no `CampaignOffer`.
 No DB rows touched in legacy no-shell aborts; draft-shell aborts leave the
 non-sendable shell for operator cleanup.