@sellable/mcp 0.1.267 → 0.1.269

package/skills/create-post/SKILL.md

@@ -34,17 +34,12 @@ 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 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.
+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.
 
 Hard fail patterns:
 
@@ -55,8 +50,6 @@ 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>
 
@@ -91,7 +84,6 @@ Before drafting, load all required assets with `mcp__sellable__get_subskill_asse
 3. `subskillName: "create-post", assetPath: "references/premise-development.md"`
 4. `subskillName: "create-post", assetPath: "references/post-validation.md"`
 5. `subskillName: "create-post", assetPath: "references/gold-standard-post-pack.md"`
-6. `subskillName: "create-post", assetPath: "references/linkedin-preview-rendering.md"`
 
 If any required asset is missing, unreadable, truncated without continuation, or internally inconsistent, return:
 
@@ -115,8 +107,6 @@ Use these MCP tools when available:
 - `mcp__sellable__get_post_idea`
 - `mcp__sellable__list_post_ideas`
 - `mcp__sellable__save_hook_research`
-- `mcp__sellable__calculate_linkedin_hook_preview`
-- `mcp__sellable__render_linkedin_post_preview`
 - `mcp__sellable__save_post_draft`
 - `mcp__sellable__update_post_draft`
 - `mcp__sellable__list_post_draft_iterations`
@@ -161,23 +151,6 @@ 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.
@@ -245,15 +218,12 @@ 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. 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.
+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.
 
 ## Ad Hoc Mode
 
@@ -313,261 +283,6 @@ Space benchmark research:
 7. For each approved tracked person, call `mcp__sellable__upsert_engage_tracked_person`.
 
 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.
-Also use this mode when the user says "use my configured thought leaders",
-"use my influencers", "use the tracked people list", or similar.
-
-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. If the user asks
-   for the configured list, load it from memory-backed
-   `discovery/influencers.md` and include only rows where
-   `Include in Discovery` is not `false`. Treat the `Reason` column as the
-   person's lane/adaptation brief.
-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.
-   Each configured person must receive full person-specific research; do not
-   collapse the configured list into generic space research.
-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,
-validate that the workflow is working, debug a bad output, explain why a draft
-is bad, or otherwise asks for the process to be explicit.
-
-This mode exists because a validation receipt hidden inside a saved draft is not
-enough. The user must be able to inspect the reasoning path before the system
-claims the workflow worked.
-
-In visible whole-flow debug mode:
-
-1. Run the normal create-post workflow.
-2. Show a `Visible Flow Trace` with every checkpoint below.
-3. Mark each checkpoint `pass`, `weak`, `fail`, or `blocked`.
-4. Include the concrete output from that checkpoint, not only a label.
-5. If any checkpoint is weak or failed, name the exact quality break and the
-   downstream effect on the draft.
-6. Do not call the run successful just because files were saved.
-7. Do not hide premise cards, source-template selection, hook candidates,
-   pre-draft structure, body-expression candidates, or validation findings only
-   inside the saved artifact.
-
-The trace must use this order:
-
-```text
-Visible Flow Trace
-
-0. Bootstrap
-- auth/workspace:
-- canonical prompt loaded:
-- required assets loaded:
-- memory loaded:
-- package/version notes:
-
-1. Raw Idea Capture
-- idea id:
-- 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:
-- keywords:
-- result count:
-- full-text fetches:
-- search gaps:
-
-3. Weighted Source Selection
-- kept sources:
-- rejected sources:
-- keeper scores:
-- lead-magnet / engagement-bait penalties:
-- why the top source actually fits:
-
-4. Hook Autopsies
-- source hook:
-- calculated mobile/desktop visible blocks from
-  `calculate_linkedin_hook_preview` or authenticated LinkedIn screenshot:
-- optional visual artifact from `render_linkedin_post_preview`:
-- see-more tension:
-- curiosity debt:
-- body promise:
-- why it works:
-- why it may not transfer:
-
-5. Source Message Outlines
-- source:
-- outline basis:
-- source paragraph order:
-- branches by paragraph/line/phrase:
-- high-level goal of each branch:
-- reusable move without copying wording:
-
-6. Post Positioning Breakdowns
-- source:
-- positioning sequence:
-- line-level narrative techniques:
-- reusable template lines:
-- adaptation guards:
-
-7. Viral-Post Outlines
-- source template:
-- hook job:
-- see-more trigger:
-- beat sequence:
-- body payoff:
-- close job:
-
-8. Audience Tension Snapshot
-- resonating ideas:
-- visible audience tension:
-- wants / objections / fears:
-- credible angle:
-- why this user can credibly say it:
-- what not to claim:
-
-9. Premise Cards
-- 3-5 cards:
-- story/scene:
-- tension:
-- reader value:
-- proof available:
-- proof missing:
-- source-template fit:
-- score:
-- selected premise:
-
-10. Source Template Selection
-- selected template:
-- positioning sequence to borrow:
-- hook move to borrow:
-- body outline to borrow:
-- required user proof:
-- forbidden borrowing:
-- no-template rationale if rejected:
-
-11. Hook Lab
-- at least 12 hooks:
-- calculated preview from `calculate_linkedin_hook_preview`:
-- optional visual artifact from `render_linkedin_post_preview` for finalists:
-- hook-to-body promise:
-- score:
-- selected hook:
-- rejected winning-looking hooks and why:
-
-12. Pre-Draft Narrative Outline
-- hierarchical outline shown before draft:
-- I. hook and click debt:
-- II. thesis the post will defend:
-- III. operating model:
-- IV. body shape borrowed from posts that worked:
-- V. narrative beats:
-- VI. scan path and proof safety:
-- user corrections applied before prose:
-
-13. Body Expression Lab
-- 5-8 body-expression candidates:
-- best lines:
-- weak lines:
-- hook promise repayment:
-- proof risk:
-- score:
-- combined body plan:
-
-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:
-
-16. Validation And Save
-- ready status:
-- proof gate:
-- voice gate:
-- anti-AI gate:
-- mobile preview gate:
-- template adaptation gate:
-- hook-to-body repayment:
-- quality break, if any:
-- saved idea path:
-- saved research path:
-- saved draft path:
-```
-
-Quality-break rules:
-
-- If the draft is bad, say which checkpoint produced the bad draft. For example:
-  weak raw story, wrong selected source template, hook promise not repaid,
-  body expression lab too generic, proof missing, or voice mismatch.
-- A draft with a coherent validation receipt but poor body copy is not a
-  successful run. Mark it `needs_revision` and show the checkpoint where the
-  body lost the premise.
-- If the source idea is too abstract, stop at premise development or save a
-  `needs_revision` draft only after showing the missing story/proof.
-- If the user is judging the workflow itself, prefer showing the trace over
-  optimizing for a polished final post.
 </modes>
 
 <pipeline>
@@ -578,8 +293,6 @@ 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:
 
@@ -589,35 +302,6 @@ 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`.
@@ -633,22 +317,11 @@ The research worker must return a compact packet only:
 
 - source examples kept and rejected
 - full adapted hook blocks
