# Signal Scout — Framework Logic Engine
# Last updated: 2026-06-11
# Purpose: Supporting logic for each of the 14 content frameworks.
# How to use: When content is ingested or inputted, summarize it, extract the core signal,
# then apply the framework logic below to structure the output with precision.

---

## HOW TO APPLY A FRAMEWORK

### Step 1 — Summarize the input
Extract:
- **Core claim** — the single most important assertion or finding
- **Evidence** — data, quotes, examples, trends that support it
- **Stakes** — who it affects, why it matters, what changes
- **Timeframe** — is this urgent/timely or evergreen?
- **Audience** — practitioner, executive, general, skeptic?

### Step 2 — Match signal to framework
Use the Best For / Trigger Conditions columns below. The framework is determined by:
- What the content IS (data-heavy, story, argument, how-to)
- What the audience NEEDS (to understand, to act, to be challenged)
- What the output FORMAT requires (60s video vs. white paper vs. tweet)

### Step 3 — Slot content into framework structure
Each framework below defines its slots. Fill them with extracted content — do not invent or embellish. If a slot can't be filled from the source, flag it rather than fabricate.

---

## THE 14 FRAMEWORKS

---

### 1. SPARK
**Structure:** Signal → Position → Argument → Reinforcement → Kicker
**Primary use:** Most versatile. Default framework when none others dominate.

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Signal** | The triggering event, data point, or observation | Lead with the most concrete, specific fact from the input |
| **Position** | Your stake in the ground — what you believe this means | Derive from the implied or explicit thesis of the source |
| **Argument** | The logical chain that supports the position | Pull the 2-3 strongest evidence threads; order by impact |
| **Reinforcement** | A second layer — analogy, case study, contrasting example | Find supporting context or a parallel from the source |
| **Kicker** | The sting — a memorable closer, call to action, or provocative question | Compress the stakes into one line; leave audience with a thought |

**Best For:** LinkedIn posts, 60–90s video, talk tracks, thought leadership
**Trigger Conditions:** Any signal with a clear implication, strong data point, or trend with an opinion attached
**Anti-patterns:** Don't use Signal to editorialize — Signal must be factual. Don't use Kicker to restate the Position.

---

### 2. PAS
**Structure:** Problem → Agitation → Solution
**Primary use:** Short-form hooks, awareness content, top-of-funnel

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Problem** | The pain state the audience is in right now | Extract the friction, inefficiency, or risk described in the input |
| **Agitation** | Make the problem feel urgent and real — consequences, compounding effects | Find the downstream impact or "what happens if you ignore this" in the source |
| **Solution** | The resolution — product, principle, behavior, or shift | Pull the remedy, recommendation, or alternative the content points to |

**Best For:** Short-form hooks (LinkedIn, Twitter/X), email subject lines, cold outreach openers
**Trigger Conditions:** Content that surfaces a known pain point or common mistake; works best when problem is already recognized by audience
**Anti-patterns:** Avoid manufactured agitation — it must be grounded in real consequences from the source. Don't skip to Solution too fast.

---

### 3. BAB
**Structure:** Before → After → Bridge
**Primary use:** Case studies, transformation narratives, proof-based content

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Before** | The prior state — struggling, uncertain, inefficient | Extract the starting condition, baseline, or problem state from the input |
| **After** | The transformed state — outcome, result, capability | Extract the end result, metric, or improvement described |
| **Bridge** | The mechanism — what caused the transformation | Extract the method, tool, decision, or process that created the change |

**Best For:** Case study videos, testimonials, ROI narratives, sales enablement content
**Trigger Conditions:** Content with a measurable before/after, a success story, or a clear intervention with outcome
**Anti-patterns:** Don't use when there's no clear outcome. Bridge must be specific — not "better approach" but the actual thing they did.

---

