@sellable/mcp 0.1.261 → 0.1.262

package/package.json

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

package/skills/create-post/SKILL.md

@@ -349,14 +349,22 @@ Visible Flow Trace
 - why it works:
 - why it may not transfer:
 
-5. Post Positioning Breakdowns
+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:
 
-6. Viral-Post Outlines
+7. Viral-Post Outlines
 - source template:
 - hook job:
 - see-more trigger:
@@ -364,7 +372,7 @@ Visible Flow Trace
 - body payoff:
 - close job:
 
-7. Market Belief Map
+8. Market Belief Map
 - resonating ideas:
 - implicit beliefs:
 - wants / resentments / fears:
@@ -372,7 +380,7 @@ Visible Flow Trace
 - why this user can credibly say it:
 - what not to claim:
 
-8. Premise Cards
+9. Premise Cards
 - 3-5 cards:
 - story/scene:
 - tension:
@@ -383,7 +391,7 @@ Visible Flow Trace
 - score:
 - selected premise:
 
-9. Source Template Selection
+10. Source Template Selection
 - selected template:
 - positioning sequence to borrow:
 - hook move to borrow:
@@ -392,7 +400,7 @@ Visible Flow Trace
 - forbidden borrowing:
 - no-template rationale if rejected:
 
-10. Hook Lab
+11. Hook Lab
 - at least 12 hooks:
 - rendered preview record or explicit preview-basis:
 - hook-to-body promise:
@@ -400,7 +408,7 @@ Visible Flow Trace
 - selected hook:
 - rejected winning-looking hooks and why:
 
-11. Pre-Draft Narrative Outline
+12. Pre-Draft Narrative Outline
 - hierarchical outline shown before draft:
 - I. hook and click debt:
 - II. thesis the post will defend:
@@ -410,7 +418,7 @@ Visible Flow Trace
 - VI. scan path and proof safety:
 - user corrections applied before prose:
 
-12. Body Expression Lab
+13. Body Expression Lab
 - 5-8 body-expression candidates:
 - best lines:
 - weak lines:
@@ -419,13 +427,13 @@ Visible Flow Trace
 - score:
 - combined body plan:
 
-13. Draft
+14. Draft
 - draft body:
 - lines intentionally copied from user source:
 - outside-source wording copied: yes/no:
 - known weak lines:
 
-14. Validation And Save
+15. Validation And Save
 - ready status:
 - proof gate:
 - voice gate:
@@ -619,6 +627,15 @@ Post positioning breakdown templates:
    - 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:
@@ -839,6 +856,7 @@ Draft from:
 - 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

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

@@ -7,12 +7,14 @@ readers click "see more," decompose each post into a reusable narrative and
 positioning template, and then adapt those templates to the user's real story
 without copying source wording.
 
-V2 research has four outputs:
+V2 research has five outputs:
 
 1. weighted source winners: the best recent posts to learn from
 2. hook autopsies: exact preview measurements, open loops, and tension created
-3. viral-post outlines: the narrative structure of each source post
-4. post positioning breakdown templates: line-level positioning and narrative
+3. source-message outlines: the paragraph/line/phrase structure of each source
+   post in its original order
+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
 
 ## Search Inputs