-- audience tension snapshot: resonating ideas, visible tensions, audience wants,
-  objections, fears, and credible angles
+- market belief map: resonating ideas, implicit beliefs, audience wants, resentments, fears, and credible controversy 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
-- viral-post outlines for the best source posts
-- line-to-template conversions that turn source structures into reusable
-  templates without source wording
-- 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
 
@@ -665,20 +338,12 @@ 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 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.
+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.
 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
    shapes, transitions, and body language patterns.
-12. Create a post positioning breakdown for each keeper post: line/phrase,
-    category, narrative technique, tension created, reader question opened,
-    proof dependency, and reusable template line.
-13. Convert each keeper into a viral-post outline: hook job, see-more trigger,
-    body payoff, close job, and beat-by-beat narrative structure.
-14. Convert the best outlines into reusable post templates with positioning
-    sequences, required story/proof inputs, forbidden borrowing, and
-    Sellable-specific adaptation instructions.
-15. Save the research with `mcp__sellable__save_hook_research`.
+12. Save the research with `mcp__sellable__save_hook_research`.
 
 Record provenance:
 
@@ -692,17 +357,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
-- audience tension snapshot and selected angle
-- thought leader inspiration packets and selected inspiration adapters when used
+- market belief map and selected controversy
 - premise cards and selected premise
 - exact phrase patterns and sentence shapes
-- post positioning breakdowns
-- viral-post outlines
-- reusable post templates
-- hook-to-body promise maps
 - body structures and body language patterns
 - why each pattern fits the user's idea and voice
 
