@sellable/mcp 0.1.257 → 0.1.258

package/package.json

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

package/skills/create-post/SKILL.md

@@ -60,8 +60,9 @@ Do:
 
 - capture rough ideas, voice memos, freestyle notes, and ad hoc prompts
 - research currently working LinkedIn hooks
+- reverse engineer why source hooks work, what shape to keep, and what not to copy
 - develop premise cards with real story/observed tension and reader value
-- generate hook candidates
+- explore many hook angle territories before choosing the winning hook
 - draft a post body that stays true to the source idea
 - run validation before calling a draft ready
 - save ideas, hook research, drafts, and published records under `~/.sellable/content/linkedin/**`
@@ -318,7 +319,10 @@ and drafting gate.
 The research worker must return a compact packet only:
 
 - source examples kept and rejected
+- hook reverse-engineering autopsies: why each source hook works, which shape to
+  keep, what not to copy, and what payoff the body must deliver
 - full adapted hook blocks
+- angle territories tested before drafting
 - 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
 - reach-normalized signal notes, including follower-band fit when available
@@ -346,9 +350,13 @@ Default flow:
 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. Render each kept source hook and adapted hook block through the LinkedIn
+12. For each keeper, create a `hookAutopsy`: the source mechanism, open-loop
+   type, click question, promised payoff, specificity anchor, tension opened,
+   source shape to keep, source words not to copy, and adaptation rule for the
+   user's idea.
+13. Render each kept source hook and adapted hook block through the LinkedIn
    preview rendering contract. Character counts alone are not enough.
-13. Save the research with `mcp__sellable__save_hook_research`.
+14. Save the research with `mcp__sellable__save_hook_research`.
 
 Record provenance:
 
@@ -367,6 +375,9 @@ Record provenance:
 - source hook rendered preview records and whether they came from full text,
   authenticated LinkedIn screenshots, or a search preview
 - selected hook patterns
+- hook reverse-engineering autopsies, including `clickQuestion`,
+  `promisedPayoff`, `sourceShapeToKeep`, `sourceWordsNotToCopy`, and
+  `adaptationRule`
 - market belief map and selected controversy
 - premise cards and selected premise
 - exact phrase patterns and sentence shapes
@@ -425,6 +436,11 @@ Premise cards:
 Hook patterns learned:
 1. full adapted hook block
    - source mechanism:
+   - open-loop type:
+   - click question:
+   - promised payoff:
+   - source shape to keep:
+   - source words not to copy:
    - rendered preview:
      - mobile visible block:
      - desktop visible block:
@@ -456,9 +472,9 @@ Save recommendations:
 - gold-standard candidates:
 
 Recommended draft directions:
-1. premise card + hook block + body structure
-2. premise card + hook block + body structure
-3. premise card + hook block + body structure
+1. premise card + hook territory + hook block + click question + body structure
+2. premise card + hook territory + hook block + click question + body structure
+3. premise card + hook territory + hook block + click question + body structure
 ```
 
 Keep this report concise enough to read, but concrete enough that another agent
@@ -492,16 +508,32 @@ unless the premise still has concrete reader value.
 
 ## Step 2: Hook Candidates
 
-Generate at least 12 hook candidates from the selected premise unless the user
-requested a smaller set. Do not generate hooks directly from the raw idea before
-the premise is selected.
+Generate a hook angle matrix from the selected premise before writing the post
+body. Do not generate hooks directly from the raw idea before the premise is
+selected.
+
+Minimum exploration:
+
+- normal drafting: at least 8 distinct angle territories and 24 hook candidates
+- hook-critical requests, "nail the hook," "a ton of angles," or space research:
+  at least 12 distinct angle territories and 40 hook candidates
+- smaller set only when the user explicitly asks for fewer options
+
+Angle territories must be genuinely different. Use options such as enemy/tool
+contrast, hidden asset, first-person build proof, workflow reveal, contrarian
+category claim, mistake/confession, market timing, operator pain,
+asset/free-reveal without comment bait, specific person/company signal,
+before/after transformation, and question hook.
 
 Each hook must include:
 
 - selected premise
+- angle territory
 - premise tension opened
 - reader value implied
 - source hook pattern
+- source shape kept
+- source words not copied
 - why it fits this idea
 - `renderedPreview` using `references/linkedin-preview-rendering.md`
 - `mobileRenderedPreviewBlock`
@@ -509,6 +541,12 @@ Each hook must include:
 - `mobileRenderedLines`
 - `desktopRenderedLines`
 - `firstScreenPromise`
+- `intentionalOpenLoop`
+- `specificClickQuestionVisible`
+- `seeMoreClickReason`
+- `clickQuestion`
+- `payoffAfterFold`
+- `bodyProofObligation`
 - `corePainProofOrCuriosityVisibleMobile`
 - `corePointVisibleMobile`
 - `pointAfterMobileClamp`
@@ -528,6 +566,8 @@ Each hook must include:
 - `rewriteIfTruncated`
 - proof/story dependency
 - AI-tell risk
+- why it should win
+- why it should lose
 - score
 
 Do not copy source wording. Copy only the structure.
@@ -548,23 +588,28 @@ available:
 Use the rendered gates from `references/linkedin-preview-rendering.md`:
 
 - `pass`: the mobile rendered preview shows the pain, proof, or curiosity by
-  the end of the first 3 rendered lines, and the core point is understandable
-  without opening "see more".
+  the end of the first 3 rendered lines, and either the core point is
+  understandable without opening "see more" or an intentional open loop creates
+  a specific click question with an immediate planned payoff.
 - `warn`: the mobile rendered preview creates useful curiosity but the core
-  point is slightly softened by wrapping, blank-line rhythm, or one missing
-  context word. A compact fallback is required.
+  point or click question is slightly softened by wrapping, blank-line rhythm,
+  or one missing context word. A compact fallback is required.
 - `fail`: the hook's real point appears after the first 3 mobile rendered
-  lines, the first rendered line is generic setup, blank lines consume the
-  preview before the reader sees the point, or desktop fit is the only reason it
-  looks good.
+  lines without an intentional open-loop plan, the visible open loop is vague,
+  the first rendered line is generic setup, blank lines consume the preview
+  before the reader sees the point, or desktop fit is the only reason it looks
+  good.
 
 Desktop preview usually has more room. Still record `desktopPreviewFit`, but
 never let desktop fit compensate for a mobile `fail`.
 
 If a hook's point depends on text after the rendered mobile preview clamp,
-rewrite it before selecting it. A selected hook may carry a `warn` only when
-the warning is explicit and the validation receipt includes a compact fallback.
-A hook with no rendered mobile and desktop preview record cannot be selected.
+rewrite it before selecting it unless the hook is intentionally using a
+see-more open loop. Intentional open loops must show a specific click question
+inside the mobile clamp and must define the first payoff line after the fold. A
+selected hook may carry a `warn` only when the warning is explicit and the
+validation receipt includes a compact fallback. A hook with no rendered mobile
+and desktop preview record cannot be selected.
 
 ## Step 3: Draft
 
@@ -594,6 +639,9 @@ Every saved draft needs a validation receipt with:
 - selected premise card
 - candidate hooks considered
 - selected hook and why
+- hook reverse-engineering audit
+- hook angle matrix summary
+- see-more click audit
 - proof claims used and source
 - story/proof files consulted
 - gold standards consulted

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

@@ -55,7 +55,9 @@ Research packet:
 - market belief map: max 8 bullets
 - controversy candidates: max 8
 - premise inputs: max 8
+- hook reverse-engineering autopsies: max 12
 - full adapted hook blocks: max 12
+- angle territories tested: max 12
 - exact phrase patterns: max 20
 - body patterns: max 8
 - source URLs and author profile URLs
@@ -261,6 +263,104 @@ Penalize lead-magnet and engagement-bait mechanics unless the user explicitly as
 - "like and comment"
 - broad giveaway framing that makes engagement inflate without proving the hook/body worked
 
+## Hook Reverse Engineering Autopsy
+
+For any space or LinkedIn topic, do not stop at "this is a good hook." Reverse
+engineer why the opening earned attention, which shape can be reused, and which
+parts belong to the source and must not be copied.
+
+For each keeper source hook, record a `hookAutopsy`:
+
+```text
+hookAutopsy:
+  sourceHook: <exact visible opening used for analysis>
+  renderedFirstScreen: <mobile and desktop visible blocks>
+  sourceMechanism: <what the hook does structurally>
+  openLoopType: none | hidden_payoff | contradiction | proof_gap | workflow_reveal | asset_reveal | story_gap
+  clickQuestion: <the question a reader has before clicking see more>
+  promisedPayoff: <what the body/video must deliver after the click>
+  curiosityGap: <what is withheld and why that is fair>
+  specificityAnchor: <tool, person, number, object, scene, or enemy named>
+  tensionOpened: <belief, resentment, fear, status, cost, or contradiction>
+  proofImplied: <what proof the source suggests in the first screen>
+  whyItWorks: <specific words and structure, not a vibe label>
+  whyItMightBeInflated: <reach, giveaway, celebrity, outrage, or topic heat>
+  sourceShapeToKeep: <portable structure, written as a template>
+  sourceWordsNotToCopy: <phrases, jokes, proof, or context owned by source>
+  adaptationRule: <how to make it true for the user's idea and voice>
+```
+
+Good `sourceShapeToKeep` examples:
+
+- "The best [desired asset] I have right now is not in [default tool]."
+- "I gave [system/person] one prompt: [specific request]."
+- "[Common vanity metric] is useless until it becomes [business outcome]."
+- "I built [familiar workflow] inside [new interface]."
+- "Most teams [surface behavior]. Then they miss [hidden opportunity]."
+
+Bad autopsies:
+
+- "contrarian hook"
+- "strong curiosity"
+- "good storytelling"
+- "viral format"
+
+Those labels are allowed only after the concrete shape, click question, and
+payoff obligation are recorded.
+
+## Angle Exploration Before Drafting
+
+After selecting a premise, create a hook angle matrix before drafting the post.
+This is mandatory when the user asks to nail the hook, study hooks, explore a
+space, or write from a specific idea.
+
+Default matrix:
+
+- at least 8 angle territories for normal drafting
+- at least 12 angle territories when the user asks for "a ton of angles" or
+  says the hook is the main constraint
+- at least 24 generated hooks across those territories for normal drafting
+- at least 40 generated hooks when the user explicitly asks to optimize hooks
+
+Angle territories should be materially different, not synonyms. Use territories
+such as:
+
+- enemy/tool contrast
+- hidden asset
+- first-person build proof
+- workflow reveal
+- contrarian category claim
+- mistake/confession
+- market timing
+- customer/operator pain
+- asset/free reveal without comment bait
+- specific person/company signal
+- before/after transformation
+- question hook
+
+For each territory, record:
+
+```text
+angleTerritory:
+  name:
+  sourceShapesUsed:
+  premiseTensionOpened:
+  readerValueImplied:
+  bestHook:
+  mobileRenderedPreview:
+  desktopRenderedPreview:
+  clickQuestion:
+  payoffAfterFold:
+  whyThisAngleShouldWin:
+  whyThisAngleShouldLose:
+  proofNeeded:
+```
+
+Do not write the post body until the winning hook territory is chosen. The post
+body must then pay off the selected hook quickly. If the best hook says the list
+is not in Apollo, the next lines must reveal where it is. If the hook says "I
+gave Sellable one prompt," the next lines must show the prompt or the demo.
+
 ## Market Belief Map
 
 Before selecting a hook or writing a draft, synthesize a market belief map from
@@ -382,6 +482,12 @@ For each source, record:
 - `corePainProofOrCuriosityVisibleDesktop`
 - `corePointVisibleMobile`
 - `corePointVisibleDesktop`
+- `intentionalOpenLoop`
+- `specificClickQuestionVisible`
+- `payoffPlannedImmediatelyAfterClamp`
+- `seeMoreClickReason`
+- `clickQuestion`
+- `payoffAfterFold`
 - `pointAfterMobileClamp`
 - `charCountIncludingNewlines`
 - `physicalLineCount`
@@ -395,6 +501,7 @@ For each source, record:
 - `desktopPreviewBudget`: `pass`, `warn`, or `fail`
 - `blankLineVisualRisk`
 - `corePointBeforeLikelyTruncation`
+- `openLoopType`
 - `renderedPreviewVerdict`: `pass`, `warn`, or `fail`
 
 If only a search preview is available, do not pretend the opening is complete.
@@ -404,15 +511,17 @@ appears cut off or body context is unavailable.
 Pass/warn/fail is based on rendered output:
 
 - `pass`: the mobile rendered preview shows the pain, proof, or curiosity by
-  the end of the first 3 rendered lines, and the core point is understandable
-  without opening "see more".
+  the end of the first 3 rendered lines, and either the core point is
+  understandable without opening "see more" or an intentional open loop creates
+  a specific click question with an immediate planned payoff.
 - `warn`: the mobile rendered preview creates useful curiosity but the core
-  point is slightly softened by wrapping, blank-line rhythm, or one missing
-  context word. A compact fallback is required.
+  point or click question is slightly softened by wrapping, blank-line rhythm,
+  or one missing context word. A compact fallback is required.
 - `fail`: the hook's real point appears after the first 3 mobile rendered
-  lines, the first rendered line is generic setup, blank lines consume the
-  preview before the reader sees the point, or desktop fit is the only reason it
-  looks good.
+  lines without an intentional open-loop plan, the visible open loop is vague,
+  the first rendered line is generic setup, blank lines consume the preview
+  before the reader sees the point, or desktop fit is the only reason it looks
+  good.
 
 ## Hook Extraction
 

package/skills/create-post/references/linkedin-preview-rendering.md

@@ -63,6 +63,10 @@ renderedPreview:
     blankLinesBeforeClamp: <number>
     corePainProofOrCuriosityVisible: true | false
     corePointVisible: true | false
+    intentionalOpenLoop: true | false
+    specificClickQuestionVisible: true | false
+    payoffPlannedImmediatelyAfterClamp: true | false
+    seeMoreClickReason: <why a reader would click see more>
     seeMoreRisk: pass | warn | fail
     screenshotPath: <optional local path>
   desktop:
@@ -88,6 +92,7 @@ renderedPreview:
     longestNonblankLineChars: <number>
     blankLineVisualRisk: none | low | medium | high
     pointAfterMobileClamp: true | false
+    openLoopType: none | hidden_payoff | contradiction | proof_gap | workflow_reveal | asset_reveal | story_gap
     rewriteIfTruncated: <short fallback>
 ```
 
