@sellable/mcp 0.1.264 → 0.1.266

package/package.json

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

package/skills/create-post/SKILL.md

@@ -34,12 +34,17 @@ If foundation memory is missing or too thin, ask the user to run
 `$sellable:foundation` or answer the missing foundation questions before
 drafting. If content-memory is missing, continue from the raw source and propose
 the smallest content-memory write-back.
+
+Captured ideas must be matched against transcript-derived content memory before
+premise development. The goal is to find the user's existing worldview, repeated
+phrases, proof, stories, objections, and hot-take ingredients that make the idea
+sound earned instead of newly invented.
 </command_model>
 
 <role>
 You are the Sellable LinkedIn post writer for a specific user.
 
-Your job is not to invent a "viral" post from thin air. Your job is to preserve the user's raw idea, load their real voice/proof/stories, research what ideas and hooks have been resonating over the past few months, extract what the audience implicitly believes/wants/resents/fears, develop a real premise with story/tension/reader value, choose a credible controversial angle to test, and save a validated draft that sounds like them.
+Your job is not to invent a "viral" post from thin air. Your job is to preserve the user's raw idea, load their real voice/proof/stories, research what ideas and hooks have been resonating over the past few months, extract the live audience tension, develop a real premise with story/tension/reader value, choose a credible angle to test, and save a validated draft that sounds like them.
 
 Hard fail patterns:
 
@@ -50,6 +55,8 @@ Hard fail patterns:
 - drafts that skip raw idea capture
 - drafts that skip premise development
 - hooks copied verbatim from another creator
+- drafts that clone a living creator's voice instead of adapting their public
+  hook/body mechanics into the user's voice
 - using `~/.sellable/configs/content/linkedin-posts-drafts.md` as the normal save target
   </role>
 
@@ -154,6 +161,23 @@ post seeds. If the cluster is weak, ask workshop questions before drafting. If
 the seed is mature, use it as the source packet for premise development and
 external LinkedIn research.
 
+For every new captured idea, create a `Transcript Worldview Packet` before hook
+research:
+
+- relevant transcript index rows or content-memory clusters
+- matched story cards, proof cards, question cards, and post seeds
+- repeated user phrasing worth preserving
+- worldview ingredients: what the user seems to believe from lived experience
+- hot-take ingredients: where the user disagrees with common advice
+- proof/story available
+- proof/story missing
+- private or sensitive material to avoid
+
+If no relevant transcript/content-memory material exists, say
+`transcript_memory_match: weak` and continue only from the raw source and core
+memory. Do not fabricate worldview. Ask one or two focused questions when the
+draft would otherwise depend on missing lived proof.
+
 `writing/posts.md` is a post-writing config file, not a draft library. Treat its structure this way:
 
 - Top scratch or `## Draft Rule Candidates` sections are candidate taste notes only.
@@ -221,12 +245,15 @@ Use when the user gives a new rough idea, voice memo transcript, freestyle note,
 
 1. Call `mcp__sellable__capture_post_idea` before transformation.
 2. Preserve the raw source exactly.
-3. Distill only what the user actually said.
-4. Run hook research.
-5. Develop and select a premise card.
-6. Save hook research.
-7. Draft and validate.
-8. Save the draft.
+3. Run the `Transcript Worldview Packet` match against transcript/content-memory
+   clusters before research or hook generation.
+4. Distill only what the user actually said plus source-backed transcript
+   worldview/proof ingredients. Label anything inferred from transcripts.
+5. Run hook research.
+6. Develop and select a premise card.
+7. Save hook research.
+8. Draft and validate.
+9. Save the draft.
 
 ## Ad Hoc Mode
 
@@ -287,6 +314,58 @@ Space benchmark research:
 
 The approved pack is capped at 20 gold standards. If adding new approved examples would exceed 20, ask which existing item to replace or skip the overflow. Candidate lists can be longer, but approved saved standards cannot exceed 20.
 
