Storyscape
A platform for building fictional universes, not writing books. Quantum Leap's creative-tech product, in early-phase architecture.
The creative-tech market has tools for writing (Google Docs, Scrivener), for designing (Figma, Notion), and for chatting with AI (ChatGPT, Claude). It does not have a tool for building the foundation of a fictional universe. The space that comes before the book, before the game, before the screenplay: the laws, the essence, the form, and the awakening of a world.
Storyscape exists to occupy that pre-narrative space. It is not an editor of text. It is not a Notion template. It is a platform where authors, game designers, and screenwriters construct the ontological base of their universes. The platform holds the foundation. Everything that comes later — books, scripts, games, shorts — respects that base.
The constraint that makes the project distinctive is design: Storyscape cannot feel like a dashboard. The creator never leaves the creative space. There is no admin panel, no project console, no settings sidebar in the main flow. The platform is an immersive instrument, dark and atmospheric, designed as a creative tool, not a project manager.
What is at stake: an IP-creation platform that becomes infrastructure for emerging creators across multiple formats, with the Oracle as the AI character that lives inside the product, not as an embedded chatbot.
Storyscape is a Quantum Leap product in early-phase architecture. The build path is Horizon 02 with platform-building patterns from Horizon 03.
Horizon 02 designed the conceptual hierarchy: Universo → Mundos → World Content. The Universo is the ontological layer (genre, essence, laws, palette, identity). The Mundos are scale and narrative-role expansions. World Content is the granular detail (regions, creatures, factions, magic, economy, lore) across 18+ data-driven categories implemented via a Registry Pattern: one generic component reads from a registry, scaling architecturally without adding components per category.
The Forge is the central editor, decomposed into 6 sealed stages, each with a distinct interaction model: dialogue (Stage 0), ceremony (Stage 1), radial canvas (Stage 2), tribunal (Stage 3), cards (Stage 4), synthesis (Stage 5). Each stage feels different on purpose. Form follows the cognitive nature of the decision being made.
Horizon 03 designed the Oracle: the AI as a character within the product, with voice, visual presence, and personality that adapts by genre. Dark fantasy speaks of ancestral forces, cyberpunk speaks of algorithms, solarpunk is organic and optimistic. Two engines drive the Oracle: structured suggestions per field and contextual streaming chat per stage and category. Prompts live in the database, version-managed via admin, never in code.
The platform is in Phase 0. Schema, repo structure, design-system briefs, and CLAUDE.md operational documentation are being authored before frontend work begins.
The architecture has three layers.
Layer 01 / The Forge. Six ceremonial stages that transform an idea into a universe:
00 O CHAMADO dialogue and reference selection 01 A CENTELHA ceremonial naming with particle materialization 02 A ESSÊNCIA radial canvas with 8 thematic nodes in orbit 03 AS LEIS tribunal where the Oracle is Advogado Primordial 04 A FORMA paleta, materiais, leis visuais as identity card 05 O DESPERTAR synthesis, voz pública, sopro, dossiê
Each stage seals. Sealed data becomes permanent context for the AI and for all downstream stages. Breaking a seal has explicit rules per project phase, with friction modals to prevent accident.
Layer 02 / World Content. 18+ content categories implemented via Registry Pattern. One generic component, one registry, scaling forever without architectural debt. Categories include regions, creatures, factions, artifacts, magic systems, economy, lore, characters, and 10+ more.
Layer 03 / The Oracle. AI as character, not chatbot. Two engines:
01 SUGGESTIONS ENGINE POST /api/oracle/generate, structured arrays per field 02 CONTEXTUAL CHAT POST /api/assistant/chat, streaming SSE per stage
Anti-repetition via bigram and Jaccard deduplication. Configurable per field and per stage via admin. Prompts live in the database, versioned. Logs every interaction for audit and quality iteration. Context is incremental: each stage sees only sealed data from previous stages.
Core stack. Next.js 14 App Router + TypeScript. Tailwind CSS v3 + Radix Primitives (custom design system, no shadcn/ui). Zustand for client state. Framer Motion for animations. Supabase (PostgreSQL + RLS) for backend. Supabase Auth with Next.js middleware. Claude API as primary inference, OpenAI as secondary. Midjourney upload and GPT Image-2 generation for visuals. Development via Claude Code, no Lovable.
Storyscape is in Phase 0 by design. Quantum Leap is treating the planning and setup as a first-class deliverable, not a preamble. CLAUDE.md operational documentation, schema design, repository structure, design-system briefs, and per-screen briefs (27 documented to date) are authored before frontend work begins.
The early-phase position is intentional. Three structural decisions are already locked.
The platform is not a text editor. The narrative space is occupied by tools that already exist. Storyscape occupies the pre-narrative space where ontology, laws, and identity are built. This positioning was decided in writing before any UI was drawn.
Each stage has a distinct interaction model. The default product instinct is to use one form across all stages. Storyscape rejected that. The ceremonial design language is the differentiator.
The Oracle is a character. Not a sidebar. Not a chat widget. A voice and personality that adapts by genre across 9 supported genres, all driven by tokens that swap via a data-genre attribute on the root element. Same platform, 9 atmospheres.
The roadmap spans 7 phases, from Foundation to Interactive Stories to multi-format narrative distribution (Shorts, Ebook, GDD, episodic formats).