Skip to content

StoryKit v1.0

Introduction

The SuperStories Universe Platform enables professional creators, writers, editors, and world builders to author dynamic, immersive, canon-respecting science fiction stories.

Stories written for SuperStories are not static. They are alive — capable of growing, evolving, and reacting — because they are designed using a hybrid method called Organic Data: a fusion of structured and unstructured narrative, built to feed the SuperStories Lore Engine.

Who

This documentation is intended for:

  • Creators — Build original characters, timelines, technology, and canon
  • Writers — Draft immersive, branching, and episodic stories
  • Editors — Enforce canon consistency, structure, and tone
  • World Builders — Engineer persistent data-driven universes

Everyone writing SuperStories must follow the StoryKit Fence & Tagging System to ensure stories are interoperable with the Lore Engine.

What is a SuperStory?

A SuperStory is:

  • A multi-act, character-driven story
  • Structurally tagged with semantic fences and Lore tags
  • Designed to be read by humans and processed by machines
  • Compatible with the Lore Engine’s memory and story graph

Every SuperStory contains:

  • YAML Frontmatter: Story-wide metadata
  • Fenced Structure: Scenes, acts, prompts, decisions
  • Semantic Tags: #tags, {#compound#relationships}, and ~(entity-id) references

When and Where

Apply structure during the writing process, not afterward. Structure should feel organic.

  • Fences wrap your content
  • Tags live inside your prose
  • Every story begins with a title, followed by :::backstory and :::prompt

Why: The Lore Engine

All structure exists to feed the SuperStories Lore Engine, which:

  • Tracks memory across timelines and decisions
  • Understands relationships between people, ships, places, values, events
  • Allows for branching paths, alternate realities, and persistent consequences
  • Ensures continuity and canon alignment

How to Draft a SuperStory

Use StoryKit Fences and Lore Tagging Rules:

Tagging Rules

#tags

Used for:

  • Descriptive lore (e.g. #temporal-anomaly, #honor, #betrayal)
  • Non-rooted relationships (e.g. #son#alexander, #command#bridge)
  • Inline narrative reinforcement

Must always use lowercase-hyphen format.
Do not use spaces or underscores.

{#compound#tags}

Used for relational tagging and data snapshots:

{#changeling#assumes#captain-worf’s-identity}

Represents semantic triple: subject#action#object.

~(entity-id)

Used for defined entities: people, ships, locations, factions.
Always use in:

  • YAML frontmatter
  • :::backstory fences
  • When tagging identity, not lore

Examples:

~(defiant), ~(worf), ~(aranis-prime), ~(section-31)

Use #uss-defiant to describe or attribute lore about the Defiant.
Use ~(defiant) to pull in its canonical root entity from the universe graph.

Final Example

# The Ghosts of Aranis Prime

:::backstory
Characters:
  - ~(worf): 
      - "Grieving #jadzia"
Ships:
  - ~(defiant): 
      - "Hull damage from #dominion skirmish"
:::

:::prompt
The ~(defiant) approaches #aranis-prime.  
A {#temporal-anomaly#pulses#beside#the-ship}, disrupting all sensor data.
:::

:::act1
## The Silent Rift

:::scene1
### Phase Echoes

:::prompt
Captain Worf orders a passive drift scan.  
You detect your own voice in the anomaly’s subspace return.
:::

:::branch
* The crew is tense.  
* Tactical believes the anomaly is trying to communicate.

1. Fire a burst into the rift and await the reply.  
2. Beam a probe into the anomaly with a personality imprint.  
3. Retreat and report the anomaly as unstable.  
:::
:::
:::

Hard Rules

  • All :::act and :::scene fences must include numeric suffixes
  • Every act must contain at least one scene
  • All file names are all lower cases, using - for spaces
  • All Lore tags must use hyphens (-) — no underscores or spaces, capitalization does not matter, but I would pick one.
  • Use ~(id) to reference known entities (identity); use #tag for lore or state of an entity.
  • :::backstory is the root of all Lore loading — treat it like metadata + memory
  • :::branch options must be rich, complete, and cinematic, the better the prompt the better the Readers experience.

SuperStories = Canon + Choice + Continuity