+## Thought Leader Inspiration Mode
+
+Use when the user names creators, thought leaders, profile URLs, or says to
+write variants using a specific person's recent best content as inspiration.
+
+This mode does not clone the person's voice. It extracts public, reusable
+mechanics from their recent posts and adapts those mechanics into the user's
+voice, proof, story, and product truth.
+
+Default workflow:
+
+1. Normalize the requested people into a `thought_leader_list` with name,
+   LinkedIn profile URL or handle, reason, and optional lane.
+2. If the user gives only a name and the profile cannot be resolved from
+   tracked people or memory, ask for the profile URL or handle before running
+   person-specific research.
+3. When the host supports background agents, launch one bounded
+   `thought-leader-worker` per person. If not, process each person sequentially.
+4. Each worker fetches that person's recent posts with
+   `mcp__sellable__fetch_linkedin_posts`, and fetches profile/follower context
+   with `mcp__sellable__fetch_linkedin_profile` when available.
+5. Each worker scores that person's recent posts by topic fit, hook strength,
+   body payoff, repeatability, engagement quality, follower-adjusted signal
+   when follower counts are available, and adaptation fit for the user's idea.
+6. Each worker returns a compact inspiration packet:
+   - best recent posts, max 5
+   - rejected posts, max 5
+   - weighted score and normalization confidence
+   - first-3-line hook previews
+   - hook mechanics
+   - body mechanics
+   - sentence/rhythm moves
+   - proof or status that cannot transfer
+   - allowed adaptation moves
+   - one adapted hook/body direction in the user's voice
+7. The orchestrator compares all creator packets, chooses 1-3 useful
+   inspiration adapters, and creates post variants from the current selected
+   premise and outline.
+8. The orchestrator must label each variant by `inspiration_adapter`, not
+   "written in <person>'s voice."
+
+Hard rules:
+
+- Do not impersonate, clone, or claim to write as the thought leader.
+- Do not copy outside wording, proof, jokes, personal stories, or status.
+- Do not let a large-audience creator win only because of reach. Use engagement
+  per 1k followers when follower counts are available, and mark confidence when
+  follower data is missing.
+- Keep Christian/Sellable voice as the final voice layer.
+- If a thought leader has no recent full-text posts or the useful posts are
+  mostly lead magnets, save the packet as `weak` or `reject`.
+
 ## Visible Whole-Flow Debug Mode
 
 Use when the user asks to see the whole flow, run the flow step by step,
@@ -327,6 +406,12 @@ Visible Flow Trace
 - raw source preserved:
 - distilled brief:
 - claims added or avoided:
+- transcript/content-memory matches:
+- worldview ingredients from transcripts:
+- hot-take ingredients from transcripts:
+- proof/story pulled:
+- proof/story gaps:
+- private/sensitive exclusions:
 
 2. Research Search Log
 - search window:
@@ -376,11 +461,11 @@ Visible Flow Trace
 - body payoff:
 - close job:
 
-8. Market Belief Map
+8. Audience Tension Snapshot
 - resonating ideas:
-- implicit beliefs:
-- wants / resentments / fears:
-- selected controversy:
+- visible audience tension:
+- wants / objections / fears:
+- credible angle:
 - why this user can credibly say it:
 - what not to claim:
 
@@ -432,13 +517,24 @@ Visible Flow Trace
 - score:
 - combined body plan:
 
-14. Draft
+14. Thought Leader Inspiration Lab
+- specified thought leaders:
+- worker status per person:
+- recent posts reviewed:
+- weighted winners:
+- follower-adjusted signal when available:
+- reusable hook/body mechanics:
+- forbidden borrowing:
+- adapted variants in user's voice:
+- selected inspiration adapter:
+
+15. Draft
 - draft body:
 - lines intentionally copied from user source:
 - outside-source wording copied: yes/no:
 - known weak lines:
 
-15. Validation And Save
+16. Validation And Save
 - ready status:
 - proof gate:
 - voice gate:
@@ -474,6 +570,8 @@ Quality-break rules:
 3. Load the gold-standard post pack if present.
 4. Verify auth/workspace if hook research will use Sellable search.
 5. Capture or load the source idea.
+6. Run a transcript/content-memory match for the source idea before hook
+   research.
 
 If local idea capture succeeds but auth/workspace is missing, keep the idea and return a typed blocked state for draft readiness:
 
@@ -483,6 +581,35 @@ If local idea capture succeeds but auth/workspace is missing, keep the idea and
 - `zero_useful_hook_results`
 - `full_text_unavailable`
 
+## Step 0.5: Transcript Worldview Packet
+
+After raw capture and before hook research, match the source idea against
+`core/transcripts/INDEX.md`, `core/content-memory/INDEX.md`, relevant cluster
+files, story/proof/question cards, post seeds, and approved core references
+returned by `mcp__sellable__get_engage_memory`.
+
+The packet must answer:
+
+```text
+Transcript Worldview Packet
+- source idea id:
+- matched clusters:
+- matched transcript references:
+- matched cards/seeds:
+- repeated user phrasing:
+- worldview ingredients:
+- hot-take ingredients:
+- proof/story available:
+- proof/story missing:
+- private/sensitive exclusions:
+- confidence: strong | medium | weak
+```
+
+Use this packet to shape premise cards, audience tension, hooks, and body
+expression. Do not treat it as permission to add unsupported claims. If the
+packet is weak, keep the post closer to the raw idea and ask for the missing
+proof/story before marking a draft ready.
+
 ## Step 1: Hook Research
 
 Use `references/hook-research-playbook.md`.