@@ -112,31 +117,39 @@ For generated hooks:
 
 - Generate the hook from the selected premise first.
 - Render the hook for mobile and desktop before scoring it.
-- Score the rendered first-screen promise before scoring cleverness.
-- Rewrite any candidate whose real point appears after the mobile clamp.
+- Score the rendered first-screen click reason before scoring cleverness.
+- If the goal is see-more clicks, the hook may intentionally hide the payoff
+  after the mobile clamp, but the visible block must create a specific question
+  the target reader wants answered.
+- Rewrite any candidate whose real point appears after the mobile clamp unless
+  that point is the planned payoff for an intentional open loop.
 
 ## Pass, Warn, Fail
 
 Use these rendered gates:
 
 - `pass`: the mobile rendered preview shows the pain, proof, or curiosity by the
-  end of the first 3 rendered lines, and the core point is understandable
-  without opening "see more".
+  end of the first 3 rendered lines, and either the core point is
+  understandable without opening "see more" or an intentional open loop creates
+  a specific click question with an immediate planned payoff.
 - `warn`: the mobile rendered preview creates useful curiosity but the core
-  point is slightly softened by wrapping, blank-line rhythm, or one missing
-  context word. A compact fallback is required.
+  point or click question is slightly softened by wrapping, blank-line rhythm,
+  or one missing context word. A compact fallback is required.
 - `fail`: the hook's real point appears after the first 3 mobile rendered lines,
