sinapse-ai 1.0.0

package/squad-storytelling/tasks/spontaneous-presentation-skills.md

@@ -0,0 +1,162 @@
+---
+task: "spontaneous-presentation-skills"
+responsavel: "keith-johnstone"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Presentation context (meetings, Q&A, impromptu talks)"
+  - "Speaker profile and comfort level"
+Saida:
+  - "Improv-based presentation skills toolkit with exercises and frameworks"
+Checklist:
+  - "[ ] Core improv techniques adapted for business presentations"
+  - "[ ] Fear and blocking patterns identified with counter-techniques"
+  - "[ ] Practice exercises designed for progressive skill building"
+---
+
+# Task: Spontaneous Presentation Skills
+
+**Task ID:** NARR-044
+**Version:** 1.0.0
+**Command:** `*spontaneous-presentation-skills`
+**Agent:** Keith Johnstone (keith-johnstone)
+**Purpose:** Develop improvisational presentation skills using Johnstone's techniques, enabling speakers to handle Q&A, impromptu talks, and unscripted moments with confidence and authenticity.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `speaker_profile` | Role, experience level, comfort with public speaking | YES |
+| `presentation_contexts` | Where they need to speak (meetings, stage, Q&A, media) | YES |
+| `challenges` | What they struggle with (freezing, rambling, nervousness) | YES |
+| `goals` | What improved skill looks like for them | PREFERRED |
+| `team_or_individual` | Training one person or a group | NO |
+
+## Execution Phases
+
+### Phase 1: Diagnose Blocking Patterns
+
+1. Identify the speaker's primary "blocks" (Johnstone's concept of self-censorship):
+   - **Originality block**: Trying to be clever instead of obvious (kills spontaneity)
+   - **Judgment block**: Fear of saying the wrong thing (causes freezing)
+   - **Status block**: Trying to maintain high status at all times (prevents vulnerability)
+   - **Control block**: Over-preparing to prevent surprises (kills authenticity)
+2. Map the speaker's fear hierarchy — what presentation situations cause the most anxiety?
+3. Identify their "comfort moves" — what they default to when nervous (filler words, rushing, humor deflection)
+4. Assess their natural status tendency — do they default to high or low status?
+
+### Phase 2: Teach Core Improv Techniques for Presentations
+
+1. **"Be Obvious"** — Johnstone's #1 rule: say the first thing that comes to mind, not the clever thing
+   - In presentations: Answer questions directly before elaborating
+   - Exercise: Practice giving one-sentence answers before expanding
+2. **"Yes, And"** — Accept what's given and build on it
+   - In presentations: Acknowledge the question before redirecting
+   - Exercise: Take hostile questions and "Yes, And" them into your message
+3. **"Make Your Partner Look Good"** — Focus on the audience, not yourself
+   - In presentations: Frame answers in terms of audience benefit
+   - Exercise: Reframe every answer to start with "What matters for you is..."
+4. **Status Flexibility** — Move between high and low status intentionally
+   - In presentations: Use low status to connect ("I don't have all the answers")
+   - Use high status to lead ("What I know for certain is...")
+5. **"Fail Cheerfully"** — Treat mistakes as gifts
+   - In presentations: When you stumble, acknowledge it and move on
+   - Exercise: Practice intentionally "forgetting" and recovering
+
+### Phase 3: Build Spontaneous Response Frameworks
+
+1. **The Triangle Response** — For unexpected questions:
+   - Point 1: Acknowledge the question (Yes, And)
+   - Point 2: Share what you know (Be Obvious)
+   - Point 3: Bridge to your message (Make Your Partner Look Good)
+2. **The Story Launch** — For "tell me about..." prompts:
+   - Start with a specific moment, not an abstract answer
+   - Use present tense to create immediacy
+   - End with the insight, not the chronology
+3. **The Redirect** — For questions you cannot answer:
+   - Acknowledge: "That's an important question"
+   - Bridge: "What I can tell you is..."
+   - Offer: "And I'll get you the specific answer by [time]"
+4. **The Emotional Pivot** — For hostile or loaded questions:
+   - Lower status first: "I understand why that concerns you"
+   - Share honestly: "Here's what I believe is true"
+   - Raise status: "And here's what we're doing about it"
+
+### Phase 4: Design Practice Exercises
+
+Progressive difficulty (beginner → advanced):
+1. **Level 1: One-Word Story** — Build a story one word at a time with a partner
+   - Develops: surrendering control, building on offers
+2. **Level 2: Three-Sentence Expert** — Become an "expert" on any random topic for 60 seconds
+   - Develops: confidence in uncertainty, Be Obvious muscle
+3. **Level 3: Status Switch** — Present the same content in high and low status
+   - Develops: range, intentional status use
+4. **Level 4: Hostile Q&A** — Field deliberately difficult questions
+   - Develops: composure, redirect skills, emotional management
+5. **Level 5: The Blank Stage** — Walk up with no topic and present for 2 minutes
+   - Develops: trust in spontaneity, elimination of blocking
+
+### Phase 5: Create the Personal Toolkit
+
+1. Build a "pocket story" library — 5 stories the speaker can reach for in any situation
+2. Create a "first sentence" library — 10 opening lines for different situations
+3. Design a pre-presentation warm-up routine (2 minutes of improv exercises)
+4. Create a "recovery phrases" cheat sheet for when things go wrong
+5. Design a 30-day practice plan with daily 5-minute exercises
+6. Set up accountability: weekly practice partner or group session
+
+## Output Format
+
+```yaml
+spontaneous_presentation_toolkit:
+  speaker: "{profile}"
+  blocking_patterns:
+    primary: "{main block}"
+    secondary: "{secondary block}"
+    comfort_moves: ["{default behaviors}"]
+    status_tendency: "{high/low}"
+  techniques:
+    - technique: "{name}"
+      principle: "{Johnstone's principle}"
+      application: "{how to use in presentations}"
+      exercise: "{practice activity}"
+  response_frameworks:
+    triangle: "{acknowledge + know + bridge}"
+    story_launch: "{moment + present tense + insight}"
+    redirect: "{acknowledge + bridge + offer}"
+    emotional_pivot: "{lower + share + raise}"
+  practice_exercises:
+    - level: "{1-5}"
+      name: "{exercise name}"
+      description: "{how to do it}"
+      develops: "{which skill}"
+      duration: "{time}"
+  personal_toolkit:
+    pocket_stories: ["{5 go-to stories}"]
+    first_sentences: ["{10 opening lines}"]
+    warm_up_routine: "{2-minute pre-presentation ritual}"
+    recovery_phrases: ["{when things go wrong}"]
+  thirty_day_plan:
+    - week: 1
+      focus: "{which skill}"
+      daily_exercise: "{5-minute activity}"
+```
+
+## Veto Conditions
+
+- **NEVER** tell a speaker to "just relax" — provide specific techniques instead
+- **NEVER** encourage memorization — it is the enemy of spontaneity
+- **NEVER** skip the progressive difficulty — jumping to Level 5 creates trauma, not skill
+- **NEVER** ignore status dynamics — most presentation anxiety is actually status anxiety
+
+## Completion Criteria
+
+- [ ] Blocking patterns diagnosed with specific counter-techniques
+- [ ] Core improv techniques adapted for business presentation contexts
+- [ ] Response frameworks created for common spontaneous situations
+- [ ] Progressive practice exercises designed (5 levels)
+- [ ] Personal toolkit built (stories, openers, recovery phrases)
+- [ ] 30-day practice plan created with daily exercises