@@ -725,7 +384,6 @@ The `Research Learning Report` must include:
 ```text
 Research status:
 - idea/topic:
-- transcript worldview packet:
 - research artifact:
 - search window:
 - keywords:
@@ -735,15 +393,15 @@ Research status:
 Best source examples:
 1. author, URL, engagement, why kept, why not copied
 
-Audience tension snapshot:
+Market belief map:
 - resonating ideas:
-- visible audience tension:
+- implicit beliefs:
 - audience wants:
-- audience objections:
+- audience resentments:
 - audience fears:
-- credible angles to test:
+- controversial angles to test:
 - avoid because:
-- selected angle:
+- selected controversy:
 
 Premise cards:
 1. premise + real story/scene + tension + reader value + proof gap + score
@@ -752,10 +410,7 @@ Hook patterns learned:
 1. full adapted hook block
    - source mechanism:
    - preview budget:
-   - see-more tension:
-   - curiosity debt:
    - internal question:
-   - hook-to-body promise:
    - why it fits / why it does not:
 
 Specific words and phrase shapes:
@@ -766,58 +421,13 @@ Specific words and phrase shapes:
    - adapted Sellable form:
    - do not copy:
 
-Post positioning breakdown templates:
-1. source + template name
-   - positioning sequence:
-   - line-level narrative techniques:
-   - tension created:
-   - reader questions opened:
-   - reusable template lines:
-   - Sellable adaptation:
-
-Source message outlines:
-1. source + outline basis
-   - source paragraph order:
-   - paragraph/line/phrase branches:
-   - high-level goal of each branch:
-   - reader effect:
-   - reusable move:
-   - adaptation guard:
-
-Viral-post outlines:
-1. outline name
-   - hook job:
-   - see-more trigger:
-   - body payoff:
-   - close job:
-   - beat sequence:
-
-Line-to-template conversion:
-1. source line/beat
-   - narrative job:
-   - template line shape:
-   - required user story/proof:
-   - forbidden borrowing:
-   - adapted Sellable expression:
-
 Body structures learned:
 1. structure name
    - source:
-   - positioning sequence:
    - sequence:
    - 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:
@@ -827,9 +437,9 @@ Save recommendations:
 - gold-standard candidates:
 
 Recommended draft directions:
-1. premise card + source template + hook block + viral outline + body structure
-2. premise card + source template + hook block + viral outline + body structure
-3. premise card + source template + hook block + viral outline + body structure
+1. premise card + hook block + body structure
+2. premise card + hook block + body structure
+3. premise card + hook block + body structure
 ```
 
 Keep this report concise enough to read, but concrete enough that another agent
@@ -839,13 +449,11 @@ could draft from it without redoing research.
 
 Use `references/premise-development.md`.
 
-Generate 3-5 `Premise Card` candidates from the raw idea, audience/source research, core
+Generate 3-5 `Premise Card` candidates from the raw idea, market 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
-score. Each card must also evaluate which source template or no-template path
-fits, which positioning sequence to test, and how the hook promise will be
-repaid in the body.
+score.
 
 Select the strongest premise before hook generation. The selected premise must
 pass:
@@ -856,104 +464,13 @@ pass:
 - `reader_value`
 - `credible_speaker`
 - `proof_safety`
-- `audience_tension`
-- `template_fit`
-- `hook_to_body_repayment`
+- `market_heat`
 
-If the idea has audience tension but no real scene, ask for the missing scene unless
+If the idea has market heat 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.
 
-## Step 1.9: Pre-Draft Narrative Outline
-
-Before generating final draft prose, create and show a compact `Pre-Draft
-Narrative Outline`. This is not a checklist. It is the user-visible argument
-skeleton that lets the user confirm what the post will say, in what order, and
-which proven body shapes will guide the draft before the system writes body
-copy.
-
-The outline must be concise, mobile-scanable, and concrete enough for the user
-to approve or correct. Do not hide it inside the validation receipt after the
-draft. Show it before writing the draft body unless the user explicitly says to
-skip outline/structure and write immediately. Even when the user skips the
-visible checkpoint, still include the outline in the validation receipt.
-
-The `Pre-Draft Narrative Outline` must use hierarchical outline notation:
-Roman numerals for major narrative beats, letters for sub-beats, and lowercase
-roman numerals for proof/examples/body moves. Do not replace this with a flat
-field list.
-
-The `Pre-Draft Narrative Outline` must include:
-
-```text
-Pre-Draft Narrative Outline
-I. Hook and click debt
-   A. Selected hook:
-   B. Rendered mobile preview verdict:
-   C. What "see more" must repay:
-
-II. Thesis the post will defend
-   A. One-sentence thesis:
-   B. Reader being taught:
-   C. Why this reader cares now:
-
-III. Operating model
-   A. Core equation or mechanism:
-   B. Key definitions:
-      i. <term>: <plain definition + concrete examples>
-      ii. <term>: <plain definition + concrete examples>
-
-IV. Body shape borrowed from posts that worked
-   A. Selected source template or no-template rationale:
-   B. Working body pattern(s) being adapted:
-      i. <pattern name>: <beat order and why it works>
-      ii. <pattern name>: <beat order and why it works>
-   C. What gets borrowed:
-      i. <narrative job, sequence, transition, or proof order>
-   D. What must not be copied:
-      i. <source wording, creator-specific proof, joke, or context>
-
-V. Narrative beats
-   A. Beat 1: <job, reader state before/after, example/proof>
-      i. Line shape or section label:
-      ii. Concrete examples:
-   B. Beat 2: <job, reader state before/after, example/proof>
-      i. Line shape or section label:
-      ii. Concrete examples:
-   C. Beat 3: <job, reader state before/after, example/proof>
-      i. Line shape or section label:
-      ii. Concrete examples:
-
-VI. Scan path and proof safety
-   A. Mobile scan path:
-   B. Proof claims:
-      i. <claim>: <source + public-safety status>
-   C. Abstractions to remove:
-      i. <abstract phrase> -> <concrete replacement>
-   D. Draft risks:
-```
-
-Rules:
-
-- The hook must already have a rendered mobile and desktop preview record.
-- The thesis must be one sentence the post can defend.
-- The reader must be specific enough to guide what gets cut.
-- `Body shape borrowed from posts that worked` must name the body pattern or
-  explain why no-template is stronger. It must say what narrative job is being
-  borrowed, not just "make it like this creator."
-- `Narrative beats` must show the order of the argument with `I.`, `A.`, and
-  `i.`-style hierarchy. A flat checklist fails this step.
-- Key definitions must name concrete examples when the post teaches an
-  operating concept. For example, define `lead source` as how the list was
-  built, not as a persona label.
-- `mobile scan path` must say what a reader understands if they read only the
-  hook, separators, section labels, numbers, and final line.
-- `abstractions to remove` must list abstract phrases and the concrete words
-  that will replace them.
-- If the user corrects the outline, update the outline first, then draft. Do
-  not patch the final prose while leaving the outline stale.
-
 ## Step 2: Hook Candidates
 
 Generate at least 12 hook candidates from the selected premise unless the user
