sinapse-ai 1.0.0

package/squad-storytelling/tasks/diagnose-narrative.md

@@ -0,0 +1,111 @@
+---
+task: "diagnose-narrative"
+responsavel: "narrative-orchestrator"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "User message with storytelling/narrative request"
+  - "Routing catalog (knowledge-base/routing-catalog.md)"
+Saida:
+  - "Narrative diagnosis with routing recommendation"
+Checklist:
+  - "[ ] User intent parsed and categorized"
+  - "[ ] Cross-cutting answer delivered to user"
+  - "[ ] Routing suggestion provided with confidence level"
+---
+
+# Task: Diagnose & Route — Narrative Masters Squad
+
+**Task ID:** NARR-001
+**Version:** 1.0.0
+**Command:** `*diagnose-narrative`
+**Agent:** Arc (narrative-orchestrator)
+**Purpose:** Analyze the user's storytelling or narrative question, provide an immediate cross-cutting answer, and determine whether specialist routing is needed.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `user_message` | User prompt | YES |
+| `routing_catalog` | `knowledge-base/routing-catalog.md` | YES |
+| `conversation_history` | Session context | NO |
+
+## Preconditions
+
+1. User message is not empty
+2. Routing catalog is loaded and accessible
+
+## Execution Phases
+
+### Phase 1: Parse Request
+
+1. Extract the core question or intent from the user message
+2. Identify keywords, narrative domains, and storytelling context
+3. Determine the story scale: micro (anecdote, post), meso (presentation, episode), macro (screenplay, novel), or meta (movement, cultural)
+4. Determine the narrative domain: mythic, structural, personal, business, performative, or movement
+
+### Phase 2: Match Routing Catalog
+
+1. Load `knowledge-base/routing-catalog.md`
+2. Match extracted keywords against domain keyword lists
+3. Score each domain by keyword overlap and contextual relevance
+4. Identify `primary_agent` and `secondary_agent` for the top-scoring domain
+5. If multiple domains score equally, consider the story scale to break ties:
+   - Micro scale: prefer kindra-hall, park-howell
+   - Meso scale: prefer nancy-duarte, oren-klaff, dan-harmon, blake-snyder
+   - Macro scale: prefer blake-snyder, joseph-campbell
+   - Meta scale: prefer marshall-ganz, joseph-campbell
+
+### Phase 3: Cross-Cutting Answer
+
+**MANDATORY — Always execute this phase before any routing.**
+
+1. Provide an immediate, useful answer to the user's question
+2. The answer should be actionable and demonstrate narrative domain competence
+3. Include relevant context: frameworks mentioned, quick storytelling guidance
+4. Reference the applicable narrative principle or framework by name
+5. This answer must stand alone — even if the user never follows the routing suggestion
+
+### Phase 4: Confidence Assessment
+
+| Level | Criteria | Action |
+|-------|---------|--------|
+| HIGH | Clear keyword match, single domain, unambiguous | Route to primary agent |
+| MEDIUM | Multiple domains match, slight ambiguity | Suggest primary + secondary |
+| LOW | No clear match, vague request, cross-domain | Stay with orchestrator, ask clarifying questions |
+
+## Output Format
+
+```yaml
+diagnosis:
+  intent: "{parsed user intent}"
+  narrative_domain: "mythic | structural | personal | business | performative | movement"
+  story_scale: "micro | meso | macro | meta"
+  matched_domain: "{domain from routing catalog}"
+  confidence: "HIGH | MEDIUM | LOW"
+  primary_agent: "{agent-id}"
+  secondary_agent: "{agent-id}"
+  cross_cutting_answer: |
+    {The immediate answer provided to the user}
+  routing_suggestion: |
+    {Why this specialist was chosen and what they can add}
+```
+
+## Veto Conditions
+
+- **NEVER** route without providing a cross-cutting answer first
+- **NEVER** route when confidence is LOW — stay with orchestrator and ask clarifying questions
+- **NEVER** load a specialist agent file during diagnosis — only identify the route
+- **NEVER** default to joseph-campbell for every question — match the actual domain
+
+## Completion Criteria
+
+- [ ] User intent parsed and categorized
+- [ ] Narrative domain and story scale identified
+- [ ] Routing catalog consulted and domain matched
+- [ ] Cross-cutting answer delivered to user
+- [ ] Confidence level assessed
+- [ ] Routing suggestion provided (if confidence >= MEDIUM)