@@ -434,13 +436,70 @@ line_map:
 ```
 
 Break long lines into phrase-level segments when one line contains multiple
-jobs. Preserve the original source line in the research artifact, but never
-copy it into the draft unless it is the user's own approved post.
+jobs. Use short anchors or paraphrased line labels for outside source posts; do
+not reproduce the full outside post. Never copy source wording into the draft
+unless it is the user's own approved post.
+
+## Source Message Outline
+
+Before converting a source post into a reusable template, outline the source
+message as it is. This is the branch map of the original post, not the adapted
+draft plan.
+
+The outline must preserve the source post's order and branch each paragraph,
+line, or phrase into the high-level rhetorical goal it serves. If a paragraph
+contains several jobs, split it into phrase-level branches.
+
+Use this format:
+
+```text
+Source Message Outline:
+source: <author + URL>
+outline_basis: full_text | excerpt_only | screenshot | user_supplied_text
+copyright_safety: use short anchors/paraphrases; do not reproduce the full source
+
+P1. <short paragraph anchor or paraphrase>
+  goal: <what this paragraph makes the reader think/feel/wonder>
+  why_here: <why it appears at this point in the sequence>
+  branches:
+    A. <phrase/line anchor or paraphrase>
+       job: <high-level job of this phrase/line>
+       reader_effect: <what changes in the reader>
+       reusable_move: <what can be adapted without copying wording>
+    B. <phrase/line anchor or paraphrase>
+       job:
+       reader_effect:
+       reusable_move:
+
+P2. <short paragraph anchor or paraphrase>
+  goal:
+  why_here:
+  branches:
+    A.
+       job:
+       reader_effect:
+       reusable_move:
+```
+
+Quality rules:
+
+- Do not summarize the whole post first and then invent a cleaner outline.
+- Do not skip ordinary body paragraphs; the point is to learn the source's real
+  sequence, including setup, repetition, proof, turns, and close.
+- Every branch must answer: "What is this exact line/paragraph/phrase doing?"
+- Use `P1`, `P2`, `A`, `B`, and `i` structure so the user can compare it
+  against the source post.
+- If only an excerpt is available, label `outline_basis: excerpt_only` and do
+  not infer hidden body structure.
+- After the source-message outline, then create the viral-post outline and
+  template. The adapted outline cannot replace the source-message outline.
 
 ## Viral-Post Outline
 
-After the line-level breakdown, convert each keeper into a viral-post outline.
-The outline is the narrative skeleton beneath the exact words.
+After the source-message outline and line-level breakdown, convert each keeper
+into a viral-post outline. The viral-post outline is the reusable narrative
+skeleton beneath the exact words, not a replacement for the source-message
+outline.
 
 Use this format:
 

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

@@ -70,6 +70,10 @@ Hook research files must preserve:
 - 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
+- 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
+  outside source post
 - extracted hook patterns
 - selected hook basis
 
@@ -88,6 +92,8 @@ Draft files must preserve:
   - score fields for hook, proof, voice, specificity, skimmability, and publish confidence
   - `verdict`: `baseline`, `keep`, `revise`, `reject`, `publish_candidate`, or a similarly explicit state
 - draft body
+- source-message outline for any outside post being adapted, when the draft's
+  body shape was learned from a specific source post
 - 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

@@ -11,6 +11,7 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 - `candidateHooksConsidered`
 - `selectedHook`
 - `selectedHookWhy`
+- `sourceMessageOutline`
 - `preDraftNarrativeOutline`
 - `preDraftStructureBrief` as a legacy compatibility alias when older drafts or
   downstream readers still expect it
@@ -170,6 +171,9 @@ Record:
 - `readerValue`: what the reader learns, sees differently, or can do
 - `proofAvailable`: source-backed proof used
 - `proofMissing`: claims intentionally avoided or requiring user input
+- `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
 - `preDraftNarrativeOutline`: hierarchical `I.`, `A.`, `i.` outline showing
   hook debt, thesis, operating model, working body patterns adapted, narrative
   beats, scan path, proof claims, and abstractions to remove

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

@@ -309,12 +309,15 @@ III. Operating model
 
 IV. Body shape borrowed from posts that worked
    A. Selected source template or no-template rationale: <source or rationale>
-   B. Working body pattern(s) being adapted:
+   B. Source-message outline being adapted:
+      i. <source post + P1/P2/P3 branch sequence from the original message>
+      ii. <which original paragraph/line/phrase jobs matter most>
+   C. 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:
+   D. What gets borrowed:
       i. <narrative job, sequence, transition, or proof order>
-   D. What must not be copied:
+   E. What must not be copied:
       i. <source wording, creator-specific proof, joke, or context>
 
 V. Narrative beats
@@ -344,9 +347,10 @@ Quality gate:
 - The outline must include proof claims and risk before prose.
 - The outline must define any operating terms that could be misunderstood.
 - The outline must use `I.`, `A.`, and `i.` hierarchy. A flat field list fails.
-- If the post is adapting bodies that worked, the outline must name the body
-  pattern and what beat order, proof order, or transition logic is being
-  borrowed.
+- If the post is adapting bodies that worked, the outline must name the source
+  message outline being adapted and the body pattern, including which original
+  paragraph/line/phrase jobs transfer and what beat order, proof order, or
+  transition logic is being borrowed.
 - If the post is a field guide, the narrative beats must show the hierarchy
   before prose, such as best-to-worst, highest-to-lowest intent, or
   source-to-outcome.