### 4. StoryBrand
**Structure:** Guide → Problem → Plan → Action → Success/Failure Stakes
**Primary use:** Explainer content, landing pages, brand narratives

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Guide** | Establish authority/credibility — who is leading the audience | Extract the speaker/brand positioning signals from the source |
| **Problem** | The villain — external problem (circumstance) + internal problem (emotion) | Surface both the practical AND emotional pain from the input |
| **Plan** | Clear, simple steps — demystify the path forward | Extract the 3-step or phased approach from the source |
| **Action** | A direct, unambiguous call to do something | Identify the recommended first move |
| **Success/Failure** | What winning looks like vs. what staying stuck costs | Extract explicit outcome framing from the source |

**Best For:** Product explainers, website copy, brand narrative videos, onboarding content
**Trigger Conditions:** Content that positions a company, product, or method as the solution; works when there's a clear protagonist (customer) and antagonist (problem)
**Anti-patterns:** Don't make the brand the hero — the customer is the hero. Guide enables, not rescues.

---

### 5. AIDA
**Structure:** Attention → Interest → Desire → Action
**Primary use:** Ad scripts, email campaigns, conversion content

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Attention** | Pattern interrupt — stop the scroll | Extract the most surprising, counterintuitive, or bold claim in the source |
| **Interest** | Draw them in — context, relevance, "here's why this matters to you" | Pull the specificity and relevance that makes the claim real to this audience |
| **Desire** | Make them want the outcome | Extract the aspirational state, the benefit, the transformation |
| **Action** | Tell them exactly what to do next | Identify the single CTA — download, book, apply, share |

**Best For:** Ad scripts, email sequences, landing page copy, video ads
**Trigger Conditions:** Content with a clear conversion goal; audience may be cold or unaware
**Anti-patterns:** Don't front-load too much context before Attention lands. Action must be singular — one CTA only.

---

### 6. Data-Driven
**Structure:** Stat → Context → Implication → Action
**Primary use:** White papers, research summaries, analyst-style content

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Stat** | The anchor data point — specific, sourced, surprising | Extract the most concrete number, percentage, or finding from the input |
| **Context** | Why this stat matters — what's the landscape, what's the baseline | Pull the surrounding conditions that make the stat meaningful |
| **Implication** | What this means for the industry, role, or decision | Derive the logical consequence of the stat given the context |
| **Action** | What a rational actor should do with this information | Extract or infer the recommended response |

**Best For:** White papers, data-backed LinkedIn posts, research reports, exec briefings
**Trigger Conditions:** Content with verifiable data points, study findings, survey results, or industry benchmarks
**Anti-patterns:** Never use unverifiable stats as anchors. Implication must be derived, not asserted. Source the Stat slot.

---

### 7. Hot Take
**Structure:** Contrarian → Evidence → CTA
**Primary use:** Viral posts, opinion pieces, high-engagement short-form

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Contrarian** | The belief most people hold — then flip it | Identify the conventional wisdom or default assumption the source challenges |
| **Evidence** | Why the contrarian view is actually correct | Pull the data, case, or logic that supports the unpopular position |
| **CTA** | Provoke a reaction — agree, disagree, share, argue | End with a challenge or question that invites response |

**Best For:** Twitter/X posts, LinkedIn provocations, podcast clips, attention hooks
**Trigger Conditions:** Content that contradicts a widely-held belief, challenges a default, or surfaces a non-obvious insight
**Anti-patterns:** Contrarian must be defensible — not clickbait. Evidence must be real. Don't manufacture controversy.

---

### 8. Story Arc
**Structure:** Hook → Tension → Resolution → Lesson
**Primary use:** Podcasts, keynotes, long-form video, narrative storytelling

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Hook** | Open with a moment that creates immediate engagement | Find the most dramatic, surprising, or relatable moment in the source |
| **Tension** | The conflict, uncertainty, or challenge — what's at stake | Extract the core obstacle, dilemma, or risk the story orbits around |
| **Resolution** | How it ended — the turn, the breakthrough, the answer | Pull the outcome, decision, or shift that resolved the tension |
| **Lesson** | What the audience should carry with them | Derive the transferable insight — the "so what" the story earns |