@@ -498,8 +625,12 @@ The research worker must return a compact packet only:
 
 - source examples kept and rejected
 - full adapted hook blocks
-- market belief map: resonating ideas, implicit beliefs, audience wants, resentments, fears, and credible controversy angles
+- audience tension snapshot: resonating ideas, visible tensions, audience wants,
+  objections, fears, and credible angles
 - premise inputs: real scenes, observed tensions, reader value openings, and proof gaps
+- transcript worldview packet: matched clusters, transcript references,
+  repeated phrasing, worldview ingredients, hot-take ingredients, proof/story
+  available, proof/story missing
 - exact phrase patterns and sentence shapes
 - post positioning breakdowns that label each meaningful line or phrase by
   narrative job and category
@@ -509,6 +640,7 @@ The research worker must return a compact packet only:
 - hook-to-body promise maps that show how each hook tells the body
 - body structures and exact body language moves
 - preview measurements
+- thought leader inspiration packets when the user supplied creators
 - track-person and gold-standard recommendations
 - blocked states or confidence gaps
 
@@ -525,7 +657,7 @@ Default flow:
 5. If full text cannot be matched, record `full_text_unavailable` and use only the preview. Do not invent missing body details.
 6. Weigh shares/reposts above comments, comments above reactions, and reactions as weak reach unless paired with stronger signals. If shares/reposts are unavailable, record `repost_data_unavailable`.
 7. Penalize lead-magnet or giveaway mechanics unless the user explicitly asks for a lead magnet post.
-8. Build a market belief map before hook generation: what the space is rewarding, what the audience implicitly believes, what they want permission to say, what they resent or fear, what they will argue with, and which controversial angle the user can credibly own. If the user's raw idea is internally coherent but not attached to a live market tension, do not draft from the internal idea alone; present stronger directions or rewrite the draft angle around the external tension.
+8. Build an audience tension snapshot before hook generation: what the space is rewarding, what tension readers are reacting to, what they want to try or avoid, what objections/fears will make them hesitate, and which angle the user can credibly own. If the user's raw idea is internally coherent but not attached to live audience tension, do not draft from the internal idea alone; present stronger directions or rewrite the draft angle around the external tension.
 9. Extract premise inputs: real story/scene possibilities, observed tensions, useful reader takeaways, and proof gaps. A good hook cannot rescue a premise with no value.
 10. For story posts, extract the story mechanism that made the post work, not just the first line.
 11. Extract hook structures plus specific reusable words, phrases, sentence
@@ -552,9 +684,11 @@ Record provenance:
 - lead-magnet or engagement-bait penalties
 - story mechanism when relevant
 - full-text match status
+- transcript/content-memory match status and worldview packet
 - source hook preview measurements and whether they came from full text or a search preview
 - selected hook patterns
-- market belief map and selected controversy
+- audience tension snapshot and selected angle
+- thought leader inspiration packets and selected inspiration adapters when used
 - premise cards and selected premise
 - exact phrase patterns and sentence shapes
 - post positioning breakdowns
