The Weaver
hardens the story
before adaptation.
The storytelling engine for the novel The Guardian in the Wires. It plans, drafts, and hardens the manuscript, then derives comic, voice-over, storyboard, and in-game quest scripts.
The job.
The Weaver works from an outline and world bible, a style guide, and reader state. It plans the narrative, drafts the manuscript, and hardens that manuscript before deriving other formats.
The derived outputs are comic scripts, voice-over scripts, storyboards, and in-game quest scripts. Book media routes to Warehouse. Narrative and quest scripts route to Game Dev.
The handoff.
SCENE is the declared contract. The manuscript is the common narrative source. Book media moves toward Warehouse and pickbits.studio/book, while narrative and quest scripts move toward the game-build studio.
The two routes keep publishing work and game-build work as separate handoffs from the same hardened manuscript.
The decisions behind the engine.
Harden the manuscript before deriving other formats.
The declared order is plan, draft, harden, then derive. Comic, voice-over, storyboard, and quest scripts follow the hardened manuscript.
Use one narrative source across every adaptation.
The same manuscript supplies the derived scripts. The comic, audio, storyboard, and game routes do not begin as separate narratives.
Keep the narrative constraints explicit.
The outline and world bible, style guide, and reader state are declared inputs. They enter the story engine before the SCENE output is produced.
Route publishing and game work to different engines.
Book media goes to Warehouse. Narrative and quest scripts go to Game Dev. Each output follows the downstream job it serves.
The operating stack.
Licensing this engine
The Weaver turns one hardened manuscript into comic, voice-over, storyboard, and quest scripts. It is operated software set up for the licensee around the narrative source, its declared constraints, and the required output formats.
Who it suits - Anyone holding one canonical source that has to appear in many forms: independent publishers, IP studios, transmedia and game teams, and equally product and policy owners deriving docs, decks and scripts from a single spec. Proven on a novel.
What it replaces - Separate adaptation passes for each output format.
Run it for - One narrative asset resold across formats: book, audio, comic, and in-game script.
- Your canonical source hardened, with its constraints declared
- The derivations you actually need, wired to your output formats
- Formats — how many derivations each source has to produce
- Canon — how often the source moves under the derivations
- Volume — how many sources a year go through it
Licensing terms are on application — the list above is what drives them, not a rate card. What you pay tracks that scope.
These engines change as they run; if something here has gone stale, tell me and I will fix it.