**Best For:** Podcast episodes, keynote openings, long-form LinkedIn articles, brand documentary content
**Trigger Conditions:** Content with a narrative arc, personal experience, historical event, or case with a clear before/after emotional journey
**Anti-patterns:** Hook must earn the story — don't open with the conclusion. Lesson should feel earned, not pasted on.

---

### 9. Listicle
**Structure:** 3–5 Key Points, each with a punchy header + 1-2 line support
**Primary use:** Carousels, skimmable content, quick-read formats

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Intro hook** | Frame the list — why these 3-5 things, why now | Extract the unifying theme or urgency from the source |
| **Point 1–5** | Each point = one distinct insight with a punchy label | Extract the most distinct, actionable, or surprising sub-claims from the input |
| **Closer** | Tie it back — what the list adds up to | Summarize the cumulative insight or call to action |

**Best For:** LinkedIn carousels, Twitter/X threads, skimmable blog posts, quick-reference video
**Trigger Conditions:** Content with multiple distinct insights, steps, or principles that work as a set
**Anti-patterns:** Don't manufacture 5 points if the source only has 3 strong ones. Each point must stand alone. No filler.

---

### 10. Trend Piece
**Structure:** Signal → Context → Trajectory → Implications
**Primary use:** Thought leadership, industry analysis, forward-looking content

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Signal** | The observable data point or event — the "this is happening now" | Extract the most current, specific, concrete evidence of the trend |
| **Context** | Where this fits — historical pattern, industry backdrop, why it's happening | Pull the conditions that explain why this signal is emerging now |
| **Trajectory** | Where this is going — projection, logical extension, acceleration factors | Derive or extract the direction + velocity of the trend from the source |
| **Implications** | What this means for the audience — risks, opportunities, required shifts | Extract or infer the downstream effects for the target audience |

**Best For:** Thought leadership posts, analyst-style content, executive briefings, year-in-review
**Trigger Conditions:** Content signaling a market shift, behavioral change, technology adoption curve, or macro trend
**Anti-patterns:** Don't state trajectory as certainty — hedge appropriately. Implications must be specific to the audience, not generic.

---

### 11. Case Study
**Structure:** Challenge → Approach → Outcome → Lesson
**Primary use:** Client videos, social proof, sales enablement, ROI documentation

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Challenge** | The specific, credible problem the subject faced | Extract the pain state, constraint, or goal gap from the source |
| **Approach** | What they actually did — specific actions, tools, decisions | Pull the methodology, process, or strategy used |
| **Outcome** | The measurable result — numbers preferred | Extract the specific, quantified outcome where possible |
| **Lesson** | The transferable principle — what others should take from this | Derive the replicable insight from the approach + outcome |

**Best For:** Client case study videos, proposal support, conference presentations, LinkedIn proof posts
**Trigger Conditions:** Content featuring a real implementation with a measurable result and a method that can be transferred
**Anti-patterns:** Outcome must be specific — not "significant improvement." Avoid vague lessons. If outcome isn't quantified in source, note it explicitly.

---

### 12. Comparison
**Structure:** Option A → Option B → Verdict → Why
**Primary use:** Evaluations, buying guides, competitive positioning

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Option A** | First alternative — define it clearly | Extract the first option's definition, use case, strengths from the source |
| **Option B** | Second alternative — define it clearly | Extract the second option's definition, use case, strengths from the source |
| **Verdict** | The recommendation — which wins, under what conditions | Pull or derive the conclusion from the source's evidence |
| **Why** | The reasoning — the criteria that led to the verdict | Extract the evaluative logic, trade-offs, and decision factors |