package/squad-storytelling/tasks/email-sequence-storytelling.md

@@ -0,0 +1,142 @@
+---
+task: "email-sequence-storytelling"
+responsavel: "park-howell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Brand context and BrandScript (or inputs to create one)"
+  - "Email sequence goal and audience"
+Saida:
+  - "Complete email sequence using SB7 storytelling framework"
+Checklist:
+  - "[ ] Each email follows ABT structure"
+  - "[ ] Sequence maps to SB7 framework progression"
+  - "[ ] Open loops maintain engagement across emails"
+---
+
+# Task: Email Sequence Storytelling
+
+**Task ID:** NARR-039
+**Version:** 1.0.0
+**Command:** `*email-sequence-storytelling`
+**Agent:** Park Howell (park-howell)
+**Purpose:** Design email sequences that use the ABT framework and SB7 principles to tell a progressive story, turning subscribers into engaged customers.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `brand_context` | Brand, product, BrandScript | YES |
+| `sequence_goal` | Welcome, nurture, launch, re-engagement, onboarding | YES |
+| `audience` | Who receives the sequence | YES |
+| `email_count` | Number of emails in sequence | PREFERRED (default: 7) |
+| `frequency` | Sending cadence | NO (default: every 2-3 days) |
+
+## Execution Phases
+
+### Phase 1: Map Sequence to SB7 Story Arc
+
+1. Each email corresponds to an SB7 element, creating a progressive narrative:
+   - Email 1: **Character** — "We see you. Here's what we know about your world."
+   - Email 2: **Problem** — "Here's what's really going on (external + internal problem)"
+   - Email 3: **Guide** — "We've been where you are. Here's how we can help."
+   - Email 4: **Plan** — "Here are the 3 simple steps."
+   - Email 5: **Call to Action** — "Here's what to do next."
+   - Email 6: **Failure** — "Here's what happens if you don't act."
+   - Email 7: **Success** — "Here's what life looks like on the other side."
+2. Adjust mapping based on sequence type (launch sequences front-load urgency)
+3. Ensure each email can stand alone while building the larger arc
+
+### Phase 2: Write Each Email with ABT
+
+For each email, apply the ABT (And, But, Therefore) structure:
+1. **Subject line** — Must create an open loop or promise a revelation
+2. **Opening (And)** — Establish shared context, rapport, or continue previous email's story
+3. **Conflict (But)** — Introduce tension, problem, or challenge relevant to this email's SB7 element
+4. **Resolution (Therefore)** — Provide insight, action step, or preview of next email
+5. **CTA** — One clear action per email (reply, click, read, share)
+6. **Open loop** — Final line that creates anticipation for the next email
+
+### Phase 3: Design Open Loop Architecture
+
+1. Each email opens a loop that the NEXT email closes (maintaining binge-readability)
+2. Types of open loops:
+   - Story cliffhanger: "Tomorrow I'll tell you what happened next..."
+   - Question hook: "But there's one thing most people get wrong about this. I'll reveal it next time."
+   - Promise hook: "In the next email, I'll share the exact framework that..."
+3. Map the loop chain: Email 1 opens loop A → Email 2 closes A, opens B → etc.
+4. The final email closes all remaining loops and resolves the narrative
+
+### Phase 4: Optimize for Engagement
+
+1. Write 3 subject line variations per email (for A/B testing)
+2. Keep each email focused on ONE idea (the SB7 element it represents)
+3. Use "you" more than "we" — the subscriber is the character
+4. Include one story per email — personal anecdote, case study, or analogy
+5. Design the P.S. line as a secondary hook (highest-read element after subject line)
+6. Optimize preview text to complement the subject line
+
+### Phase 5: Create Sequence Mechanics
+
+1. Define trigger/enrollment criteria (when does someone enter this sequence?)
+2. Design exit conditions (what action moves them to the next sequence?)
+3. Create segmentation points — where behavior splits the audience
+4. Plan the "rescue" emails — what to send if someone stops opening
+5. Design the handoff — where this sequence connects to the next one
+6. Document A/B test plan for subject lines and CTAs
+
+## Output Format
+
+```yaml
+email_sequence:
+  name: "{sequence name}"
+  goal: "{what the sequence achieves}"
+  audience: "{who receives it}"
+  frequency: "{cadence}"
+  sb7_mapping:
+    - email: 1
+      sb7_element: "Character"
+      subject_line: "{primary}"
+      subject_variations: ["{alt 1}", "{alt 2}"]
+      abt:
+        and: "{shared context}"
+        but: "{tension}"
+        therefore: "{insight/action}"
+      story: "{email's narrative element}"
+      cta: "{one clear action}"
+      open_loop: "{hook for next email}"
+      ps: "{secondary hook}"
+    # ... all emails
+  loop_architecture:
+    - email: 1
+      opens: "{loop A}"
+    - email: 2
+      closes: "{loop A}"
+      opens: "{loop B}"
+  mechanics:
+    trigger: "{enrollment criteria}"
+    exit: "{success condition}"
+    segmentation_points: ["{where behavior splits}"]
+    rescue_emails: "{re-engagement plan}"
+    handoff: "{next sequence connection}"
+  ab_test_plan: ["{what to test}"]
+```
+
+## Veto Conditions
+
+- **NEVER** send emails without a narrative arc — isolated emails are noise
+- **NEVER** make every email a sales pitch — the sequence is a STORY, not a sales funnel
+- **NEVER** write subject lines that don't connect to the email body — clickbait destroys trust
+- **NEVER** skip the open loop — without anticipation, subscribers stop opening
+
+## Completion Criteria
+
+- [ ] Complete sequence mapped to SB7 elements
+- [ ] Each email structured with ABT and clear CTA
+- [ ] Open loop architecture chains emails together
+- [ ] Subject line variations provided for A/B testing
+- [ ] Sequence mechanics documented (triggers, exits, segmentation)
+- [ ] Each email stands alone while contributing to the arc