@@ -987,103 +504,35 @@ Each hook must include:
 
 Do not copy source wording. Copy only the structure.
 
-Use the rendered-preview contract from
-`references/linkedin-preview-rendering.md`. LinkedIn does not publish exact
-"see more" cutoff rules, and rendering varies by device, app version, font,
-media, and line break. Treat character counts as diagnostics only, not as proof
-that the hook will render before "see more."
-
-The selected hook and top candidates must include literal mobile and desktop
-visible blocks from `mcp__sellable__calculate_linkedin_hook_preview`.
-Observed LinkedIn screenshots and current third-party preview tools support a
-line-count model: review the first 3 rendered visual lines, not the first 210
-characters. Blank lines and `--` separators consume visible preview lines.
-Use `mcp__sellable__render_linkedin_post_preview` only when a visual QA artifact
-is useful.
-
-Use:
-
-- `pass`: rendered mobile preview shows the pain, proof, or curiosity by the end
-  of the first 3 rendered lines, and either the core point is visible or a
-  specific intentional open loop is visible with immediate body payoff planned
-- `warn`: rendered mobile preview creates useful curiosity but wrapping,
-  blank-line rhythm, media risk, or one missing context word weakens it; include
-  a compact fallback
-- `fail`: the hook's real point appears after the rendered mobile review clamp,
-  the visible open loop is vague, blank lines consume the preview before the
-  point, or desktop fit is the only reason it looks good
+Use this conservative mobile-first LinkedIn preview gate. LinkedIn does not
+publish exact "see more" cutoff rules, and rendering varies by device, app
+version, font, media, and line break. These are v1 safety budgets, not claims
+about an official LinkedIn limit:
+
+- `pass`: hook is <= 110 chars including newlines, every nonblank line is <= 45 chars, and the hook's core point lands before likely truncation.
+- `warn`: hook is 111-140 chars including newlines, any nonblank line is 46-55 chars, or blank lines create visual-line risk. Blank lines are allowed, but they count as physical lines.
+- `fail`: hook is > 140 chars including newlines, any nonblank line is > 55 chars, or the hook's point depends on text after likely truncation.
 
 Desktop preview usually has more room. Still record `desktopPreviewFit`, but
-never let desktop fit compensate for a mobile `fail`. Do not tell the user "we
-know" how LinkedIn will render unless there is an authenticated LinkedIn
-screenshot; say it passes the renderer and show the visible blocks.
+never let desktop fit compensate for a mobile `fail`.
 
 If a hook's point depends on text after the likely preview, rewrite it before
 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`
 - hook research artifact
-- selected source template or no-template rationale
-- source-message outline for any outside post being adapted
-- viral-post outline
-- post positioning breakdown template
-- body expression candidates and combined body plan
 - user's core memory
 - 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.
 
@@ -1095,28 +544,16 @@ 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
 - candidate hooks considered
 - 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
-- body expression candidates and combined body plan
 - proof claims used and source
 - story/proof files consulted
 - 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
 - simplifier/concrete-language audit findings
 - voice audit findings
 - anti-AI audit findings
@@ -1211,18 +648,8 @@ iteration:
   score: <compact score object>
 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
   proof: pass | needs_user_input | blocked
   voice: pass | needs_revision
   anti_ai: pass | needs_revision