-  the first rendered line is generic setup, blank lines consume the preview
-  before the reader sees the point, or desktop fit is the only reason it looks
-  good.
+  the visible open loop is vague, the first rendered line is generic setup,
+  blank lines consume the preview before the reader sees the point, or desktop
+  fit is the only reason it looks good.
 
 A draft cannot be `ready` when the selected hook has:
 
 - no `renderedPreview`
 - `mobile.seeMoreRisk: fail`
 - `mobile.corePainProofOrCuriosityVisible: false`
-- `mobile.corePointVisible: false`
-- `pointAfterMobileClamp: true`
+- `mobile.corePointVisible: false` unless `mobile.intentionalOpenLoop: true`,
+  `mobile.specificClickQuestionVisible: true`, and
+  `mobile.payoffPlannedImmediatelyAfterClamp: true`
+- `pointAfterMobileClamp: true` unless the point after the clamp is the
+  intentional payoff for a specific open loop
 
 ## Report Format
 

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

@@ -72,6 +72,12 @@ Hook research files must preserve:
   including literal mobile/desktop preview blocks, rendered line wraps, render
   basis, CSS contract version, text widths, first-screen promise visibility,
   core point visibility, and whether the point lands after the mobile clamp
+- hook reverse-engineering autopsies for kept source hooks, including source
+  mechanism, open-loop type, click question, promised payoff, specificity
+  anchor, source shape to keep, source words not to copy, and adaptation rule
+- hook angle matrix summary, including angle territories tested, top generated
+  hooks, winning territory, runner-up territories, and why the winning angle
+  beat the alternatives
 - extracted hook patterns
 - selected hook basis
 