package/squad-storytelling/tasks/employee-advocacy-stories.md

@@ -0,0 +1,156 @@
+---
+task: "employee-advocacy-stories"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Organization context and culture"
+  - "Advocacy goals (recruitment, engagement, brand)"
+Saida:
+  - "Employee storytelling program with frameworks and story collection system"
+Checklist:
+  - "[ ] Internal story types defined (Culture, Growth, Impact, Belonging)"
+  - "[ ] Story collection process designed with interview guides"
+  - "[ ] Employee stories structured for internal and external deployment"
+---
+
+# Task: Employee Advocacy Stories
+
+**Task ID:** NARR-037
+**Version:** 1.0.0
+**Command:** `*employee-advocacy-stories`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Build an employee storytelling program that strengthens culture internally and employer brand externally, using Hall's story structure methodology.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `organization` | Company, size, industry, culture | YES |
+| `advocacy_goals` | Recruitment, engagement, employer brand, retention | YES |
+| `culture_values` | Stated values and cultural norms | YES |
+| `existing_programs` | Current employee engagement or advocacy initiatives | PREFERRED |
+| `target_audience` | Prospective employees, current team, external market | NO |
+
+## Execution Phases
+
+### Phase 1: Define Internal Story Types
+
+1. **Culture Stories** — "What it's really like to work here"
+   - Moments that embody values in action (not posters on walls)
+   - Stories of how things are done differently here
+2. **Growth Stories** — "How I became who I am here"
+   - Career development, skill acquisition, mentorship
+   - The moment an employee realized they had grown
+3. **Impact Stories** — "How my work matters"
+   - Customer lives changed, projects that made a difference
+   - The "why" behind the daily work
+4. **Belonging Stories** — "How I found my place"
+   - Inclusion moments, team bonding, feeling seen
+   - When someone went from "working here" to "being part of this"
+
+### Phase 2: Design the Story Collection Process
+
+1. Create a story interview guide with 5 open-ended questions per story type:
+   - Culture: "Tell me about a time when something happened here that wouldn't happen anywhere else"
+   - Growth: "What can you do now that you couldn't do when you started?"
+   - Impact: "When did you realize your work actually mattered to someone?"
+   - Belonging: "When did you first feel like you truly belonged here?"
+2. Design the "story harvest" event — a structured workshop where teams share stories
+3. Create an anonymous story submission channel (for introverts and sensitive stories)
+4. Train 5-10 "story champions" — employees who help others find and tell their stories
+5. Plan quarterly collection cadence with rotating themes
+
+### Phase 3: Structure Employee Stories
+
+For each collected story:
+1. Apply Normal → Explosion → New Normal:
+   - Normal: What was the employee's world before this moment?
+   - Explosion: What happened that created the change/realization?
+   - New Normal: What is different now because of this experience?
+2. Find the "universal moment" — the line that any employee (current or future) would relate to
+3. Ensure the employee's voice is preserved — edit for clarity, not for corporate polish
+4. Connect to a specific company value (naturally, not forced)
+5. Add the "I stayed because..." bridge for retention-focused stories
+
+### Phase 4: Create Deployment Strategy
+
+1. **Internal deployment:**
+   - All-hands meetings: Feature one story per meeting
+   - Onboarding: New hires hear stories from each department
+   - Internal newsletter: Story of the week/month
+   - Slack/Teams: Story channel with regular contributions
+2. **External deployment:**
+   - Careers page: Stories by role, department, and experience level
+   - Social media: Employee takeovers with guided storytelling
+   - Glassdoor/LinkedIn: Structured employee narratives
+   - Recruitment materials: Stories matched to open role types
+3. For each channel, specify the format (video, written, audio, carousel)
+
+### Phase 5: Build the Ongoing Program
+
+1. Design recognition: employees who share stories are celebrated
+2. Create the "story library" — searchable database of employee stories
+3. Measure impact: track engagement, applicant quality, retention correlation
+4. Plan annual "Story Summit" — an event celebrating the best stories of the year
+5. Design the feedback loop: how stories inform culture initiatives
+6. Create manager guide: how to spot, encourage, and share team stories
+
+## Output Format
+
+```yaml
+employee_advocacy:
+  organization: "{name}"
+  goals: ["{recruitment, engagement, brand}"]
+  story_types:
+    culture:
+      description: "{what it captures}"
+      interview_questions: ["{5 questions}"]
+      example_story: "{structured example}"
+    growth:
+      description: "{what it captures}"
+      interview_questions: ["{5 questions}"]
+      example_story: "{structured example}"
+    impact:
+      description: "{what it captures}"
+      interview_questions: ["{5 questions}"]
+      example_story: "{structured example}"
+    belonging:
+      description: "{what it captures}"
+      interview_questions: ["{5 questions}"]
+      example_story: "{structured example}"
+  collection_process:
+    interview_guide: "{complete guide}"
+    story_harvest_event: "{workshop design}"
+    submission_channel: "{anonymous option}"
+    champions: "{training plan}"
+    cadence: "{quarterly themes}"
+  deployment:
+    internal: ["{channels and formats}"]
+    external: ["{channels and formats}"]
+  program_design:
+    recognition: "{how storytellers are celebrated}"
+    story_library: "{database design}"
+    metrics: ["{what to measure}"]
+    annual_event: "{Story Summit design}"
+    manager_guide: "{how leaders participate}"
+```
+
+## Veto Conditions
+
+- **NEVER** force employees to tell stories — voluntarism is essential for authenticity
+- **NEVER** edit out the employee's voice — clarity yes, corporate polish no
+- **NEVER** use employee stories without their explicit consent
+- **NEVER** only share "happy" stories — authentic culture includes challenge and growth
+
+## Completion Criteria
+
+- [ ] Four internal story types defined with interview guides
+- [ ] Story collection process designed (interviews, harvests, submissions)
+- [ ] Story champion training plan created
+- [ ] Deployment strategy covers both internal and external channels
+- [ ] Ongoing program designed with recognition, metrics, and cadence
+- [ ] Manager guide created for leadership participation