**Best For:** Product evaluations, build vs. buy decisions, technology comparisons, vendor analysis
**Trigger Conditions:** Content that explicitly or implicitly compares two or more approaches, tools, methodologies, or options
**Anti-patterns:** Verdict must be conditional if both options have legitimate use cases. Don't declare a winner without clear criteria.

---

### 13. Prediction
**Structure:** Current → Forces → Predicted → Prepare
**Primary use:** Year-end content, forward-looking analysis, market forecasting

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Current** | The present state — undeniable, grounded, factual | Extract the most concrete current conditions from the source |
| **Forces** | The drivers pushing toward change — technology, behavior, economics, regulation | Identify and extract the change vectors described or implied |
| **Predicted** | The future state — specific, time-bound where possible | Extract or derive the predicted outcome based on the forces identified |
| **Prepare** | What the audience should do now, before it arrives | Extract or infer the recommended response — hedge, invest, shift, build |

**Best For:** Year-end roundups, industry forecasts, "future of X" content, strategic advisory
**Trigger Conditions:** Content with a clear directional signal, emerging pattern, or forces that logically extend into a future state
**Anti-patterns:** Predicted must be specific — not "things will change." Prepare must be actionable. Don't forecast without anchoring to current evidence.

---

### 14. Explainer
**Structure:** Concept → Analogy → Example → Application
**Primary use:** Tutorials, onboarding, educational content, "explain like I'm smart but new"

| Slot | Definition | Extraction Logic |
|------|-----------|-----------------|
| **Concept** | Define the thing clearly — no jargon | Extract the core definition or principle from the source, strip technical language |
| **Analogy** | Map it to something familiar — bridge the unfamiliar to the known | Find or construct an analogy that fits the concept; use context from the source's examples |
| **Example** | A concrete, real instance of the concept in action | Extract the most vivid, specific example from the source |
| **Application** | How the audience actually uses this — practical, specific, role-relevant | Extract or derive the actionable use of the concept for the target audience |

**Best For:** Tutorial videos, onboarding sequences, educational LinkedIn posts, documentation walkthroughs
**Trigger Conditions:** Content introducing a new concept, process, or technology to an audience that's unfamiliar or skeptical
**Anti-patterns:** Don't skip Analogy — it's the comprehension bridge. Application must be specific to the audience's context, not generic.

---

---

## PLATFORM & FORMAT STRUCTURING MATRIX

Use this table to recommend the right framework given a target platform or output format.
Ratings: ✅ Optimal · 🟡 Works with adjustments · ❌ Poor fit

| Framework | LinkedIn Post | LinkedIn Article | Twitter/X Thread | Instagram (caption/reel) | Short-Form Video (≤60s) | Long-Form Video (2–10min) | Podcast | Keynote/Talk | Email | White Paper/Report |
|-----------|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
| **SPARK** | ✅ | ✅ | 🟡 | 🟡 | ✅ | ✅ | 🟡 | ✅ | 🟡 | ❌ |
| **PAS** | ✅ | 🟡 | ✅ | ✅ | ✅ | ❌ | 🟡 | 🟡 | ✅ | ❌ |
| **BAB** | ✅ | ✅ | 🟡 | 🟡 | 🟡 | ✅ | 🟡 | ✅ | ✅ | 🟡 |
| **StoryBrand** | 🟡 | ✅ | ❌ | 🟡 | 🟡 | ✅ | ✅ | ✅ | 🟡 | 🟡 |
| **AIDA** | 🟡 | ❌ | 🟡 | ✅ | ✅ | 🟡 | ❌ | 🟡 | ✅ | ❌ |
| **Data-Driven** | 🟡 | ✅ | 🟡 | ❌ | 🟡 | ✅ | ✅ | ✅ | 🟡 | ✅ |
| **Hot Take** | ✅ | 🟡 | ✅ | ✅ | ✅ | ❌ | 🟡 | 🟡 | 🟡 | ❌ |
| **Story Arc** | 🟡 | ✅ | 🟡 | 🟡 | ❌ | ✅ | ✅ | ✅ | ❌ | 🟡 |
| **Listicle** | ✅ | 🟡 | ✅ | ✅ | ✅ | 🟡 | 🟡 | 🟡 | ✅ | 🟡 |
| **Trend Piece** | ✅ | ✅ | 🟡 | ❌ | 🟡 | ✅ | ✅ | ✅ | 🟡 | ✅ |
| **Case Study** | ✅ | ✅ | ❌ | 🟡 | 🟡 | ✅ | ✅ | ✅ | ✅ | ✅ |
| **Comparison** | ✅ | ✅ | 🟡 | ❌ | 🟡 | ✅ | ✅ | 🟡 | 🟡 | ✅ |
| **Prediction** | ✅ | ✅ | 🟡 | ❌ | 🟡 | ✅ | ✅ | ✅ | 🟡 | ✅ |
| **Explainer** | 🟡 | ✅ | 🟡 | ✅ | ✅ | ✅ | ✅ | ✅ | 🟡 | ✅ |