package/squad-storytelling/tasks/status-dynamics-negotiation.md

@@ -0,0 +1,149 @@
+---
+task: "status-dynamics-negotiation"
+responsavel: "keith-johnstone"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Negotiation context and parties involved"
+  - "Desired outcome and relationship dynamics"
+Saida:
+  - "Negotiation strategy using status theory with status plays mapped to key moments"
+Checklist:
+  - "[ ] Status dynamics mapped for all parties"
+  - "[ ] Status play sequence designed for each negotiation phase"
+  - "[ ] Flexibility plan for adapting when status shifts unexpectedly"
+---
+
+# Task: Status Dynamics for Negotiation
+
+**Task ID:** NARR-043
+**Version:** 1.0.0
+**Command:** `*status-dynamics-negotiation`
+**Agent:** Keith Johnstone (keith-johnstone)
+**Purpose:** Apply Johnstone's status theory to negotiation strategy, designing intentional status plays that build rapport, establish credibility, and drive desired outcomes.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `negotiation_context` | What is being negotiated | YES |
+| `parties` | Who is involved, their roles, and power dynamics | YES |
+| `desired_outcome` | What you want to achieve | YES |
+| `relationship_goal` | Short-term deal vs long-term partnership | YES |
+| `known_dynamics` | Any existing relationship history | PREFERRED |
+| `cultural_context` | Cultural norms that affect status | NO |
+
+## Execution Phases
+
+### Phase 1: Map Status Dynamics
+
+1. Rate each party's "natural" status in this context (1-10):
+   - Positional status: Title, role, organizational authority
+   - Expertise status: Knowledge, experience, credentials
+   - Resource status: Money, time, alternatives (BATNA)
+   - Social status: Network, reputation, relationships
+2. Identify status gaps — where is the asymmetry?
+3. Map default status behaviors each party likely displays:
+   - High-status signals: Still body, direct eye contact, slow speech, taking space
+   - Low-status signals: Fidgeting, looking away, rapid speech, apologizing
+4. Identify status traps — situations that could force you into unwanted low status
+
+### Phase 2: Design Status Strategy
+
+1. Determine optimal status position for each phase:
+   - **Opening**: Slightly lower status than the other party (creates rapport through deference)
+   - **Building**: Gradual status rise through demonstrated expertise
+   - **Proposing**: Peer-level status (equal footing for fair deal)
+   - **Closing**: Slightly higher status (confidence in the outcome)
+2. Design status "see-saws" — intentional moments where you raise or lower your status
+3. Plan "status gifts" — moments where you intentionally raise the OTHER party's status
+   - Complimenting their expertise, acknowledging their position, asking for their opinion
+4. Plan "status claims" — moments where you establish your own value
+   - Sharing a relevant credential, making a confident statement, taking a firm position
+
+### Phase 3: Design Status Plays for Key Moments
+
+1. **The Opening:** Lower status slightly — "I'm grateful for your time" (builds goodwill)
+2. **The Expertise Drop:** Raise status naturally — share an insight that reframes the discussion
+3. **The Empathy Play:** Lower status intentionally — "I could be wrong, but..." (disarming)
+4. **The Anchor:** High-status move — make the first offer with confidence and silence
+5. **The Concession:** Status gift — "That's a fair point" (acknowledges their status without losing yours)
+6. **The Close:** Peer status — "I think we've found something that works for both of us"
+7. **The Walk-Away:** Highest-status move — willingness to leave maintains power
+
+### Phase 4: Plan for Status Shifts
+
+1. What to do when the other party raises their status unexpectedly:
+   - Don't compete immediately — absorb, then redirect
+   - Use humor to neutralize (laughter is the great status equalizer)
+   - Ask a question that requires them to teach you something (flattering but recentering)
+2. What to do when the other party lowers YOUR status:
+   - Don't react defensively (confirms the status loss)
+   - Make a calm, specific statement that re-establishes expertise
+   - Change the subject to territory where your status is naturally higher
+3. What to do in group negotiations with mixed status dynamics:
+   - Identify the real decision-maker (not always the highest-title person)
+   - Align your status plays to the actual power holder
+   - Use "we" language to create group-level status alignment
+
+### Phase 5: Build the Negotiation Playbook
+
+1. Script the first 60 seconds (most important for status establishment)
+2. Map 5 key moments where status will be most impactful
+3. Create "if/then" responses for the top 3 status challenges
+4. Design the body language plan (Johnstone's physical status markers)
+5. Plan the environment: seating, timing, materials that support your status strategy
+6. Practice sequence: rehearse status transitions from low → peer → high → peer
+
+## Output Format
+
+```yaml
+negotiation_status_strategy:
+  context: "{what's being negotiated}"
+  parties:
+    - party: "{name/role}"
+      natural_status: "{1-10}"
+      status_signals: ["{typical behaviors}"]
+      status_leverage: "{their source of power}"
+  status_strategy:
+    opening: "{status position and technique}"
+    building: "{how to gradually shift}"
+    proposing: "{peer-level approach}"
+    closing: "{confidence signals}"
+  status_plays:
+    - moment: "{key negotiation moment}"
+      play: "{what to do}"
+      status_direction: "{raise/lower/gift}"
+      rationale: "{why this works here}"
+  contingencies:
+    - scenario: "{status shift event}"
+      response: "{how to adapt}"
+  environment_plan:
+    seating: "{arrangement}"
+    timing: "{when and how long}"
+    materials: "{what supports status}"
+  first_sixty_seconds: "{scripted opening}"
+  body_language:
+    high_status: ["{specific physical signals}"]
+    low_status: ["{specific physical signals}"]
+    transitions: ["{how to shift physically}"]
+```
+
+## Veto Conditions
+
+- **NEVER** compete in status wars — intentional status play is strategic, not ego-driven
+- **NEVER** stay in low status for too long — it becomes the permanent dynamic
+- **NEVER** ignore cultural context — status signals vary dramatically across cultures
+- **NEVER** script rigidly — status dynamics are improvisational and must adapt in real-time
+
+## Completion Criteria
+
+- [ ] Status dynamics mapped for all parties with numerical ratings
+- [ ] Status strategy designed for each negotiation phase
+- [ ] Key status plays scripted for critical moments
+- [ ] Contingency plans for unexpected status shifts
+- [ ] Body language plan aligned with status strategy
+- [ ] First 60 seconds scripted for optimal status establishment

package/squad-storytelling/tasks/structure-episode.md

@@ -0,0 +1,79 @@
+---
+task: "structure-episode"
+responsavel: "dan-harmon"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Episode concept, series context, or theme"
+Saida:
+  - "Complete TV episode structure with A/B stories and beat breakdown"
+Checklist:
+  - "[ ] A-story and B-story defined with thematic rhyme"
+  - "[ ] Cold open through tag structured with circle mapping"
+  - "[ ] Fractal circles identified (episode, act, scene levels)"
+---
+
+# Task: Structure TV Episode
+
+**Task ID:** NARR-006
+**Version:** 1.0.0
+**Command:** `*structure-episode`
+**Agent:** Dan Harmon (dan-harmon)
+**Purpose:** Structure a TV episode using the Story Circle, with A/B story integration and fractal narrative mapping.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `episode_concept` | User prompt | YES |
+| `series_context` | Ongoing series details | PREFERRED |
+| `characters` | Available characters | PREFERRED |
+| `episode_format` | 22min/30min/60min | NO (default: 30min) |
+
+## Execution Phases
+
+### Phase 1: Define A-Story and B-Story
+
+1. **A-Story:** The main plot (what happens)
+2. **B-Story:** The thematic mirror (what the episode is actually about)
+3. Verify thematic rhyme — both stories explore the same theme from different angles
+
+### Phase 2: Map Episode Circle
+
+| Section | Circle Steps | Content |
+|---------|-------------|---------|
+| Cold Open | Step 1 (You) | Establish status quo |
+| Act 1 | Steps 2-3 (Need, Go) | Disruption and commitment |
+| Act 2a | Step 4 (Search) | Complications, fun and games |
+| Midpoint | Step 5 (Find) | The turn, the discovery |
+| Act 3a | Step 6 (Take) | Consequences, the price |
+| Act 3b | Steps 7-8 (Return, Change) | Resolution, new status quo |
+| Tag | Coda | For the audience's unconscious |
+
+### Phase 3: Beat Breakdown
+
+For each section, define 3-5 beats with:
+- What happens (action)
+- Emotional state of protagonist
+- How it connects to theme
+- A/B story toggle
+
+### Phase 4: Fractal Verification
+
+Verify nested circles work at scene level within each act.
+
+## Veto Conditions
+
+- **NEVER** let A and B stories be thematically disconnected
+- **NEVER** skip the midpoint turn — it drives everything after
+- **NEVER** resolve the B-story before it informs the A-story climax
+
+## Completion Criteria
+
+- [ ] A-story and B-story defined with thematic connection
+- [ ] Full episode structure mapped to Story Circle
+- [ ] Beat breakdown complete for each section
+- [ ] Emotional arc tracked throughout

package/squad-storytelling/tasks/testimonial-story-framework.md

@@ -0,0 +1,135 @@
+---
+task: "testimonial-story-framework"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Raw testimonials or customer feedback"
+  - "Product/service context"
+Saida:
+  - "Testimonials transformed into structured stories using Stories That Stick framework"
+Checklist:
+  - "[ ] Each testimonial follows Normal → Explosion → New Normal arc"
+  - "[ ] Emotional specificity added to generic praise"
+  - "[ ] Stories ready for deployment across channels"
+---
+
+# Task: Transform Testimonials into Stories
+
+**Task ID:** NARR-035
+**Version:** 1.0.0
+**Command:** `*testimonial-story-framework`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Transform flat customer testimonials into compelling stories using Hall's narrative structure, extracting the drama and emotion that make testimonials persuasive.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `raw_testimonials` | Existing reviews, feedback, quotes | YES |
+| `product_service` | What was purchased/used | YES |
+| `customer_profiles` | Who these customers are | PREFERRED |
+| `target_channels` | Where stories will be deployed | PREFERRED |
+| `interview_access` | Can customers be re-interviewed? | NO (default: no) |
+
+## Execution Phases
+
+### Phase 1: Audit Existing Testimonials
+
+1. Collect all existing testimonials and customer quotes
+2. Rate each on the "story spectrum":
+   - Level 1: Generic praise ("Great product!")
+   - Level 2: Feature mention ("The dashboard saved us time")
+   - Level 3: Outcome mention ("We increased revenue 30%")
+   - Level 4: Emotional specificity ("I finally stopped dreading Monday reports")
+   - Level 5: Full narrative (before/problem/after with feeling)
+3. Identify the top 10 testimonials with the most story potential
+4. Note what is MISSING from each — usually the "before" and the "explosion"
+
+### Phase 2: Extract the Story from Each Testimonial
+
+For each high-potential testimonial:
+1. **Find the Normal** — What was life like before? Ask: "What were you doing before?"
+2. **Find the Explosion** — What broke, frustrated, or motivated them to change? "What was the last straw?"
+3. **Find the New Normal** — What is different now? "What can you do now that you couldn't before?"
+4. **Find the Feeling** — What emotion was present at each stage? (stressed, relieved, proud, free)
+5. **Find the Specific Detail** — The one concrete image that makes the story vivid
+6. If interview is possible, use these 5 extraction questions directly
+
+### Phase 3: Structure Each Story
+
+1. Write each testimonial as a 3-part narrative:
+   - **Normal** (2-3 sentences): Set the scene with specificity and relatability
+   - **Explosion** (2-3 sentences): The problem at its worst, the moment of "enough"
+   - **New Normal** (2-3 sentences): Life transformed, with a specific proof point
+2. Include the customer's own words wherever possible — authenticity is non-negotiable
+3. Add the "universal moment" — the line where any prospect would think "that's me"
+4. End with the single most powerful quote from the customer
+
+### Phase 4: Create Format Variations
+
+For each story, create:
+1. **Full narrative** (150-250 words) — Website, case study, email
+2. **Social proof snippet** (50-75 words) — Landing page, social media
+3. **Pull quote** (1-2 sentences) — Ad copy, hero section, email subject line
+4. **Video script** (30-60 seconds) — If video testimonial is planned
+5. **Carousel format** (3-5 slides) — Instagram/LinkedIn carousel
+
+### Phase 5: Deploy and Systematize
+
+1. Map each story to the funnel stage it best serves:
+   - Awareness: Stories that name the problem (resonance)
+   - Consideration: Stories that show the process (trust)
+   - Decision: Stories that prove the outcome (confidence)
+2. Tag stories by persona, industry, use case, and emotional tone
+3. Create a testimonial interview template for future story collection
+4. Design a quarterly "story harvest" process for ongoing collection
+5. Create guidelines for the team: how to spot, request, and capture testimonial stories
+
+## Output Format
+
+```yaml
+testimonial_stories:
+  stories:
+    - customer: "{name/anonymized}"
+      persona_match: "{which audience persona}"
+      raw_testimonial: "{original quote}"
+      structured_story:
+        normal: "{before state with specificity}"
+        explosion: "{breaking point}"
+        new_normal: "{transformed state with proof}"
+        core_feeling: "{emotional journey}"
+        universal_moment: "{the 'that's me' line}"
+      formats:
+        full_narrative: "{150-250 words}"
+        social_snippet: "{50-75 words}"
+        pull_quote: "{1-2 sentences}"
+      funnel_stage: "{awareness/consideration/decision}"
+      tags: ["{persona, industry, emotion}"]
+  interview_template: ["{5 extraction questions}"]
+  collection_process: "{quarterly story harvest design}"
+  deployment_map:
+    website: ["{which stories where}"]
+    social_media: ["{which stories where}"]
+    email: ["{which stories where}"]
+    ads: ["{which stories where}"]
+```
+
+## Veto Conditions
+
+- **NEVER** fabricate or embellish customer quotes — authenticity is sacred
+- **NEVER** accept "Great product!" as a usable testimonial — extract the real story
+- **NEVER** strip the emotion from testimonials to sound "professional" — feeling IS persuasion
+- **NEVER** use testimonials without the "before" — outcomes without context are unconvincing
+
+## Completion Criteria
+
+- [ ] Existing testimonials audited and rated on story spectrum
+- [ ] Top stories structured with Normal → Explosion → New Normal
+- [ ] Each story has universal moment and core feeling identified
+- [ ] Format variations created for each story (full, snippet, quote)
+- [ ] Stories mapped to funnel stages and tagged by persona
+- [ ] Collection process designed for ongoing testimonial harvesting

package/squad-storytelling/tasks/transformation-arc-design.md

@@ -0,0 +1,131 @@
+---
+task: "transformation-arc-design"
+responsavel: "joseph-campbell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Subject of transformation (person, brand, product, audience)"
+  - "Context and desired outcome"
+Saida:
+  - "Complete transformation arc with before/after states and mythic structure"
+Checklist:
+  - "[ ] Before and after states clearly defined with emotional depth"
+  - "[ ] Transformation arc follows mythic death/rebirth pattern"
+  - "[ ] Arc adaptable to multiple content formats"
+---
+
+# Task: Design Transformation Arc
+
+**Task ID:** NARR-020
+**Version:** 1.0.0
+**Command:** `*transformation-arc-design`
+**Agent:** Joseph Campbell (joseph-campbell)
+**Purpose:** Design a complete transformation arc for marketing, using Campbell's death-and-rebirth pattern to create compelling before/after narratives.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `transformation_subject` | Who/what is being transformed (customer, brand, product) | YES |
+| `before_state` | Current state, pain points, limitations | YES |
+| `after_state` | Desired outcome, aspirational identity | YES |
+| `catalyst` | What triggers the transformation (product, service, event) | YES |
+| `medium` | Where the arc will be used (ad, case study, landing page) | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Map the Before State (Death Territory)
+
+1. Define the subject's Ordinary World in vivid detail — what does daily life look like?
+2. Identify the core suffering or dissatisfaction — what is endured but not accepted?
+3. Name the false beliefs or coping mechanisms that maintain the status quo
+4. Quantify the cost of staying (emotional, financial, relational, opportunity cost)
+5. Identify the "last straw" — the moment tolerance breaks
+
+### Phase 2: Design the Threshold Moment
+
+1. What specific event, encounter, or realization triggers the shift?
+2. What is the emotional quality of this moment? (revelation, desperation, hope, anger)
+3. What must the subject give up to cross? (comfort, identity, money, time)
+4. Design the "symbolic death" — what part of the old self must die?
+5. What is the irreversible action that marks commitment?
+
+### Phase 3: Map the Transformation Process
+
+1. **First Trial** — The immediate challenge after committing (buyer's remorse, learning curve)
+2. **Deepening** — Progressive mastery, small wins, growing confidence
+3. **Dark Night** — The moment of doubt where the subject almost reverts
+4. **Breakthrough** — The insight or achievement that makes the transformation real
+5. **Integration** — The new identity solidifies; old patterns no longer fit
+
+### Phase 4: Map the After State (Rebirth Territory)
+
+1. Define the new Ordinary World — what does daily life look like now?
+2. Identify the new beliefs that replaced the old false beliefs
+3. Quantify the gains (emotional, financial, relational, capability)
+4. Describe the "elixir" — what wisdom or capability can they now share with others?
+5. Design the "freedom to live" moment — the scene that captures the transformed life
+
+### Phase 5: Craft Arc Variations
+
+1. **30-second version** — For ads and social: one sentence before, catalyst, one sentence after
+2. **2-minute version** — For testimonials and case studies: emotional detail at each stage
+3. **Long-form version** — For landing pages and keynotes: full mythic arc with all phases
+4. Identify the single most powerful contrast point (before vs after in one image/sentence)
+5. Design the "mirror moment" — where the audience sees themselves in the before state
+
+## Output Format
+
+```yaml
+transformation_arc:
+  subject: "{who is being transformed}"
+  before_state:
+    ordinary_world: "{daily reality}"
+    core_suffering: "{main pain}"
+    false_beliefs: ["{limiting beliefs}"]
+    cost_of_staying: "{quantified cost}"
+    last_straw: "{breaking point}"
+  threshold:
+    trigger: "{catalyst event}"
+    emotional_quality: "{feeling}"
+    sacrifice: "{what must be given up}"
+    symbolic_death: "{what dies}"
+    irreversible_action: "{commitment point}"
+  transformation_process:
+    first_trial: "{immediate challenge}"
+    deepening: "{progressive mastery}"
+    dark_night: "{moment of doubt}"
+    breakthrough: "{turning point}"
+    integration: "{new identity solidifies}"
+  after_state:
+    new_world: "{transformed daily reality}"
+    new_beliefs: ["{empowering beliefs}"]
+    gains: "{quantified gains}"
+    elixir: "{wisdom to share}"
+    freedom_moment: "{scene of transformed life}"
+  arc_versions:
+    thirty_second: "{ad version}"
+    two_minute: "{testimonial version}"
+    long_form: "{full narrative}"
+  power_contrast: "{single most powerful before/after image}"
+  mirror_moment: "{where audience sees themselves}"
+```
+
+## Veto Conditions
+
+- **NEVER** skip the struggle — transformation without ordeal is advertising, not story
+- **NEVER** present transformation as instant — the process must be visible and earned
+- **NEVER** fabricate transformation outcomes — arc must be grounded in reality
+- **NEVER** ignore the "dark night" — the doubt moment is what makes the arc credible
+
+## Completion Criteria
+
+- [ ] Before and after states defined with emotional and quantitative depth
+- [ ] Threshold moment designed with clear symbolic death
+- [ ] Full transformation process mapped (trial through integration)
+- [ ] Three arc versions created (30s, 2min, long-form)
+- [ ] Power contrast and mirror moment identified
+- [ ] Arc tested for audience identification and emotional resonance