package/squad-storytelling/tasks/founder-story-craft.md

@@ -0,0 +1,138 @@
+---
+task: "founder-story-craft"
+responsavel: "kindra-hall"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Founder background and company context"
+  - "Key moments in founding journey"
+Saida:
+  - "Compelling founder story crafted with vulnerability and strategic purpose"
+Checklist:
+  - "[ ] Founder story follows Normal → Explosion → New Normal arc"
+  - "[ ] Vulnerability present without self-indulgence"
+  - "[ ] Story bridges founder's 'why' to customer's 'why'"
+---
+
+# Task: Craft Founder Story
+
+**Task ID:** NARR-036
+**Version:** 1.0.0
+**Command:** `*founder-story-craft`
+**Agent:** Kindra Hall (kindra-hall)
+**Purpose:** Craft a compelling founder story that builds trust and emotional connection by revealing the human behind the brand, using Hall's methodology.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `founder_background` | Personal history, career, motivations | YES |
+| `founding_moment` | What triggered the creation of the company | YES |
+| `company_context` | What the company does and who it serves | YES |
+| `struggles` | Difficulties faced before and during founding | PREFERRED |
+| `current_state` | Where the company is today | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Find the Defining Moment
+
+1. Interview/analyze the founder's life for the catalytic moment — when did everything change?
+2. Look for the "explosion" — not the business plan, but the EMOTIONAL breaking point
+3. Identify the pattern of three:
+   - What the founder WAS doing (Normal)
+   - What happened that made it IMPOSSIBLE to continue (Explosion)
+   - What they BECAME by starting this company (New Normal)
+4. Find the "unlikely" detail — the thing that makes this story uniquely theirs
+5. Identify the vulnerability — the fear, doubt, failure, or struggle that makes them human
+
+### Phase 2: Structure the Founder Story
+
+1. **Normal (The Before):**
+   - Paint the founder's world before the company with specific, sensory details
+   - Show what was good about it — what they were giving up
+   - Establish their competence subtly — credibility without bragging
+   - Include a hint of dissatisfaction or calling
+2. **Explosion (The Catalyst):**
+   - The specific moment that changed everything (day, place, feeling)
+   - Make this visceral — what did they see, hear, feel?
+   - Show the stakes — what was at risk?
+   - Include the "almost didn't" moment — they nearly chose the safe path
+3. **New Normal (The After):**
+   - The decision to act and its immediate aftermath
+   - Early struggles that tested the commitment
+   - The first sign it was going to work
+   - Where they are now — but framed through what they learned, not what they achieved
+
+### Phase 3: Calibrate Vulnerability
+
+1. Vulnerability builds trust — but must be calibrated:
+   - Too little: Sounds like a press release (no connection)
+   - Too much: Sounds like therapy (uncomfortable)
+   - Just right: Sounds like a conversation with a wise friend (trust)
+2. Include ONE significant failure or fear — no more, no less
+3. Show the founder as a real person, not a superhero
+4. Ensure the vulnerability serves the audience: "Here's what I learned that helps YOU"
+5. Test: Would the founder be comfortable sharing this at a dinner party?
+
+### Phase 4: Bridge Founder to Customer
+
+1. Identify the shared "why" — what the founder cares about that the customer also cares about
+2. Show how the founder's struggle mirrors the customer's struggle
+3. Create the "I built this for you" moment — the bridge from founder pain to customer solution
+4. Ensure the founder story ENDS with the customer, not the founder
+5. The last paragraph should implicitly say: "And that's why this exists for you"
+
+### Phase 5: Create Deployment Versions
+
+1. **Keynote version** (5-8 minutes) — Full emotional arc with pauses and audience connection
+2. **About page version** (400-600 words) — Web-optimized with scannable structure
+3. **Elevator version** (60 seconds) — The core arc compressed to its essence
+4. **Social media version** (280 characters) — The single most powerful sentence
+5. **Bio version** (100 words) — Third-person with the defining moment woven in
+6. **Podcast/interview version** — Key beats and prompts for when the founder is interviewed
+
+## Output Format
+
+```yaml
+founder_story:
+  founder: "{name}"
+  defining_moment: "{the explosion}"
+  narrative:
+    normal: "{before — specific and sensory}"
+    explosion: "{catalyst — visceral and stakes-driven}"
+    new_normal: "{after — lessons and current state}"
+  vulnerability_point: "{the honest struggle that builds trust}"
+  founder_customer_bridge: "{shared why — their pain → your solution}"
+  unlikely_detail: "{the unique element that makes this memorable}"
+  versions:
+    keynote: "{5-8 minute version}"
+    about_page: "{400-600 words}"
+    elevator: "{60-second version}"
+    social: "{one powerful sentence}"
+    bio: "{100-word third-person version}"
+    interview_beats: ["{key moments to hit when telling live}"]
+  deployment:
+    website: "{where and how}"
+    pitch_deck: "{which slide}"
+    social_media: "{which platforms, which version}"
+    media_kit: "{version for press}"
+```
+
+## Veto Conditions
+
+- **NEVER** write a founder story that reads like a resume — chronology is not story
+- **NEVER** skip the vulnerability — perfect founders are not trusted
+- **NEVER** end with the founder — end with the customer and the mission
+- **NEVER** fabricate or embellish the founding moment — authenticity is the entire point
+
+## Completion Criteria
+
+- [ ] Defining moment identified with specific, sensory detail
+- [ ] Story follows Normal → Explosion → New Normal arc
+- [ ] Vulnerability calibrated (present but not self-indulgent)
+- [ ] Founder-to-customer bridge created
+- [ ] All deployment versions written (keynote, about page, elevator, social, bio)
+- [ ] Interview beats documented for live storytelling situations