---

## PLATFORM-FIRST STRUCTURING GUIDANCE

If the user selects a platform FIRST and wants a framework recommended:

### Instagram (Feed Post / Reel / Story)
- **Content type:** Visual-first. Hook must land in 0–2 seconds. Copy is secondary.
- **Best frameworks:** PAS, Hot Take, AIDA, Listicle, Explainer
- **Avoid:** Story Arc (too long), Data-Driven (too abstract without visual), Prediction (no payoff in short window)
- **Format notes:** Caption = max 3 lines visible before fold. Reel = hook in first 3s, resolution by 30s. Carousel = Listicle maps 1:1.

### Short-Form Video (TikTok / Instagram Reels / YouTube Shorts ≤60s)
- **Content type:** Fast hook, one idea, strong close. No room for nuance.
- **Best frameworks:** PAS, Hot Take, SPARK (condensed), AIDA, Listicle, Explainer
- **Avoid:** Story Arc, StoryBrand, Data-Driven, Prediction, Comparison (all require setup time)
- **Format notes:** Hook = first 3s must state the premise. One slot per ~10s. End with CTA or rewatch hook.

### Long-Form Video (YouTube / Wistia / Conference Recording 2–10min)
- **Content type:** Earned attention. Can build context. Allows structure to breathe.
- **Best frameworks:** SPARK, BAB, StoryBrand, Data-Driven, Story Arc, Trend Piece, Case Study, Comparison, Prediction, Explainer
- **Avoid:** PAS (too compressed), Hot Take (needs more than 60s to land safely)
- **Format notes:** Open with Hook (0–30s), deliver value before 2min, close with clear CTA. Beat map recommended.

### LinkedIn Post
- **Content type:** Professional feed scroll. Hook line is everything. Authority matters.
- **Best frameworks:** SPARK, PAS, BAB, Hot Take, Listicle, Trend Piece, Case Study, Comparison, Prediction
- **Avoid:** AIDA (too salesy for organic), Story Arc (too long without video)
- **Format notes:** First line = the hook (no lead-up). Whitespace is engagement. CTA at end. 150–300 words optimal.

### LinkedIn Article / Long-Form Written
- **Content type:** Depth content. Reader opted in. Structure and evidence matter.
- **Best frameworks:** Data-Driven, Trend Piece, Case Study, StoryBrand, Comparison, Prediction, Story Arc, BAB, Explainer
- **Avoid:** PAS (too shallow), AIDA (conversion-focused, wrong intent)
- **Format notes:** H2 subheads every 300 words. Data needs inline citation. End with a single strong CTA.

