@sellable/mcp 0.1.436 → 0.1.438

package/dist/tools/campaign-fill-routing.js

@@ -6,7 +6,7 @@ async function postCampaignFillRoute(body) {
 export const campaignFillRoutingToolDefinitions = [
     {
         name: "resolve_campaign_fill_route",
-        description: 'Audit-only resolver to call before interpreting plain "fill campaigns", "load everyone up", or similar fill requests. It decides whether the workspace has evergreen/horizon targets, currently active campaign-backed sequence targets, or no targets so the agent must ask what to create. It does not create, append, prepare, approve, schedule, launch, archive, delete, send, or call lower-level fill tools. Only call fill_campaign_horizon when this resolver returns route "evergreen_horizon" or the user explicitly requested evergreen/horizon and the returned target is eligible; otherwise route plain fill through regular campaign refill before any two-send-day horizon preparation. Exact target narrowing uses campaignId or tableId only; never fuzzy campaign names.',
+        description: 'Audit-only resolver to call before interpreting plain "fill campaigns", "load everyone up", or similar fill requests. It decides whether the workspace has evergreen/horizon targets, current dashboard-active campaign-backed sequence targets, start-eligible PAUSED targets, or no targets so the agent must ask what to create. It does not create, append, prepare, approve, schedule, launch, archive, delete, send, or call lower-level fill tools. Only call fill_campaign_horizon when this resolver returns route "evergreen_horizon" and the selected returned target is eligible; use start_campaign only for exact returned startEligible PAUSED targets after the refill workflow approval/reread packet proves starting is needed. Exact target narrowing uses campaignId or tableId only; never fuzzy campaign names.',
         inputSchema: {
             type: "object",
             properties: {

package/dist/tools/prompts.js

@@ -373,7 +373,7 @@ export function getPostFindLeadsScoutRegistry() {
             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. The filter-choice answer is the post-import user gate for this single worker; do not ask another question about starting it in step-wise or YOLO mode. The registry lookup is not a launch: after get_post_find_leads_scout_registry, immediately invoke Task/spawn_agent or the host background-agent mechanism before loading filter-leads.md, before saving rubrics, and before treating skip-filters as ready for message review. Both choices route through this kickoff; do not let filters_skipped jump straight from filter-choice to message-generation. 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 only after Message Drafting has started or is ready; update_campaign(currentStep=messages) is not proof of launch. If 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. When the background worker starts, persist workerDetails.messageDraftBuilder with statusSource "branch", status "branch-running", runId, startedAt, updatedAt, basisToken when known, and basis containing campaignId, selectedLeadListId, workflowTableId, filterChoice, and reviewBatchRowHash or reviewBatchRowIds; workerStatuses.messageDraftBuilder may be "running" as a simple badge only. Never put rich proof under workerStatuses and never use workerStatuses.messageDrafting. If no background-agent tool is callable, start the same full message branch inline before filter drafting or before skip-filter message review, record workerDetails.messageDraftBuilder with statusSource "parent-thread-fallback" and status "fallback-active", and require the same live context, prompt, assets, and validation gate before message review; do not wait until filters are saved and then call the registry.',
             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: 'Named agents are optional acceleration, but message drafting is not optional. The only normal background worker is Message Drafting. The filter-choice answer is the campaign-scoped go-ahead for this single post-import worker; do not ask another question to start it in step-wise or YOLO mode. If a named agent is unavailable, use a generic gpt-5.5 xhigh Message Drafting background agent. source work and filter work stay in the parent thread with MCP tools. If post-find-leads-message-scout is available, run it as the background Message Draft Builder after the filter-choice answer. The registry lookup is not a launch: get_post_find_leads_scout_registry only identifies the worker, and Message Drafting counts as started only after Task/spawn_agent or the host background-agent tool is invoked, or after the parent begins the same full message branch inline because no background-agent tool is callable. This launch must happen before loading filter-leads.md, save_rubrics, filter approval, or skip-filter message review; currentStep=messages is not proof of launch. If post-find-leads-message-scout is absent, do not customer-surface install status. Do not silently treat message drafting as started; the main thread must either launch the background worker or execute the same message branch from CampaignOffer state, selected source state, workflowTableId, and initial campaign-table execution slice rows. For a spawned worker, record workerDetails.messageDraftBuilder with statusSource branch / status branch-running, runId, startedAt, updatedAt, and basis containing campaignId, selectedLeadListId, workflowTableId, filterChoice, and reviewBatchRowHash or reviewBatchRowIds. workerStatuses.messageDraftBuilder is optional simple badge text only ("running", "ready", "blocked", "idle"); never put runId/statusSource/basis under workerStatuses and never use workerStatuses.messageDrafting. If no background-agent tool is callable, start that same full message branch inline before filter drafting or before skip-filter message review, record workerDetails.messageDraftBuilder with statusSource parent-thread-fallback / status fallback-active then ready, and require the same live context, prompt, assets, and validation gate before message review; do not report that as a background worker failure. If neither branch nor inline fallback can run, return blocked/retry-needed; do not wait until filters are saved and then call the registry. The Message Drafting handoff must be lean. Do not paste copied row counts, brief hashes, review-batch hashes, full reviewBatchRowIds, broad row data, or local debug artifacts into the spawn prompt. Local markdown/json files are not normal-path inputs. The filter-choice question is the first post-import user gate; do not load post-lead registries or filter references before it. Message drafting starts after the filter-choice answer, must load get_subskill_prompt({ subskillName: "generate-messages" }), and must load every required message asset named by generate-messages Mode 0 through get_subskill_asset before drafting. Reference Asset Loading means loading the required pre-draft reference pack before drafting; return blocked/retry-needed if required assets cannot be loaded; load ai-tells.md because it is never optional. The branch or parent-thread fallback loads the full generate-messages prompt and every referenced asset through get_subskill_asset. After generating/revising the candidate and before returning ready, must load get_subskill_prompt({ subskillName: "create-campaign-v2-validation" }) as the final internal validation gate, must read live campaign table state through scoped MCP/product tools, and must reject mismatched selectedLeadListId/workflowTableId/campaign/workspace input. Do not block when filters were chosen but leadScoringRubrics are not yet visible in the branch read; the parent owns save_rubrics and filter approval in parallel, so Message Drafting should return status ready with basisStatus usable_initial when campaign/list/table identity and the non-empty execution slice match. Do not use any alternate, local-artifact, 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, risk notes, or a qaReceipt on the normal happy path. On the filter path, save_rubrics keeps the browser on Filter Rules after save_rubrics so the user can approve the saved criteria; after saved-filter approval, move to Filter Leads with currentStep=apply-icp-rubric whether Message Drafting is ready or still running. 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 after Message Drafting has started or is ready 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, required message assets, and validation gate 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. Handoff and recommendation output are Markdown with labeled fields, not raw JSON.',
-            prepareMessagesRule: `Default create-campaign stays on the existing reviewBatchLimit:15 first campaign-table execution slice. For plain post-mint fill/load/refill requests, load get_subskill_prompt({ subskillName: "refill-sends-workflow" }), then call resolve_campaign_fill_route({ intent:"plain" }), list_senders, and get_campaign_refill_state for enough candidate campaigns to identify the campaign that most recently had scheduler-owned sends for the relevant sender set before any mutation. Route outcomes are route:"evergreen_horizon", route:"active_campaigns", and route:"ask_create"; stay in the same campaignOfferId/campaignId context after minting. Plain fill is not an alias for fill_campaign_horizon or campaign creation. fill_campaign_horizon is evergreen-only and is not the generic regular-campaign fill path. Campaign creation is allowed only after route:"ask_create" and explicit user selection; it is never the default response to plain fill. Treat "fill up/load sends" as capacity-fill preparation, and treat "refill senders", "fill senders", "max out senders", and "load everyone up" as sender-scoped capacity-fill preparation. For sender-scoped requests with no named senders, --yolo means all eligible healthy senders enrolled in active campaign-backed sequence campaigns in the active workspace; without --yolo, ask which eligible enrolled senders to refill before choosing campaigns or mutating. In non-yolo interactive Codex or Claude Code sessions, the sender/campaign/action approval packet must be asked through request_user_input/AskUserQuestion with exactly Accept and Decline; do not use plain chat approval. The approval question body must show workspace, sender scope, a campaign-by-campaign table, exact ids/caps/dates, side effects, forbidden actions, and stop condition before mutation. Default --yolo horizon is a two-send-day horizon: two sender-local send days, skipping no-send-hour days. For campaign-scoped fill/refill, select the best recent-send campaign and calculate the bounded gap from healthy sender daily capacity minus future scheduler-owned scheduled sends and ready-to-schedule rows, then prepare only that gap. For sender-scoped fill/refill, calculate the bounded gap per eligible sender across active enrolled campaigns, counting future scheduled and ready-to-schedule rows across those campaigns, then choose the best same-sender campaign to fill each sender gap: prefer recent/future scheduler-owned sends for that sender, then strongest recent result evidence, then source health. Do not stop after filling only one sender when the request was sender-scoped. Use the refill workflow to decide whether to enrich/prep more rows in that same recent-send/best-result campaign, add/import more rows to that same campaign/source path, use a different existing campaign only when the selected same-sender lane is blocked/exhausted/already loaded while the sender still has a gap, or ask what to create. Do not create warm-post-engager side campaigns. Surface sender-health blockers separately from prepared/approved/scheduled counts. User-facing refill decisions must be campaign-name-first and sender-name-first, with ids as proof/execution targets only. For already-running regular campaigns that need Signal Discovery source replenishment, use the guarded currentStep clear with clearCurrentStepIfMatches:"running", campaign-scoped provider prompt/search/select, and import_leads with the existing sourceLeadListId when a newly approved selected-post scrape would otherwise return reusedExistingSourceList. After confirm_lead_list copies rows into an existing table, avoid fixed maxRowsToCheck:100; if confirm_lead_list returns USER_ADDED_ROWS_LIMIT_EXCEEDED, create a bounded same-source split from selectedLeadListId with get_rows_minimal/load_csv_linkedin_leads, confirm that smaller source list into the same campaign, and operate on the reviewBatch first; inspect reviewBatch/table selectors or use adaptive/wider bounded prep so appended rows are included. Do not interpret checkedRows as enriched rows; it is only the table cursor. Prepared, approved, and ready_to_schedule rows are intermediate states; never call them scheduled unless a re-read proves scheduler-owned scheduled cells with non-null scheduledFor. Before source import, prep, approval, or selected paused campaign start, require exact visible approval or --yolo packet auto-accept and a fresh get_campaign_refill_state reread; stop if freshness.stateHash or exact ids changed. For "approve X messages", use approvalMode:approve only when explicitly requested. For "schedule X sends" or "fill sender sends", approve only when explicitly requested, then re-read campaign/table scheduled counts; if scheduler-owned scheduledFor cells are not present, report prepared/approved/ready - awaiting scheduler instead of success. start_campaign is allowed in refill only for exact selected PAUSED, dashboard-active, campaign-backed sequence targets named in the bounded packet, and the packet must state that starting can let the product scheduler schedule/send approved eligible sequence actions. Never start unrelated, archived, completed, draft, direct, or non-selected campaigns, never broad approve-all, and never use direct scheduler writes. campaignId is CampaignOffer.id. If the user asks to stop preparation, the target is wrong, or status shows the wrong campaign/table, use cancel_campaign_message_preparation only for the exact active job. Low-level selectors are diagnostics and recovery only for this lane.`,
+            prepareMessagesRule: `Default create-campaign stays on the existing reviewBatchLimit:15 first campaign-table execution slice. For plain post-mint fill/load/refill requests, load get_subskill_prompt({ subskillName: "refill-sends-workflow" }), then call resolve_campaign_fill_route({ intent:"plain" }), list_senders, and get_campaign_refill_state for enough candidate campaigns to identify the campaign that most recently had scheduler-owned sends for the relevant sender set before any mutation. Route outcomes are route:"evergreen_horizon", route:"active_campaigns", and route:"ask_create"; if a plain managed-waterfall route has archived/completed skipped slots or does not cover the named sender set, immediately refetch with resolve_campaign_fill_route({ intent:"active" }) and inspect current dashboard-active ACTIVE/PAUSED campaign-backed sequence campaigns before declaring a sender blocked; stay in the same campaignOfferId/campaignId context after minting. Plain fill is not an alias for fill_campaign_horizon or campaign creation. fill_campaign_horizon is evergreen-only and is not the generic regular-campaign fill path. Campaign creation is allowed only after route:"ask_create" and explicit user selection; it is never the default response to plain fill. Treat "fill up/load sends" as capacity-fill preparation, and treat "refill senders", "fill senders", "max out senders", and "load everyone up" as sender-scoped capacity-fill preparation. For sender-scoped requests with no named senders, --yolo means all eligible healthy senders enrolled in active campaign-backed sequence campaigns in the active workspace; without --yolo, ask which eligible enrolled senders to refill before choosing campaigns or mutating. In non-yolo interactive Codex or Claude Code sessions, the sender/campaign/action approval packet must be asked through request_user_input/AskUserQuestion with exactly Accept and Decline; do not use plain chat approval. The approval question body must show workspace, sender scope, a campaign-by-campaign table, exact ids/caps/dates, side effects, forbidden actions, and stop condition before mutation. Default --yolo horizon is a two-send-day horizon: two sender-local send days, skipping no-send-hour days. For campaign-scoped fill/refill, select the best recent-send campaign and calculate the bounded gap from healthy sender daily capacity minus future scheduler-owned scheduled sends and ready-to-schedule rows, then prepare only that gap. For sender-scoped fill/refill, calculate the bounded gap per eligible sender across active enrolled campaigns, counting future scheduled and ready-to-schedule rows across those campaigns, then choose the best same-sender campaign to fill each sender gap: prefer recent/future scheduler-owned sends for that sender, then strongest recent result evidence, then source health. Do not stop after filling only one sender when the request was sender-scoped. In --yolo, continue through every safe selected sender/campaign action covered by the rendered packet, reread after each terminal apply/prep/start result, and when no safe in-packet action remains return concrete continuation options with campaign names, exact ids, and which options require a new approval packet. Use the refill workflow to decide whether to enrich/prep more rows in that same recent-send/best-result campaign, add/import more rows to that same campaign/source path, use a different existing campaign only when the selected same-sender lane is blocked/exhausted/already loaded while the sender still has a gap, or ask what to create. Do not create warm-post-engager side campaigns. Surface sender-health blockers separately from prepared/approved/scheduled counts. User-facing refill decisions must be campaign-name-first and sender-name-first, with ids as proof/execution targets only. For already-running regular campaigns that need Signal Discovery source replenishment, use the guarded currentStep clear with clearCurrentStepIfMatches:"running", campaign-scoped provider prompt/search/select, and import_leads with the existing sourceLeadListId when a newly approved selected-post scrape would otherwise return reusedExistingSourceList. After confirm_lead_list copies rows into an existing table, avoid fixed maxRowsToCheck:100; if confirm_lead_list returns USER_ADDED_ROWS_LIMIT_EXCEEDED, create a bounded same-source split from selectedLeadListId with get_rows_minimal/load_csv_linkedin_leads, confirm that smaller source list into the same campaign, and operate on the reviewBatch first; inspect reviewBatch/table selectors or use adaptive/wider bounded prep so appended rows are included. Do not interpret checkedRows as enriched rows; it is only the table cursor. Prepared, approved, and ready_to_schedule rows are intermediate states; never call them scheduled unless a re-read proves scheduler-owned scheduled cells with non-null scheduledFor. Before source import, prep, approval, or selected paused campaign start, require exact visible approval or --yolo packet auto-accept and a fresh get_campaign_refill_state reread; stop if freshness.stateHash or exact ids changed. For "approve X messages", use approvalMode:approve only when explicitly requested. For "schedule X sends" or "fill sender sends", approve only when explicitly requested, then re-read campaign/table scheduled counts; if scheduler-owned scheduledFor cells are not present, report prepared/approved/ready - awaiting scheduler instead of success. start_campaign is allowed in refill only for exact selected PAUSED, dashboard-active, campaign-backed sequence targets named in the bounded packet, and the packet must state that starting can let the product scheduler schedule/send approved eligible sequence actions. Never start unrelated, archived, completed, draft, direct, or non-selected campaigns, never broad approve-all, and never use direct scheduler writes. campaignId is CampaignOffer.id. If the user asks to stop preparation, the target is wrong, or status shows the wrong campaign/table, use cancel_campaign_message_preparation only for the exact active job. Low-level selectors are diagnostics and recovery only for this lane.`,
         },
     };
 }

package/dist/tools/refill-sends.js

@@ -143,15 +143,18 @@ export function refillSendsCommand(input = {}) {
         firstOperationalSteps: [
             'Load get_subskill_prompt({ subskillName: "refill-sends-workflow" }) before any product operation.',
             `Resolve route with resolve_campaign_fill_route({ intent: "${intent}"${input.campaignId ? `, campaignId: "${input.campaignId}"` : ""}${input.tableId ? `, tableId: "${input.tableId}"` : ""} }).`,
+            'If the plain route shows stale managed waterfall evidence, archived/completed shared slots, or targets that do not cover the selected sender set, immediately call resolve_campaign_fill_route({ intent: "active" }) and inspect current dashboard-active ACTIVE/PAUSED campaign-backed sequence campaigns before declaring a sender blocked.',
             "Call list_senders and get_sender_routing, then resolve sender selectors against active enrolled campaign-backed sequence senders.",
             untilDate
                 ? `Use fill window untilDate="${untilDate}" as the inclusive sender-local through date; do not extend beyond that date without a new approval packet.`
                 : `Use the default fill window of ${horizonSendDays} sender-local send days.`,
             "Read get_campaign_refill_state for enough exact candidate campaigns to pick the best per-sender target by recent/future scheduler-owned sends, then recent result evidence, then source health.",
+            "Treat current dashboard-active PAUSED campaign-backed sequence campaigns as start-eligible candidates: read refill state before deciding whether to prep, approve, start, or skip.",
             "Fresh reread get_campaign_refill_state immediately before any import, prep, approval, or horizon-fill mutation.",
+            "In --yolo, continue through every safe selected sender/campaign action covered by the rendered packet; when no safe in-packet action remains, return concrete continuation options instead of silently stopping.",
         ],
         approvalContract: yolo
-            ? "Auto-accept only the rendered bounded refill packet after fresh reread. This may include start_campaign only for exact selected PAUSED campaign-backed sequence refill targets named in the packet. Stop if sender set, route, ids, caps, dates, blockers, or side-effect class drift."
+            ? "Auto-accept only the rendered bounded refill packet after fresh reread. Continue through every safe apply/prep/start action inside that packet, including start_campaign only for exact selected PAUSED campaign-backed sequence refill targets named in the packet. If no safe in-packet action remains, return concrete continuation options and stop. Stop immediately if sender set, route, ids, caps, dates, blockers, or side-effect class drift."
             : hasSenderSelectors
                 ? "Ask the final Accept/Decline structured approval question before mutation, including workspace, sender scope, campaign table, exact ids, caps/dates, side effects, forbidden actions, and stop condition."
                 : "Ask which eligible enrolled senders to refill first, then ask the final Accept/Decline structured approval question before mutation.",

package/package.json

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

@@ -44,8 +44,8 @@ reference and no self-aware reason the note might matter.
 them. Real founders do not interrogate the recipient's data feed or
 recite profile facts. `"I noticed your..."` reads as scraped intel.
 
-**Allowed alternative:** Use a concise permissioned bridge for non-evergreen
-weak-signal campaigns:
+**Allowed alternative:** Use a concise permissioned bridge for Shared Signal
+Discovery and non-evergreen weak-signal campaigns:
 `"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."`, or `"Found you in a
@@ -56,10 +56,10 @@ 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 and other shared
-evergreen lanes, `hope this is relevant`, `saw you in a few conversations`, and
-`found you in a thread` are blocked. Translate the source topic into a concrete
-buyer/problem bridge or omit the source line.
+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.
 
 **Severity:** REJECT
 
@@ -268,7 +268,8 @@ one observed signal to why the note may matter. For non-evergreen weak-signal
 campaigns that can be `"Hope this is relevant if market expansion is still on
 your plate."`, `"Saw you might be interested in Claude + GTM, so hope this is
 relevant."`, or `"Saw you in a few conversations around international growth,
-so hope this is relevant."` For shared evergreen lanes, use a concrete
+so hope this is relevant."` For Shared Signal Discovery, the topic-level
+conversation bridge is allowed when evidence-backed; otherwise use a concrete
 buyer/problem bridge instead of the source-thread opener.
 
 **Severity:** REJECT
@@ -341,12 +342,13 @@ 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."` only for non-evergreen weak-signal
-campaigns. For shared evergreen lanes, translate the source into a concrete
-buyer/problem bridge or omit it.
+opt-ins. Otherwise use `"saw you in a few conversations around [topic], so
+hope this is relevant."` for Shared Signal Discovery when topic-level and
+evidence-backed, or `"saw you might be interested in [topic], so hope this is
+relevant."` / `"found you in a thread about [topic], so may be off, but this
+seemed relevant."` only for non-evergreen weak-signal campaigns. For other
+shared evergreen lanes, translate the source into a concrete buyer/problem
+bridge or omit it.
 
 **Severity:** REJECT
 

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

@@ -203,7 +203,58 @@ Why it works:
 **Proof ranks used:** rank 1 (mechanism - 1,000+ conditions from one blood
 draw), rank 3 (risk before claims).
 
-Do not use the Superpower weak-signal hedge pattern for Shared Evergreen Signal Discovery. `might be interested`, `hope this is relevant`, `saw you in a few conversations`, and `found you in a thread` make the source provider visible and are blocked for shared evergreen lanes. Use the safe pattern below: translate the source topic into a concrete buyer/problem bridge.
+### Dotwork Shared Signal Discovery Gold Standard
+
+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 in a few conversations about {{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 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 `might be interested`; that assumes intent from weak evidence.
+- 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
 

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

@@ -199,20 +199,25 @@ 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" only for non-evergreen weak-signal campaigns
+- 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
 - 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:
 
-- Do not use `hope this is relevant`, `might be interested`, or `saw you in a
-  few conversations` as the opener.
+- `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.
+- Do not use `might be interested`; that assumes intent from weak evidence.
+- Do not use `found you in a thread`; that exposes sourcing mechanics.
 - Do not use `I'm building`, `I've mapped`, `my company`, or `my team`.
-- Turn the source topic into a buyer problem bridge, then write the product line
-  in team/company voice.
-- If the source topic cannot support a concrete bridge, omit the source line and
-  start from a role/company/problem observation.
+- 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.
 
 Avoid:
 
@@ -316,6 +321,8 @@ Avoid:
 
 Prefer:
 
+- concrete A + B + C plus-sign subjects for InMail, especially Shared Signal
+  Discovery, such as `initiatives + business outcomes + one live picture`
 - event or asset name
 - buyer-language workflow
 - concrete offer

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

@@ -74,7 +74,32 @@ 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 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."` Shared evergreen signal override: `hope this is relevant`, `saw you in a few conversations`, `found you in a thread`, and `might be interested` are blocked for Shared Signal Discovery evergreen lanes. 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 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 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:
+  topic-level `saw you in a few conversations... hope this is relevant` is
+  allowed for Shared Signal Discovery when evidence-backed; `might be
+  interested` remains blocked because it assumes intent, and `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.
 - **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..."`.
@@ -375,13 +400,13 @@ 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.` Non-evergreen weak-signal only.
+still on your plate.` Shared Signal Discovery or 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.` Non-evergreen weak-signal only.
+- `Hey {{first_name}}, saw you in a few conversations about [topic], so hope
+this is relevant.` Shared Signal Discovery or non-evergreen weak-signal only.
 - `Hey {{first_name}}, saw you in a few conversations around [topic],
-so hope this is relevant.` Non-evergreen weak-signal only.
+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
 off, but this seemed relevant.` Non-evergreen weak-signal only.
 - `Hey {{first_name}}, saw you raise your hand for [topic], so figured

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

@@ -1232,7 +1232,7 @@ 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 intent-assumptive/source-thread hedges such as "might be interested", "hope this is relevant", and "saw you in a few conversations"; Shared Signal Discovery is a source provider, not customer-facing message copy.
+     Short form: Shared lanes must reject intent-assumptive hedges such as "might be interested"; Shared Signal Discovery may use topic-level bridges like "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 internal workflow vocabulary.
      Short form: revise or rerun the packaged create-campaign/generate-messages path.
    - **Post Engagers** first-message style: short, casual, references the
@@ -1273,9 +1273,18 @@ 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.
-     Do not use intent-assumptive/source-thread hedges such as "might be
-     interested", "hope this is relevant", "found you in a thread", or "saw
-     you in a few conversations" in Shared Signal Discovery samples.
+     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",
@@ -1289,7 +1298,7 @@ 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: no "might be interested", "hope this is relevant", "found you in a thread", or "saw you in a few conversations"; translate source evidence into buyer context.
+     Short form: topic-level bridges, including "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; "might be interested" is not allowed.
      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",
@@ -1329,7 +1338,7 @@ 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 evergreen lanes.
+     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: 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

package/skills/generate-messages/SKILL.md

@@ -269,10 +269,14 @@ 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.
 
-- `might be interested`, `hope this is relevant`, and Shared Signal
-  Discovery bridges like `saw you in a few conversations around [topic]` are
-  blocked for shared evergreen lanes. Signal Discovery is a source provider,
-  not the customer-facing reason for the note.
+- For Shared Signal Discovery, low-certainty topic bridges are allowed when
+  evidence-backed: `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,
+  other engagement that is not proven, or that the buyer `might be interested`.
+- `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.
 - 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.
@@ -293,11 +297,12 @@ or a founder self-intro.
 - 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, not relevance
-hedges.
-Short form: shared evergreen copy cannot use `might be interested`.
-Short form: Shared Signal Discovery must not use `saw you in a few
-conversations`; use the public business theme or buyer problem instead.
+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 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; do not
+use `saw you might be interested`.
 Short form: shared evergreen copy cannot use `I'm building`.
 Short form: write a concrete signal/problem bridge instead of a rejected relevance hedge.
 
@@ -319,11 +324,14 @@ 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 `might be interested`, `hope this is
-relevant`, `saw you in a few conversations`, or source-thread disclaimers.
-Use a concrete buyer/problem bridge instead. 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
+shared evergreen lanes, do not use source-thread disclaimers that expose
+mechanics. For Shared Signal Discovery, `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; do not use
+`saw you might be interested`. 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".
 FALLBACK: if unsupported, omit the entire line.]`
@@ -484,9 +492,9 @@ artifact.**
 
    Safer shapes:
 
-   - `hope this is relevant if {{signal_topic}} is part of the plan` for non-evergreen weak-signal campaigns only
+   - `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 non-evergreen weak-signal campaigns only
-   - `saw you in a few conversations around {{signal_topic}}, so hope this is relevant` for 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
    - `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
@@ -548,23 +556,28 @@ artifact.**
    line-to-line chain is real.
    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 and the campaign is not a
-   shared evergreen lane. 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, translate the source topic into a concrete buyer/problem bridge or
-   omit the source line.
+   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.
 
    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 evergreen lanes, `hope this is
-   relevant`, `might be interested`, and `saw you in a few conversations` are
-   blocked. 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, 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.
 
    Block wordier source narration such as `you might not remember the thread,
    but I found you through a {{signal_topic}} discussion and your
@@ -1561,10 +1574,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 and
-  other shared evergreen lanes, `might be interested`, `hope this is relevant`,
-  and `saw you in a few conversations around...` are blocked; start from the
-  public business theme, row role/company context, or buyer problem instead.
+  or `if you've ever wanted...`. Exception: for Shared Signal Discovery,
+  topic-backed `hope this is relevant` and `saw you in a few conversations
+  around...` are allowed when topic-level and evidence-backed; do not use `saw
+  you might be interested`. Other shared evergreen lanes should start from the
+  public business theme, row role/company context, or buyer problem.
 - **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
@@ -1866,10 +1880,11 @@ about`, or `clearly relevant` are BLOCKED. Source-y phrases such as
   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 evergreen lanes, skip the `might be
-  interested` version and use `hope this is relevant` or `saw you in a few
-  conversations ... hope this is relevant` only when it stays topic-level and
-  avoids false engagement claims, or use the concrete bridge version. Longer
+  a similarly natural line. For Shared Signal Discovery, topic-backed `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; do
+  not use `saw you might be interested`. Other shared evergreen lanes should use
+  the concrete bridge version. Longer
   source-recap forms such as `you
   might not remember the thread,
   but I found you through a [topic] discussion...` are BLOCKED; they narrate
@@ -2016,9 +2031,9 @@ 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 non-evergreen weak-signal campaigns only.
-- `Hey {{first_name}}, saw you might be interested in [topic], so hope this is relevant.` Not for shared evergreen lanes.
-- `Hey {{first_name}}, saw you in a few conversations around [topic], so hope this is relevant.` For non-evergreen weak-signal campaigns only; never for Shared Signal Discovery evergreen lanes.
+- `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 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}}, 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.
@@ -2280,9 +2295,9 @@ Rules:
 - 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."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
-  - `"Saw you in a few conversations around [topic], so hope this is relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
-  - `"Saw you in a few conversations about [topic], so may be off, but this seemed relevant."` Non-evergreen weak-signal only; blocked for shared evergreen lanes.
+  - `"Saw you might be interested in [topic], so hope this is relevant."` 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.
   - `"Thought of {{company}} because [observable signal] points at [problem]."`
   - `"Figured this might matter if [workflow] is live at {{company}}."`
@@ -2298,11 +2313,13 @@ 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 non-evergreen LinkedIn-post-sourced campaigns, source bridges such as `"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 Evergreen Signal Discovery, do not use the `might be interested`,
-  `hope this is relevant`, `saw you in a few conversations`, or `found you in a
-  thread` weak signal-led opener shapes above. Translate the source into a
-  concrete problem bridge, e.g.
+- 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` and `saw you
+  in a few conversations about/around [topic], so hope this is relevant` are
+  allowed when evidence-backed and not engagement-claiming; do not use `might be
+  interested`. 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.
@@ -2314,9 +2331,10 @@ Rules:
 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 evergreen lanes, `might be
-interested`, `hope this is relevant`, `saw you in a few conversations`, and
-`found you in a thread` are blocked. Use a concrete signal/problem bridge. Use
+off, but this seemed relevant`. For Shared Signal Discovery, topic-backed `hope
+this is relevant` and `saw you in a few conversations ... hope this is relevant`
+are allowed when topic-level and evidence-backed; do not use `might be
+interested`. 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

package/skills/refill-sends/SKILL.md

@@ -108,6 +108,13 @@ step using campaign names first, and stop before mutation unless the user has
 explicitly approved the exact workspace, campaign/table/source ids, caps/dates,
 approval mode, expected side effects, and stop/rollback condition.
 
+If the plain route's managed waterfall targets are stale, for example skipped
+targets show archived/completed shared slots or the returned targets do not cover
+the named sender, immediately run the active route refetch before declaring a
+sender blocked. Current dashboard-active `PAUSED` campaign-backed sequence
+campaigns are start-eligible refill candidates; read refill state before deciding
+whether to prep, approve, start, or skip. Do not treat them as archived inventory.
+
 For interactive Codex or Claude Code sessions, that approval must use the
 host-native structured question gate, not plain chat:
 
@@ -142,6 +149,14 @@ direct scheduler writes, sender reassignment, or campaigns outside those
 selected for the eligible sender set. Stop and re-plan if the route, sender set,
 ids, caps, blockers, or side-effect class drift before mutation.
 
+In `--yolo`, continue as far as the rendered packet safely allows. After each
+apply/prep/start result, reread state, settle processing when needed, and move to
+the next selected sender or start-eligible same-packet campaign instead of
+stopping after the first partial result. If no in-packet safe action remains,
+return concrete continuation options with campaign names, exact ids, which option
+is already covered by the current packet, and which option needs a new approval
+packet.
+
 In `--yolo`, the default two-day fill horizon is two send days unless
 `--until`/`untilDate` is provided. If an until date is provided, compute bounded
 gaps through that sender-local date inclusive, skipping no-send days and never

package/skills/refill-sends-workflow/SKILL.md

@@ -60,8 +60,16 @@ campaign.
 
 1. Call `resolve_campaign_fill_route` first. Use `intent:"plain"` for generic
    fill/load language, `intent:"active"` only when the user explicitly narrowed
-   to active regular campaigns, and `intent:"evergreen"` only when the user
-   explicitly asked for evergreen or horizon work.
+   to active regular campaigns or when the plain route has stale managed
+   waterfall evidence, and `intent:"evergreen"` only when the user explicitly
+   asked for evergreen or horizon work. The resolver must refetch current
+   dashboard-active campaigns as well as managed waterfall state. If the plain
+   route returns managed waterfall targets but skipped targets include
+   archived/completed waterfall slots, or if the returned targets do not cover a
+   named sender, immediately call `resolve_campaign_fill_route({ intent:"active" })`
+   and inspect current dashboard-active `ACTIVE` and `PAUSED` campaign-backed
+   sequence campaigns before declaring a sender blocked.
+   Short form: stale waterfall bindings do not overrule current dashboard-active campaigns.
 2. Resolve sender context before choosing a target. Call `list_senders`; when a
    managed program is involved, also call `get_campaign_waterfall`, and call
    `get_sender_routing` when territory rules may constrain sender eligibility.
@@ -76,12 +84,18 @@ campaign.
    refill-state readbacks and report that inference.
    Short form: `--yolo refill senders` means all eligible enrolled senders; non-yolo asks which enrolled senders.
 3. Read `get_campaign_refill_state` for candidate campaigns from the resolver
-   result. For a broad `active_campaigns` route, inspect enough candidates to
-   identify the campaign or small campaign set that most recently had
-   scheduler-owned sends for the relevant sender set. Do not stop after the
+   result and from the required active-route refetch when managed waterfall
+   evidence looks stale. For a broad `active_campaigns` route, inspect enough
+   candidates to identify the campaign or small campaign set that most recently
+   had scheduler-owned sends for the relevant sender set. Do not stop after the
    first resolver target unless it is also the most recent sender-relevant send
-   lane.
+   lane. A current dashboard-active `PAUSED` campaign-backed sequence campaign is
+   a start-eligible refill candidate, not an archived blocker; read its refill
+   state first, then include a bounded `start_campaign` packet only when the
+   state proves healthy senders, sequence, source/list, ready/preparable rows,
+   and starting is needed for the product scheduler to schedule/send.
    Short form: Do not stop after the first resolver target unless recent-send evidence supports it.
+   Short form: `PAUSED` dashboard-active campaigns are start-eligible candidates, not skipped archived inventory.
    In `--yolo` sender-scoped mode, selecting every active campaign is still a
    scope error, but selecting one best refill campaign per eligible sender is
    expected. Pick the single highest-ranked recent-send or best-result campaign
@@ -103,7 +117,8 @@ campaign.
 Use the refill-state response as the current facts receipt:
 
 - campaign status/current step, workflow table id, table config type, and public
-  type;
+  type, including whether the route target is dashboard-active `PAUSED` and
+  start-eligible;
 - selected source list/provider identity, source id, target prospect gap,
   cursor/inventory state, dedupe/DNC/provider exclusions, good-prospect yield,
   scan/import caps, and proof;
@@ -134,6 +149,13 @@ was actually sending most recently for the relevant available senders", not
 "fill every eligible target sender from the best enrolled active campaign for
 that sender", not "fill only the first/best campaign globally".
 
+When managed waterfall bindings point at archived/completed campaigns but the
+dashboard has current unarchived `ACTIVE` or `PAUSED` campaigns for the same
+sender/shared lane, prefer the current dashboard-active campaign for target
+discovery. The stale waterfall slot remains diagnostic proof, not a reason to
+skip a visible paused shared campaign that can be started through a bounded
+packet.
+
 Default `--yolo` horizon is two send days when the user asks to fill, refill,
 load, or max sends without naming a different horizon. Send days are sender-local
 days with configured sending hours; do not treat weekends or other no-send-hour
@@ -311,6 +333,9 @@ Paused campaign start discipline:
 
 - `PAUSED`, dashboard-active campaign-backed sequence campaigns are existing
   refill targets, not archived inventory.
+- If the route or active-campaign refetch marks a target as start-eligible, read
+  `get_campaign_refill_state` for that campaign/table before deciding whether to
+  start, prep, or skip it.
 - If the selected refill target is `PAUSED` and has healthy senders, sequence,
   source/list, and ready/preparable rows or a bounded source/prep packet, the
   final packet may include `start_campaign` when starting is needed for the
@@ -366,7 +391,28 @@ same refill request, do not ask the `Accept` / `Decline` question. Instead:
 3. verify the route, workspace id, campaign id, table id, source/action ids,
    caps/dates, approval mode, blockers, and side-effect class still match the
    packet;
-4. execute only the exact packet.
+4. execute only the exact packet;
+5. after each terminal apply/prep/start result, reread state, settle processing
+   when needed, and continue with the next smallest safe action inside the same
+   bounded packet until every selected sender is loaded/awaiting scheduler,
+   scheduled, or blocked by evidence.
+
+In `--yolo`, do not stop after the first selected campaign if the request was
+sender-scoped and more selected senders or same-packet start-eligible campaigns
+remain. If the first candidate is duplicate-only, already loaded, awaiting
+scheduler, source-exhausted, or otherwise blocked, continue to the next
+same-sender candidate that was already in the rendered packet and still matches
+the fresh route/refill-state evidence. If no in-packet safe action remains, stop
+before mutation and return continuation options instead of guessing.
+
+Continuation options must be campaign-name-first and concrete. For each blocked
+sender/campaign, list the next viable options with exact ids and the approval
+boundary, for example: start an already selected start-eligible paused campaign,
+repair stale waterfall bindings, replenish the current source, expand Signal
+Discovery post selection, use the next same-sender campaign, or run evergreen
+setup/repair. Mark which options are covered by the current `--yolo` packet and
+which require a new approval packet.
+Short form: in `--yolo`, go as far as the packet safely allows, then give exact continuation options.
 
 `--yolo` authorizes `start_campaign` only for selected `PAUSED` refill targets
 named in the exact packet. It never authorizes starting unrelated, archived,
@@ -466,6 +512,9 @@ Report in campaign-name-first language:
   create;
 - source state, blockers, exact next primitive, approval required, and the
   freshness hash used.
+- for `--yolo`, how far the run continued automatically, which selected senders
+  are loaded/scheduled/awaiting scheduler, and the exact continuation options for
+  any sender/campaign that remains blocked.
 
 Keep ids visible but secondary: show them under "Exact target" or "Proof", not
 as the main decision text. Say explicitly whether a selected paused campaign was