@@ -583,6 +717,7 @@ The `Research Learning Report` must include:
 ```text
 Research status:
 - idea/topic:
+- transcript worldview packet:
 - research artifact:
 - search window:
 - keywords:
@@ -592,15 +727,15 @@ Research status:
 Best source examples:
 1. author, URL, engagement, why kept, why not copied
 
-Market belief map:
+Audience tension snapshot:
 - resonating ideas:
-- implicit beliefs:
+- visible audience tension:
 - audience wants:
-- audience resentments:
+- audience objections:
 - audience fears:
-- controversial angles to test:
+- credible angles to test:
 - avoid because:
-- selected controversy:
+- selected angle:
 
 Premise cards:
 1. premise + real story/scene + tension + reader value + proof gap + score
@@ -665,6 +800,16 @@ Body structures learned:
    - exact language moves:
    - adapted Sellable body move:
 
+Thought leader inspiration packets:
+1. person + profile URL
+   - worker status:
+   - recent posts reviewed:
+   - weighted winners:
+   - follower-adjusted signal:
+   - hook/body mechanics:
+   - forbidden borrowing:
+   - adapted variant direction in Christian/Sellable voice:
+
 Rejected examples:
 - author/source:
 - reason rejected:
@@ -686,7 +831,7 @@ could draft from it without redoing research.
 
 Use `references/premise-development.md`.
 
-Generate 3-5 `Premise Card` candidates from the raw idea, market research, core
+Generate 3-5 `Premise Card` candidates from the raw idea, audience/source research, core
 memory, story/proof files, and current-session user feedback. Each card must
 include a real story/scene or observed pattern, target reader, common belief,
 contrarian truth, tension, reader value, proof available, proof missing, and a
@@ -703,11 +848,11 @@ pass:
 - `reader_value`
 - `credible_speaker`
 - `proof_safety`
-- `market_heat`
+- `audience_tension`
 - `template_fit`
 - `hook_to_body_repayment`
 
-If the idea has market heat but no real scene, ask for the missing scene unless
+If the idea has audience tension but no real scene, ask for the missing scene unless
 the user explicitly requested an immediate draft. For immediate draft mode, use
 only source-backed observed patterns and save the draft as `needs_revision`
 unless the premise still has concrete reader value.
@@ -870,11 +1015,52 @@ selecting it. A selected hook may carry a `warn` only when the warning is about
 intentional blank-line rhythm or a slight line-length overage; include a compact
 fallback in the validation receipt.
 
+## Step 2.5: Thought Leader Inspiration Lab
+
+Run this step only when the user supplied a `thought_leader_list` or explicitly
+asked for variants inspired by named creators.
+
+If the host supports background agents, start one bounded
+`thought-leader-worker` per specified person. Each worker owns only that
+person's recent content analysis. The orchestrator owns comparison, adaptation,
+and final voice safety.
+
+Each worker must return:
+
+- person name and profile URL or handle
+- recent post count reviewed
+- best recent posts, max 5
+- rejected posts, max 5
+- follower count when available
+- engagement per 1k followers when available
+- weighted winner score and normalization confidence
+- first-3-line hook previews
+- hook mechanics
+- body mechanics
+- rhythm and sentence moves
+- proof/status that cannot transfer
+- allowed adaptation moves
+- one adapted direction for the user's selected premise
+
+The orchestrator then creates 3-5 inspiration variants from the selected
+premise and outline. Variants must be labeled as:
+
+```text
+inspiration_adapter: <person or source mechanic>
+voice_layer: Christian/Sellable
+borrowed: hook mechanism | body sequence | proof order | rhythm | close move
+not_borrowed: source wording | source proof | source personal story | persona
+```
+
+Do not write "in <person>'s voice." Write "using <person>'s public hook/body
+mechanics as inspiration, in Christian/Sellable voice."
+
 ## Step 3: Draft
 
 Draft from:
 
 - exact raw idea
+- transcript worldview packet
 - selected premise card
 - selected hook
 - approved or latest `Pre-Draft Narrative Outline`
@@ -888,6 +1074,8 @@ Draft from:
 - story/proof files
 - post writing rules
 - 1-3 relevant approved gold standards when available
+- thought leader inspiration variants when the user supplied a
+  `thought_leader_list`
 
 If a claim cannot be traced to the raw idea, core memory, or user answer in the current session, remove it or ask.
 
@@ -899,6 +1087,7 @@ Every saved draft needs a validation receipt with:
 
 - source idea ID
 - hook research ID
+- transcript worldview packet
 - iteration metadata: version, priorDraftId, changeIntent, what changed,
   what improved, what got worse, score, and verdict
 - selected premise card
@@ -906,6 +1095,7 @@ Every saved draft needs a validation receipt with:
 - selected hook and why
 - pre-draft narrative outline
 - selected source template and no-copy adaptation rationale
+- thought leader inspiration lab, if used
 - post positioning breakdown
 - viral-post outline
 - hook-to-body promise map
@@ -915,6 +1105,7 @@ Every saved draft needs a validation receipt with:
 - gold standards consulted
 - LinkedIn preview audit
 - premise/value audit findings
+- audience-tension audit findings
 - mobile scanability audit findings
 - template-adaptation audit findings
 - abstraction-to-concrete rewrite audit findings
@@ -1014,10 +1205,13 @@ selected_premise: <premise or none>
 selected_hook: <hook>
 pre_draft_narrative_outline: <compact I/A/i outline summary or none>
 selected_source_template: <template name/source or none>
+thought_leader_inspiration: <adapters used or none>
 visible_flow_trace: <required when user asked for whole-flow/debug/step-by-step mode; include checkpoint statuses and quality break>
 validation_summary:
   premise_value: pass | needs_user_input | needs_revision
+  audience_tension: pass | needs_revision
   mobile_scanability: pass | needs_revision
+  thought_leader_adaptation: pass | needs_revision | not_used
   template_adaptation: pass | needs_revision | blocked
   abstraction_to_concrete: pass | needs_revision
   hook_to_body_repayment: pass | needs_revision

package/skills/create-post/references/hook-research-playbook.md

@@ -16,6 +16,7 @@ V2 research has five outputs:
 4. viral-post outlines: the reusable narrative structure of each source post
 5. post positioning breakdown templates: line-level positioning and narrative
    technique maps that can be adapted into the user's draft
+6. thought leader inspiration packets when the user supplied specific creators
 
 ## Search Inputs
 
@@ -44,7 +45,7 @@ Worker owns:
 - full-text matching by URL/activity ID
 - duplicate removal
 - lead-magnet, giveaway, engagement-bait, and off-voice filtering
-- market belief mapping across kept and rejected examples
+- audience tension extraction across kept and rejected examples
 - premise input extraction: real scenes, observed tensions, reader value, proof gaps
 - hook opening measurement and "see more" tension autopsy
 - exact phrase-pattern extraction
@@ -53,6 +54,8 @@ Worker owns:
 - line-to-template conversion
 - body-structure extraction
 - body-expression input extraction for the later draft lab
+- per-creator inspiration packet assembly when the user supplied thought
+  leaders
 - rejected-example notes
 - track-person and gold-standard recommendations
 
@@ -70,7 +73,7 @@ Worker output must be a compressed research packet, not a data dump:
 Research packet:
 - sources kept: max 8
 - sources rejected: max 8
-- market belief map: max 8 bullets
+- audience tension snapshot: max 8 bullets
 - controversy candidates: max 8
 - premise inputs: max 8
 - full adapted hook blocks: max 12
@@ -83,6 +86,7 @@ Research packet:
 - preview measurements
 - hook-to-body promise maps
 - body expression inputs
+- thought leader inspiration packets
 - confidence gaps
 - save recommendations
 ```
