The Guide

The Guide, as described by its author, is a self-contained interactive storytelling system built around portable Markdown cartridges called Elixirs. These cartridges are designed to be downloaded and launched in ChatGPT, where they guide the user through choose-your-own-adventure-style narratives while maintaining explicit consent and capability boundaries. The project was developed during OpenAI Build Week using Codex and GPT-5.6.

The author states that this is a proof-of-concept for portable conversational experiences, with no evidence of revenue, customers or traction. It appears to be an experimental tool built by one person (Ben Whitfield-Heap) as part of a hackathon submission.

The description states:

• The Guide is a "cabinet of portable interactive-story cartridges called Elixirs"
• Each Elixir is a "versioned Markdown cartridge containing structured metadata, the complete narrative and interaction logic, clear capability and data boundaries, consent and configuration steps, and integrity markers"
• The system allows users to "browse stories, preview what each experience involves, download a cartridge, and copy a safe launch prompt"
• Cartridges are designed to be "self-contained" and "do not require an account, database, API key, or custom runtime; the user's existing ChatGPT conversation becomes the runtime"

The product is described as a format and delivery mechanism for interactive narratives that can be launched in ChatGPT without requiring backend infrastructure.

The description states:

• The Guide "reverses that relationship: you choose an experience, hand it to ChatGPT, and the story takes the lead"
• It aims to make AI conversations feel "less like operating software and more like stepping into an authored, interactive world"
• The system emphasizes transparency about what the experience will ask of the player
• The author claims to have explored whether AI conversations can feel less like software and more like "an authored, interactive world"

The positioning appears to be that of a new format for creating portable, interactive AI experiences that prioritize user agency and safety over traditional prompting approaches.

Not evidenced. The description does not identify specific customer segments or personas. It describes the system as allowing users to "browse stories" but does not specify who those users are or what their needs are beyond general interest in interactive experiences.

Not evidenced. The description makes no mention of pricing, monetization strategies, or business models. It describes a technical prototype with no commercial elements.

The description states:

• Elixirs are "versioned Markdown cartridges"
• They contain "structured metadata and a unique identifier", "the complete narrative and interaction logic", "clear capability and data boundaries", "consent and configuration steps", and "integrity markers"
• The system provides "a working mobile-friendly cabinet for discovering Elixirs"
• Cartridges are "delivered via GitHub Pages deployment"
• The format is designed to be "readable by people, reliably interpreted by a model, versionable in Git, and resistant to partial delivery"
• The system uses "Codex with GPT-5.6" for development

The technical approach appears to be a portable Markdown-based format with integrity checks, delivered through static web hosting.

Not evidenced. The description states this is a "working mobile-friendly cabinet" and "a complete end-to-end experience requiring no custom backend or API credentials," but provides no data on usage, adoption, or engagement. It was submitted to a hackathon and appears to be a prototype.

Not evidenced. The description does not mention any competitors or existing products in this space. No market analysis or competitive positioning is provided.

• Single developer: The project is described as being built by one person (Ben Whitfield-Heap), which raises questions about scalability and long-term maintenance
• Prototype nature: This appears to be a hackathon submission with no evidence of commercial traction or adoption beyond the author's own use
• No monetization strategy: There is no indication of how this would generate revenue or sustain a business
• Limited scope: The description suggests it's an experimental approach without evidence of broader applicability or market demand

1. What specific user needs does this solve that existing AI storytelling tools don't?
2. How many people have actually used the Elixirs beyond the author?
3. Are there any plans to monetize or scale this beyond the current prototype?
4. What are the technical limitations of the Markdown-based approach for more complex interactive experiences?
5. How would you handle user feedback or updates to existing Elixirs?
6. What is the long-term vision for the Elixir format beyond this prototype?