{
  "core_value_proposition": "A public proof that structured collaborative research produces valuable technical output — convincing the right developers to join and serving the broader UE community with permanent, high-quality learning resources.",
  "features": [
    {
      "name": "Landing Page",
      "description": "The primary pitch page. Communicates who Unreal Expeditions is, what the expedition model is, and why it matters. Immediate access to Join Discord CTA.",
      "priority": "must",
      "persona": "The Deep Diver",
      "user_story": "As a developer discovering this community, I want to immediately understand what it is and why I should join so that I can decide in under 60 seconds whether this is for me.",
      "complexity": "medium",
      "notes": "Must serve both The Recruit (needs the full pitch) and The Convert (needs the Join button immediately). Join CTA must be persistent — sticky nav or repeated throughout the page."
    },
    {
      "name": "How It Works Section",
      "description": "Visual explanation of the expedition lifecycle: Announcement → Team → Expedition → Returns → Conclave → Voyage → Chronicle. Scannable, not text-heavy.",
      "priority": "must",
      "persona": "The Deep Diver",
      "user_story": "As a potential member, I want to understand the structure of the program so that I know what I'm committing to and what I'll get out of it.",
      "complexity": "medium",
      "notes": "This is the key differentiator. Can be a section on the landing page or a dedicated page. Visual treatment is critical — a wall of text describing the phases will lose people."
    },
    {
      "name": "Expedition Showcase Page",
      "description": "A full write-up of a completed expedition. Includes title, topic overview, squad members, key findings with embedded code, demo video, audio version, outcome, and below-the-fold phase journey breakdown.",
      "priority": "must",
      "persona": "The Curious Observer",
      "user_story": "As a developer who found this write-up, I want to read a thorough technical exploration with code and demos so that I can learn something and judge the quality of this community's output.",
      "complexity": "high",
      "notes": "This is the most content-rich page. Needs thoughtful mobile treatment for code blocks. Audio narration is a Could-have enhancement. Phase journey is collapsible/tabbed below the main findings. At launch, seeded with at least one simulated expedition."
    },
    {
      "name": "Join Discord CTA",
      "description": "Persistent, globally accessible call-to-action that links directly to the Discord invite. No forms, no gates.",
      "priority": "must",
      "persona": "The Deep Diver / The Convert",
      "user_story": "As someone ready to join, I want to get to Discord in one click from anywhere on the site so that nothing slows me down.",
      "complexity": "low",
      "notes": "In global nav and repeated at key conversion points throughout pages."
    },
    {
      "name": "Expedition Status Indicator",
      "description": "Shows current expedition phase and countdown to next phase or next expedition. Visible on the landing page.",
      "priority": "should",
      "persona": "The Community Member / The Deep Diver",
      "user_story": "As a visitor or member, I want to see what's happening right now so that I know the community is active and when I could participate.",
      "complexity": "medium",
      "notes": "Needs a simple way to update — could be a JSON file or lightweight CMS entry. Must degrade gracefully when no expedition is active (show countdown to next one or 'accepting topic proposals')."
    },
    {
      "name": "Topic Backlog",
      "description": "Read-only list of proposed future expedition topics. Shows the pipeline of ideas the community is considering.",
      "priority": "should",
      "persona": "The Deep Diver",
      "user_story": "As a potential member, I want to see what topics are coming up so that I can judge whether joining would help me learn what I care about.",
      "complexity": "low",
      "notes": "Simple list with topic name, brief description, and maybe a tag for status (proposed, under consideration, selected). Updated manually. No voting on the website — that happens in Discord."
    },
    {
      "name": "Expedition Archive",
      "description": "Browsable collection of all published expedition write-ups. Organized by topic with cards showing title, topic, outcome status (completed, failed, in progress).",
      "priority": "should",
      "persona": "The Curious Observer / The Community Member",
      "user_story": "As a returning visitor, I want to browse all past expedition output so that I can find topics relevant to my interests.",
      "complexity": "medium",
      "notes": "At launch this may only have 1-2 entries. Design should look good sparse and scale well as content grows. Failed expeditions get distinct visual treatment."
    },
    {
      "name": "Side Program Examples",
      "description": "Section showcasing curated examples of Weekly Inspiration, Thought Provokers, Weekend Proof, and Source Dive to demonstrate community rhythm.",
      "priority": "should",
      "persona": "The Deep Diver",
      "user_story": "As a potential member, I want to see what the community does between expeditions so that I know there's ongoing value beyond the main program.",
      "complexity": "low",
      "notes": "Static curated examples, not live-mirrored from Discord. Could be a section on the landing page or a sub-page."
    },
    {
      "name": "Smart Content Surfacing",
      "description": "Backend logic that personalizes which marketing content or expedition highlights a visitor sees based on their browsing behavior.",
      "priority": "could",
      "persona": "The Deep Diver",
      "user_story": "As a visitor browsing the site, I want to see content relevant to my interests so that I'm more likely to find something that compels me to join.",
      "complexity": "high",
      "notes": "Backend-only — minimal design impact. Requires analytics and content tagging infrastructure. Not needed at launch."
    },
    {
      "name": "AI Audio Narration",
      "description": "Generated audio versions of expedition write-ups, allowing content to be consumed by listening.",
      "priority": "could",
      "persona": "The Curious Observer",
      "user_story": "As a reader, I want to listen to expedition findings so that I can consume content while doing other things.",
      "complexity": "medium",
      "notes": "Content production feature, not a site architecture feature. Just needs an audio player component on expedition pages. Can be added to any write-up at any time."
    },
    {
      "name": "Community Stats",
      "description": "Member count, expeditions completed, and other proof-of-life metrics displayed on the landing page.",
      "priority": "could",
      "persona": "The Deep Diver",
      "user_story": "As a potential member, I want to see that this community is active and growing so that I feel confident joining.",
      "complexity": "low",
      "notes": "Counterproductive at small scale. Add once numbers are meaningful. Manually updated."
    },
    {
      "name": "Content Search",
      "description": "Search across all published expedition content by topic, engine subsystem, or keyword.",
      "priority": "could",
      "persona": "The Curious Observer / The Community Member",
      "user_story": "As a returning visitor, I want to search for specific engine topics so that I can quickly find relevant expedition output.",
      "complexity": "medium",
      "notes": "Becomes important as archive grows. Not needed at launch with 1-2 expeditions."
    }
  ]
}