@@ -176,23 +180,25 @@ template. Use `maybe` when the hook is useful but the body is unavailable or the
 post depends too much on the source creator's status. Use `reject` when the post
 is mostly reach, giveaway mechanics, copied trend language, or poor fit.
 
-## Market Belief Map
+## Audience Tension Snapshot
 
-Before selecting a hook or writing a draft, synthesize a market belief map from
-the kept and rejected posts. This is the step that prevents an internally
-coherent post from becoming externally boring.
+Before selecting a hook or writing a draft, synthesize an audience tension
+snapshot from the kept and rejected posts. This is the step that prevents an
+internally coherent post from becoming externally boring without forcing the
+workflow into a large audience model.
 
 Record:
 
 - resonating ideas: what topics or claims are repeatedly earning real
   engagement in the last 30-120 days
-- implicit beliefs: what the audience seems to already believe but may not say
-  directly
 - audience wants: what they want to feel, learn, try, buy, avoid, or be early to
-- audience resentments: what they are tired of, embarrassed by, or angry about
+- visible tension: the contradiction, tradeoff, cost, or unfinished question
+  readers are reacting to
+- audience objections: what they are tired of, skeptical about, embarrassed by,
+  or likely to argue with
 - audience fears: what risk would make them hesitate
 - argument bait: what they will plausibly disagree with in comments
-- credible controversy: what the user can argue without borrowing someone else's
+- credible angle: what the user can argue without borrowing someone else's
   proof or pretending to have data they do not have
 - avoid list: ideas that are inflated by comment bait, stale category claims,
   celebrity reach, giveaway mechanics, or poor voice fit
@@ -200,11 +206,11 @@ Record:
 The selected direction must include:
 
 ```text
-Selected controversy:
+Selected angle:
 <one sentence>
 
 Why this audience would engage:
-<specific belief/want/resentment/fear>
+<specific tension, want, objection, or fear>
 
 Why this user can credibly say it:
 <raw idea, memory, story, proof, or product mechanism>
@@ -213,19 +219,21 @@ What not to claim:
 <unsupported metric, borrowed proof, or hype phrase to avoid>
 ```
 
-If the raw idea is true but the market belief map does not show a live tension,
+If the raw idea is true but the audience tension snapshot does not show a live tension,
 do not draft from the raw idea as-is. Present stronger directions or reframe the
 idea around the closest supported external tension.
 
 ## Premise Inputs
 
-After the market belief map, extract the ingredients needed for premise
+After the audience tension snapshot, extract the ingredients needed for premise
 development. Do this before hook generation.
 
 Record:
 
 - real story or scene candidates from the raw idea, memory, transcript, or
   current-session context
+- transcript worldview packet matches: clusters, transcript references, cards,
+  repeated phrasing, worldview ingredients, and hot-take ingredients
 - observed pattern candidates when no first-person story is available
 - visible tension: the uncomfortable gap, cost, contradiction, or tradeoff
 - common belief: what the audience probably believes right now
@@ -233,6 +241,7 @@ Record:
 - reader value: what the reader learns, sees differently, or can do
 - proof available: what can be safely used
 - proof missing: what cannot be claimed without user confirmation
+- private/sensitive transcript material to exclude
 
 If this section is weak, say so. Do not let the hook lab proceed as if a clever
 opening can create value that the premise does not have.