### Twitter/X Thread
- **Content type:** Sequential micro-posts. Hook tweet is the entry. Each tweet must stand alone.
- **Best frameworks:** PAS, Hot Take, Listicle, SPARK (1 tweet per slot)
- **Avoid:** Story Arc, StoryBrand, Case Study (all require sustained narrative)
- **Format notes:** Tweet 1 = hook + promise. Tweet 2–N = one point each. Last tweet = summary + CTA. Max 8–12 tweets for retention.

### Podcast Episode
- **Content type:** Audio-only. No visuals. Conversational. Listener is multitasking.
- **Best frameworks:** Story Arc, StoryBrand, Data-Driven, Trend Piece, Case Study, Comparison, Prediction, Explainer
- **Avoid:** Listicle (hard to follow aurally), Hot Take (needs visual proof), AIDA (too ad-like)
- **Format notes:** Open with a question or story. Chapter breaks every 5–7min. Close with explicit takeaway + subscribe ask.

### Email
- **Content type:** Subject line = open rate. Body = one idea, one CTA. Relationship-aware.
- **Best frameworks:** PAS, AIDA, BAB, Case Study, SPARK
- **Avoid:** Story Arc (too long), Trend Piece (too abstract without visual), Prediction (low urgency)
- **Format notes:** Subject line = 6–8 words. Preview text = agitation or hook. Body = 100–200 words. One link.

### White Paper / Research Report
- **Content type:** High-trust, long-read. Reader is a decision-maker or analyst. Evidence is king.
- **Best frameworks:** Data-Driven, Trend Piece, Case Study, Comparison, Prediction, Explainer
- **Avoid:** Hot Take, PAS, AIDA, Listicle (all too lightweight for this context)
- **Format notes:** Executive summary first (1 page). Data before argument. Every claim sourced. End with recommendations section.

### Keynote / Talk
- **Content type:** Live audience. Emotional connection matters. Structure must be felt, not read.
- **Best frameworks:** Story Arc, SPARK, StoryBrand, Data-Driven, Trend Piece, Prediction, BAB
- **Avoid:** Comparison (too analytical live), Listicle (forgettable without visual support)
- **Format notes:** Open with a story or bold claim. One idea per 3–5 minutes. Close with a call to belief, not just action.

---

## STYLE MODE MODIFIERS

Apply after framework structure is filled. These adjust tone, not structure.

| Mode | Effect | When to Use |
|------|--------|-------------|
| **Thought Leader** | First-person, opinionated, authoritative. Remove hedges. | Executive or practitioner audience, high-credibility context |
| **Educational** | Clear, patient, no assumed knowledge. Define every term. | New audience, onboarding, tutorial context |
| **Provocative** | Challenge assumptions, use friction, invite debate. | High-engagement goals, viral potential, opinion pieces |
| **Corporate** | Professional, measured, third-person safe. | Regulated industries, formal communications, enterprise accounts |
| **Conversational** | Peer-to-peer, informal, remove formality markers. | Community content, authentic social, podcast-style |

---

## ANTI-PATTERNS — NEVER GENERATE

These are hard blocks regardless of framework or style mode:

| Anti-Pattern | Definition |
|-------------|-----------|
| **Doom Framing** | Leading with catastrophe, worst-case as likely case, fear without resolution |
| **Fear Farming** | Using anxiety to drive engagement without a credible path forward |
| **Generic Hype** | "Game-changing," "revolutionary," "unprecedented" without specific evidence |
| **Unsubstantiated Claims** | Any stat, outcome, or assertion that cannot be traced back to the source material |

---

## EXTRACTION QUALITY CHECKLIST

Before finalizing any structured output, verify:

- [ ] Every slot filled from source — no invented content
- [ ] Anti-patterns absent
- [ ] Style mode applied consistently across all slots
- [ ] Kicker/CTA is singular and actionable
- [ ] Stats are sourced and specific
- [ ] Audience is named or implied (not generic "people")
- [ ] If a slot can't be filled from source — flagged, not fabricated

---

*Source: Signal Scout Dev Spec + memory/signal-scout-full-spec-data.md*