@@ -92,6 +98,9 @@ Draft files must preserve:
 - draft body
 - validation receipt, including LinkedIn preview pass/warn/fail status and
   compact fallback when the selected hook carries a warning
+- selected hook reverse-engineering audit, hook angle matrix summary, and
+  see-more click audit when the selected hook intentionally hides the payoff
+  after the mobile fold
 - rendered mobile and desktop preview blocks for the selected hook; drafts
   cannot be ready when this rendered-preview audit is missing or fails mobile
   visibility

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

@@ -12,6 +12,9 @@ Every saved draft needs a validation receipt. A draft without this receipt is no
 - `selectedHook`
 - `selectedHookWhy`
 - `sourceHookReachAudit`
+- `hookReverseEngineeringAudit`
+- `hookAngleMatrix`
+- `seeMoreClickAudit`
 - `proofClaimsUsed`
 - `proofClaimSources`
 - `storyFilesConsulted`
@@ -69,15 +72,29 @@ set the verdict to `revise` or `reject`.
 
 ## Candidate Set
 
-Generate multiple hook candidates before drafting. Do not lock onto the first draft.
+Generate many hook candidates before drafting. Do not lock onto the first draft.
+
+Minimum candidate set:
+
+- normal drafting: at least 8 angle territories and 24 hook candidates
+- hook-critical requests: at least 12 angle territories and 40 hook candidates
+- smaller set only when the user explicitly asks for fewer options
+
+An angle territory is a distinct reason the reader might care, such as hidden
+asset, tool/enemy contrast, first-person build proof, workflow reveal,
+contrarian category claim, mistake/confession, market timing, operator pain,
+specific person/company signal, before/after transformation, or question hook.
 
 Each candidate should include:
 
 - hook text
 - selected premise
+- angle territory
 - premise tension opened
 - reader value implied
 - source pattern
+- source shape kept
+- source words not copied
 - source pattern reach signals: author follower count when available, target
   follower band, follower-band fit, engagement per 1k followers, weighted
   engagement per 1k followers, reach-adjusted score, baseline lift, and
@@ -87,6 +104,12 @@ Each candidate should include:
 - literal mobile and desktop rendered preview blocks
 - mobile and desktop rendered line wraps
 - first-screen promise: pain, proof, or curiosity visible by the mobile clamp
+- `intentionalOpenLoop`
+- `specificClickQuestionVisible`
+- `seeMoreClickReason`
+- `clickQuestion`
+- `payoffAfterFold`
+- `bodyProofObligation`
 - whether the core point is visible in the mobile rendered preview
 - whether the point lands after the mobile clamp
 - char count including newlines and first-line / first-two-line preview measurements
@@ -97,6 +120,55 @@ Each candidate should include:
 - AI-tell risk
 - why it should win or lose
 
+## Hook Reverse Engineering Audit
+
+Before a draft can be `ready`, validate that the selected hook came from a real
+source-shape analysis, not from generic brainstorming.
+
+Record:
+
+- `sourceHooksStudied`
+- `sourceHookAutopsies`
+- `selectedSourceShape`
+- `sourceShapeKept`
+- `sourceWordsNotCopied`
+- `whyItWorks`
+- `openLoopType`: `none`, `hidden_payoff`, `contradiction`, `proof_gap`,
+  `workflow_reveal`, `asset_reveal`, or `story_gap`
+- `clickQuestion`
+- `promisedPayoff`
+- `specificityAnchor`
+- `tensionOpened`
+- `proofImplied`
+- `adaptationRule`
+- `bodyPayoffObligation`
+
+The selected draft cannot be `ready` if the hook was copied verbatim from
+another creator, if the receipt only says "contrarian" or "curiosity" without
+the concrete shape, or if the body does not pay off the hook quickly.
+
+## Hook Angle Matrix Audit
+
+Before a draft can be `ready`, validate that the hook was chosen after exploring
+materially different angles.
+
+Record:
+
+- `angleTerritoriesTested`
+- `hookCandidatesGenerated`
+- `winningTerritory`
+- `runnerUpTerritories`
+- `whyWinningAngleBeatsAlternatives`
+- `whyRejectedHooksLost`
+- `mobileRenderedPreviewBlocksForTopCandidates`
+- `desktopRenderedPreviewBlocksForTopCandidates`
+- `proofNeededByWinningAngle`
+
+If the user asked to "nail the hook," "focus on hooks," or explore "a ton of
+angles," the draft cannot be `ready` unless at least 12 territories and 40 hook
+candidates were considered or the receipt explains why the user explicitly
+requested fewer.
+
 ## Finalizer Pass
 
 After the first draft:
@@ -216,15 +288,17 @@ review clamp: first 3 rendered text lines
 Use rendered gates:
 
 - `pass`: the mobile rendered preview shows the pain, proof, or curiosity by
-  the end of the first 3 rendered lines, and the core point is understandable
-  without opening "see more".
+  the end of the first 3 rendered lines, and either the core point is
+  understandable without opening "see more" or an intentional open loop creates
+  a specific click question with an immediate planned payoff.
 - `warn`: the mobile rendered preview creates useful curiosity but the core
-  point is slightly softened by wrapping, blank-line rhythm, or one missing
-  context word. A compact fallback is required.
+  point or click question is slightly softened by wrapping, blank-line rhythm,
+  or one missing context word. A compact fallback is required.
 - `fail`: the hook's real point appears after the first 3 mobile rendered
-  lines, the first rendered line is generic setup, blank lines consume the
-  preview before the reader sees the point, or desktop fit is the only reason it
-  looks good.
+  lines without an intentional open-loop plan, the visible open loop is vague,
+  the first rendered line is generic setup, blank lines consume the preview
+  before the reader sees the point, or desktop fit is the only reason it looks
+  good.
 
 Desktop preview usually has more room. Still record desktop fit, but never let
 desktop fit compensate for a mobile `fail`.
@@ -247,6 +321,12 @@ Record:
 - `corePainProofOrCuriosityVisibleDesktop`
 - `corePointVisibleMobile`
 - `corePointVisibleDesktop`
+- `intentionalOpenLoop`
+- `specificClickQuestionVisible`
+- `payoffPlannedImmediatelyAfterClamp`
+- `seeMoreClickReason`
+- `clickQuestion`
+- `payoffAfterFold`
 - `pointAfterMobileClamp`
 - `charCount`
 - `charCountIncludingNewlines`
@@ -270,10 +350,33 @@ If the hook only works after the rendered mobile clamp, rewrite it. A draft
 cannot be `ready` with `previewBudgetStatus: fail`,
 `mobilePreviewFit: fail`, missing `renderedPreview`,
 `corePainProofOrCuriosityVisibleMobile: false`,
-`corePointVisibleMobile: false`, or `pointAfterMobileClamp: true`. A draft may
-be `ready` with `previewBudgetStatus: warn` only when the warning is explicit,
-usually because the user prefers blank-line rhythm, and the receipt includes a
-compact fallback.
+`corePointVisibleMobile: false` unless the receipt has
+`intentionalOpenLoop: true`, `specificClickQuestionVisible: true`, and
+`payoffPlannedImmediatelyAfterClamp: true`, or `pointAfterMobileClamp: true`
+unless the post is intentionally hiding the payoff for a specific see-more
+click. A draft may be `ready` with `previewBudgetStatus: warn` only when the
+warning is explicit, usually because the user prefers blank-line rhythm, and
+the receipt includes a compact fallback.
+
+## See-More Click Audit
+
+When the selected hook intentionally hides the payoff after the mobile fold,
+record:
+
+- `intentionalOpenLoop: true`
+- `openLoopType`
+- `visibleBeforeFold`
+- `clickQuestion`
+- `payoffAfterFold`
+- `firstPayoffLine`
+- `payoffArrivesWithinFirstBodySection`
+- `readerValueAfterClick`
+- `baitRisk`
+- `baitRiskMitigation`
+
+Open loops are allowed only when the body actually delivers the promised payoff.
+If the hook withholds the answer but the body switches topics, save as
+`needs_revision`.
 
 ## Simplifier / Concrete-Language Audit