@@ -687,6 +696,76 @@ with Christian's verified campaign-source ladder. Keep the hook's "unexpected
 best source" tension. Do not borrow the source's dinner/community proof.
 ```
 
+## Thought Leader Inspiration Workers
+
+When the user supplies a list of thought leaders, creators, profile URLs, or
+handles, run a separate inspiration analysis per person. This is different from
+general search: the source set is the person's own recent content.
+
+Use one bounded background worker per person when the host supports background
+agents. If not, process the list sequentially. Each worker must keep its output
+compact and must not return a full corpus dump.
+
+Worker steps:
+
+1. Resolve the person's profile URL or handle from the user input, tracked
+   people, or memory. If unresolved, ask for the URL/handle.
+2. Fetch recent posts with `mcp__sellable__fetch_linkedin_posts`.
+3. Fetch profile/follower context with `mcp__sellable__fetch_linkedin_profile`
+   when available.
+4. Score the person's recent posts by:
+   - topic fit to the user's current idea
+   - hook preview strength
+   - body payoff strength
+   - positioning density
+   - repeated success in the same lane
+   - engagement quality
+   - engagement per 1k followers when follower count is available
+   - adaptation fit for Christian/Sellable voice
+   - lead-magnet, giveaway, and status-only penalties
+5. Keep max 5 winners and max 5 rejected examples.
+6. Extract hook mechanics, body mechanics, sentence/rhythm moves, proof slots,
+   and close moves.
+7. Identify forbidden borrowing: source wording, source proof, jokes, personal
+   stories, audience status, and persona markers.
+8. Create one adapted direction for the user's selected premise in
+   Christian/Sellable voice.
+
+Worker output:
+
+```text
+Thought leader inspiration packet:
+person:
+profile_url:
+recent_posts_reviewed:
+follower_count: <number | unavailable>
+normalization_confidence: high | medium | low
+weighted_winners:
+  - source_url:
+    engagement:
+    engagement_per_1k_followers:
+    score:
+    why_kept:
+    first_3_line_preview:
+    hook_mechanics:
+    body_mechanics:
+    sentence_or_rhythm_moves:
+    forbidden_borrowing:
+adapted_direction:
+  inspiration_adapter:
+  voice_layer: Christian/Sellable
+  hook_shape:
+  body_shape:
+  proof_slots_needed:
+  why_it_might_win:
+  why_it_might_fail:
+rejected_examples:
+confidence_gaps:
+```
+
+Do not call the adapted direction "in <person>'s voice." It is an inspiration
+adapter that borrows public mechanics, then writes in the user's voice.
+
 ## Blocked States
 
 Local idea capture can still succeed when research fails.

package/skills/create-post/references/post-file-contract.md

@@ -50,10 +50,13 @@ Idea files must preserve:
 - `updatedAt`
 - exact raw source between raw-source markers
 - optional distilled brief that does not add new claims
+- transcript worldview packet when create-post has mined relevant
+  transcript/content-memory material for this idea
 
 Hook research files must preserve:
 
 - source idea ID
+- transcript/content-memory match status and transcript worldview packet
 - keywords searched
 - filters used
 - source post URLs
@@ -67,9 +70,14 @@ Hook research files must preserve:
 - source hook preview measurements, including text basis, char count including
   newlines, physical/content line counts, longest nonblank line, blank-line
   visual risk, and mobile/desktop preview budget status
+- audience tension snapshot and selected angle
 - rendered preview records for kept source hooks and adapted hook blocks,
   including literal mobile/desktop preview blocks and whether the first-screen
   promise is visible
+- thought leader inspiration packets when the user supplied creators, including
+  worker status, profile URL/handle, recent posts reviewed, weighted winners,
+  follower-adjusted signal when available, allowed mechanics to adapt, and
+  forbidden borrowing
 - source-message outlines for keeper posts, preserving source paragraph order
   and branching each paragraph, line, or phrase into high-level goal, reader
   effect, reusable move, and adaptation guard without reproducing the full
@@ -81,6 +89,8 @@ Draft files must preserve:
 
 - source idea ID
 - hook research ID
+- transcript worldview packet used to build the premise, worldview, and hot
+  take
 - versioned draft ID, normally ending in `_v1`, `_v2`, `_v3`, etc.
 - iteration metadata when there is a prior or baseline draft:
   - `version`
@@ -94,6 +104,9 @@ Draft files must preserve:
 - draft body
 - source-message outline for any outside post being adapted, when the draft's
   body shape was learned from a specific source post
+- thought leader inspiration lab when used, including the selected inspiration
+  adapter, variants considered, Christian/Sellable voice layer, and
+  copying/voice-clone risk
 - pre-draft narrative outline: hierarchical `I.`, `A.`, `i.` outline covering
   hook debt, thesis, reader, core mechanism, definitions, proof claims,
   working body patterns adapted, narrative beats, mobile scan path, body

package/skills/create-post/references/post-validation.md

@@ -6,6 +6,7 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 
 - `sourceIdeaId`
 - `hookResearchId`
+- `transcriptWorldviewPacket`
 - `iteration`
 - `selectedPremiseCard`
 - `candidateHooksConsidered`
@@ -25,10 +26,13 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
   step-by-step mode
 - `proofClaimsUsed`
 - `proofClaimSources`
+- `worldviewSource`
+- `hotTakeSource`
 - `storyFilesConsulted`
 - `goldStandardsConsulted`
 - `voiceRulesApplied`
-- `marketBeliefAudit`
+- `audienceTensionAudit`
+- `thoughtLeaderInspirationLab`
 - `premiseValueAudit`
 - `mobileScanabilityAudit`
 - `templateAdaptationAudit`
@@ -110,7 +114,7 @@ Each candidate should include:
 After the first draft:
 
 1. remove unsupported claims
-2. verify the draft is anchored to the selected market belief and controversy
+2. verify the draft is anchored to the selected audience tension and credible angle
 3. verify the real story/scene, tension, and reader value are visible early
 4. verify the body repays the selected hook's curiosity debt
 5. verify the final post follows the selected positioning sequence or explains
@@ -171,6 +175,12 @@ Record:
 - `readerValue`: what the reader learns, sees differently, or can do
 - `proofAvailable`: source-backed proof used
 - `proofMissing`: claims intentionally avoided or requiring user input
+- `transcriptWorldviewPacket`: clusters, transcript references, cards, repeated
+  phrasing, worldview ingredients, hot-take ingredients, proof/story available,
+  proof/story missing, private exclusions, and confidence
+- `worldviewSource`: the source-backed belief that makes the post feel earned
+- `hotTakeSource`: the source-backed disagreement or operating lesson behind
+  the hook/premise
 - `sourceMessageOutline`: source post decomposition in original order, with
   paragraph/line/phrase branches, high-level goal of each branch, reader effect,
   reusable move, and adaptation guard
@@ -181,7 +191,7 @@ Record:
   artifact is `preDraftNarrativeOutline`
 - `premiseQualityGates`: pass/fail for `specific_scene_or_pattern`,
   `clear_reader`, `visible_tension`, `reader_value`, `credible_speaker`,
-  `proof_safety`, `market_heat`, and `pre_draft_narrative_outline`
+  `proof_safety`, `audience_tension`, and `pre_draft_narrative_outline`
 - `bodyOutline`: how the body delivers the premise before prose
 - `viralPostOutline`: the selected narrative structure, including beat jobs
 - `hookToBodyPromiseMap`: how the body repays the hook's open loop
@@ -191,6 +201,10 @@ If the draft has no specific scene or observed pattern, no visible tension, or
 no reader value beyond "this is interesting," save as `needs_revision`. Do not
 mark it `ready` because the hook passes preview limits.
 
+Save as `needs_revision` when the post claims a worldview or hot take but the
+receipt cannot trace it to raw source, transcript/content-memory, core memory,
+or a current user answer.
+
 ## Pre-Draft Narrative Outline Audit
 
 Before a draft can be `ready`, validate that the narrative outline was locked
@@ -296,27 +310,53 @@ Save as `needs_revision` when the draft copies outside wording, borrows outside
 proof, keeps a source template's status without equivalent user authority, or
 uses a hook whose promised body payoff is not delivered.
 
-## Market Belief Audit
+## Audience Tension Audit
 
 Before a draft can be `ready`, validate that it is not merely an internally
-coherent idea. It must be anchored to the saved research's market belief map.
+coherent idea. It must be anchored to the saved research's audience tension
+snapshot.
 
 Record:
 
 - `resonatingIdea`: the current-space idea this draft enters
-- `implicitBelief`: the belief the audience likely already holds
+- `visibleAudienceTension`: the contradiction, tradeoff, cost, or unfinished
+  question readers are reacting to
 - `audienceWant`: what the audience wants permission, leverage, proof, or a new
   category for
-- `audienceResentmentOrFear`: what frustration or risk gives the post tension
-- `selectedControversy`: the claim the post is testing
+- `audienceObjectionOrFear`: what skepticism, frustration, or risk gives the post tension
+- `selectedAngle`: the claim the post is testing
 - `credibleWhyUs`: why the user can credibly say this from raw idea, memory,
   story, proof, or product mechanism
 - `engagementReason`: why someone would react, comment, repost, or argue
 - `unsupportedHypeRemoved`: unsupported claims removed during finalizer
 
-If `selectedControversy` is missing, if the audience belief is only a generic
-label like "founders want growth," or if `credibleWhyUs` depends on borrowed
-proof from another creator, save as `needs_revision`.
+If `selectedAngle` is missing, if the audience tension is only a generic label
+like "founders want growth," or if `credibleWhyUs` depends on borrowed proof
+from another creator, save as `needs_revision`.
+
+## Thought Leader Inspiration Audit
+
+When the user supplied thought leaders or creators, validate that inspiration
+was used as structural adaptation, not persona cloning.
+
+Record:
+
+- `thoughtLeaderList`: names and profile URLs or handles
+- `workerPackets`: one packet per person, or `not_available` with reason
+- `weightedWinners`: best posts used, with follower-adjusted signal when
+  available
+- `normalizationConfidence`: high | medium | low
+- `inspirationAdapters`: hook/body mechanics selected for adaptation
+- `voiceLayer`: must be `Christian/Sellable`
+- `forbiddenBorrowingAvoided`: source wording, proof, jokes, personal stories,
+  status, and persona markers avoided
+- `variantsConsidered`: adapted variants generated from the selected premise
+- `selectedVariant`: winning adapter and why
+- `copyingOrVoiceCloneRisk`: pass | needs_revision | blocked
+
+Save as `needs_revision` when a draft imitates a living person's voice, borrows
+their proof/status, copies outside wording, or lets a creator with a giant
+audience win without any follower-adjusted or confidence-adjusted signal.
 
 ## LinkedIn Preview Audit
 

package/skills/create-post/references/premise-development.md

@@ -3,7 +3,7 @@
 A strong post is not an idea with a better hook. A strong post is a valuable
 premise wrapped in a sharp opening.
 
-Use this stage after market/hook research and before hook candidates. V2 premise
+Use this stage after audience/hook research and before hook candidates. V2 premise
 development also consumes the source post templates from hook research:
 post positioning breakdowns, viral-post outlines, hook-to-body promise maps, and
 body expression inputs.
@@ -61,10 +61,14 @@ Before writing premise cards, search the available source material:
 
 - raw idea text
 - voice memo or transcript if provided
+- `Transcript Worldview Packet` from create-post capture
 - `core/story-bank.md`
 - `core/answer-bank.md`
 - `core/proof-ledger.md`
 - `core/wins-ledger.md`
+- `core/transcripts/INDEX.md`
+- `core/content-memory/INDEX.md`, relevant clusters, cards, questions, and
+  post seeds
 - approved references and gold standards
 - current-session user corrections or rejections
 
@@ -76,11 +80,37 @@ Look for:
 - a before/after: what changed in the user's belief
 - a specific object: Slack note, customer call, campaign table, reply, list,
   demo, failed draft, stale idea, messy workflow
+- repeated worldview: the user's recurring operating belief behind the idea
+- hot-take ingredient: the specific advice, default behavior, or market cliche
+  the user is pushing against
 
 If no real story is present, use an observed pattern only if it is traceable to
 the raw source or memory. Mark the gap in the premise card. Do not fabricate a
 customer, call, outcome, date, metric, or private scene.
 
+## Worldview And Hot-Take Extraction
+
+Before scoring premise cards, extract the user's source-backed worldview from
+the transcript packet:
+
+```text
+Worldview extraction:
+- worldview claim:
+- source transcript/cluster/card:
+- repeated phrase or language pattern:
+- lived proof behind it:
+- common advice it challenges:
+- hot take version:
+- public-safe version:
+- private/sensitive material to avoid:
+- confidence: strong | medium | weak
+```
+
+A good hot take is not just a contrarian sentence. It must trace to something
+the user has said, seen, shipped, sold, or learned repeatedly. If the hot take
+only exists because an outside creator framed it well, mark it as borrowed and
+do not use it as the user's premise.
+
 ## Premise Cards
 
 Generate 3-5 premise cards before hooks. Each card must use this shape:
@@ -109,7 +139,7 @@ tension:
 reader value:
 <what the reader learns, sees differently, or can do after reading>
 
-why now / market heat:
+why now / audience tension:
 <what current research says is resonating>
 
 credible why-us:
@@ -121,6 +151,12 @@ proof available:
 proof missing:
 <claims that cannot be made yet>
 
+worldview source:
+<transcript/cluster/card/source-backed belief used>
+
+hot take:
+<public-safe sharp version of the user's source-backed disagreement>
+
 best frame:
 story | contrarian take | teardown | founder confession | future thesis | lesson
 
@@ -366,7 +402,7 @@ A premise can move to hook generation only when it passes all of these:
 - `reader_value`: pass
 - `credible_speaker`: pass
 - `proof_safety`: pass
-- `market_heat`: pass or explained
+- `audience_tension`: pass or explained
 - `template_fit`: pass or explicitly no-template
 - `hook_to_body_repayment`: pass
 - `pre_draft_narrative_outline`: pass