package/squad-storytelling/tasks/identify-archetypes.md

@@ -0,0 +1,76 @@
+---
+task: "identify-archetypes"
+responsavel: "joseph-campbell"
+responsavel_type: "agent"
+atomic_layer: true
+elicit: true
+Entrada:
+  - "Narrative, brand, or situation to analyze"
+Saida:
+  - "Archetype analysis with character/force mapping"
+Checklist:
+  - "[ ] All characters/forces mapped to archetypes"
+  - "[ ] Shadow and Trickster identified (often overlooked)"
+  - "[ ] Recommendations for strengthening archetypal resonance"
+---
+
+# Task: Identify Archetypes
+
+**Task ID:** NARR-004
+**Version:** 1.0.0
+**Command:** `*identify-archetypes`
+**Agent:** Joseph Campbell (joseph-campbell)
+**Purpose:** Identify and analyze archetypal patterns in any narrative, brand, or situation.
+
+---
+
+## Inputs
+
+| Input | Source | Required |
+|-------|--------|----------|
+| `narrative` | Story, brand description, or situation | YES |
+| `context` | Literary, brand, personal, organizational | PREFERRED |
+
+## Execution Phases
+
+### Phase 1: Map Characters to Archetypes
+
+For each character or force, determine which archetype(s) they embody:
+
+| Archetype | Function | Question |
+|-----------|----------|----------|
+| Hero | Undergoes transformation | Who is changed by this story? |
+| Mentor | Provides wisdom/tools | Who guides the hero? |
+| Threshold Guardian | Tests readiness | What barriers test commitment? |
+| Herald | Announces change | What signals the call to adventure? |
+| Shapeshifter | Creates uncertainty | Who cannot be fully trusted? |
+| Shadow | Represents darkness | What is the hero's dark mirror? |
+| Trickster | Breaks rules | Who brings chaos and humor? |
+| Allies | Provide support | Who stands with the hero? |
+
+### Phase 2: Analyze Archetypal Dynamics
+
+1. Is the Shadow a true dark mirror of the Hero?
+2. Does the Mentor withdraw at the right moment?
+3. Are Threshold Guardians testing the right qualities?
+4. Does the Shapeshifter create genuine uncertainty?
+5. Is the Trickster serving the story or just providing comic relief?
+
+### Phase 3: Assess Gaps and Recommendations
+
+1. Which archetypes are missing or underserved?
+2. Where could archetypal resonance be strengthened?
+3. What mythological parallels illuminate the story?
+
+## Veto Conditions
+
+- **NEVER** force an archetype where none exists — not every story uses all 8
+- **NEVER** reduce characters to single archetypes — real characters blend multiple
+- **NEVER** ignore cultural context when assigning archetypal meaning
+
+## Completion Criteria
+
+- [ ] All characters/forces mapped to archetypes with reasoning
+- [ ] Shadow and Trickster identified (or noted as absent)
+- [ ] Archetypal dynamics analyzed for effectiveness
+- [ ] Gaps identified with recommendations for strengthening