Project Explorer

Seeds of the Throne

Seeds of the Throne began as years of conversations and thousands of story ideas. The Project Explorer shows how those ideas are being organized into characters, a world, a timeline, and a finished series.

See how the story is being built Browse the story files
Konrad stands under Samuel's hidden red control while Sylvan observes from the clear opposing side.

Story development tools

The workshop helps the author complete the parts of the story that are still missing.

It explains one story problem, asks one clear question, offers different possible answers, and shows what each answer would change. The author makes the decision. The accepted answer is then added to the characters, timeline, world, and plot.

This is a public, read-only look at the real project, so it contains full spoilers. You can try the workshop, but your draft stays in this browser unless you export it.

  1. The author explains the story in ordinary language.

    The system records those ideas and separates confirmed decisions from suggestions and unanswered questions.

    Read how the system is designed

  2. The workshop asks one question at a time.

    Each question helps the author decide a missing cause, character choice, relationship, world rule, or event.

    Open a workshop question

  3. Accepted answers are added where they belong.

    An accepted decision can update character notes, the timeline, world rules, plot events, and the list of remaining questions.

    Review decisions and supporting information

  4. Use the completed plan to write and revise scenes.

    The planned system will create scene outlines, draft prose, check continuity, revise weak sections, and assemble the manuscript for the author's approval.

    Read the system plan

Seeds of the Throne is the working example. The notes, decisions, and workshop below are the live project, not a demonstration mockup.

See what the analysis foundSee where development continuesEnter the story

Current story development

See what the story already has and what it still needs.

The system checks the whole story for missing causes, weak character decisions, unclear rules, and unfinished events. The results show the author what to work on next.

Current story premise

The colonization process trains participants and contains dangerous criminals.

Humanity developed the Luminai inside an interactive colonization environment. Sylvan and his Luminai are tested against Samuel Franklin, a criminal already held inside the containment process.

The current story problem Explain how Sylvan can expose Samuel while Samuel still believes he can regain control.

See how the story changed

9 / 27major story problems resolved

Current development pass33%
33%
Current sweep
Macro Shape
Current task
SC-010
  1. 01 Macro
  2. 02 Causal
  3. 03 Agency
  4. 04 Systems + evidence
  5. 05 Sequence
  6. 06 Scene map
  7. 07 Scene development
  8. 08 Draft

What the story needs next

  • Human–Luminai breakthrough
  • Evidence chain
  • Character agency
Follow the full story roadmap

Story files

Browse the files used to develop the story.

Search 561 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

Document metadata
type: development-session
status: completed
date: 2026-08-26
topics: docs website, creative possibilities, research queue, author review

Experimental Ideas Docs Interface

Result

Added a live Experimental Ideas workspace to the docs website at docs/ideas.html.

The page reads a stable current pointer and renders the active creative-possibilities packet without creating a separate database or authority source.

Interface behavior

  • shows live idea, unreviewed, and research-prompt totals;
  • lists every non-canon possibility with filters for author-review status;
  • opens a detailed view containing source foundations, story function, character choice, dramatic expression, continuity risk, and next gate;
  • displays the research mechanisms that inspired the pass;
  • displays suggested research as live Markdown checklist items and identifies the ideas each question supports;
  • links directly to the current packet and governing protocol;
  • keeps non-canon authority visible throughout.

Update contract

  • Change idea status in the packet's Author review board.
  • Check off completed research in Suggested research queue.
  • Edit or add candidates in Raw candidate portfolio.
  • Point CURRENT-EXPERIMENTAL-IDEAS.md to a new packet when the active window changes.

The website is read-only. It reflects author decisions recorded in the vault but cannot make them.

Verification

  • parser assertions: 10 ideas, 5 research inputs, 5 suggested research items;
  • desktop visual review completed;
  • mobile review completed at 390 × 844 with no horizontal overflow;
  • idea selection and empty-filter recovery verified;
  • no browser console errors;
  • native buttons, status text, live announcements, focus styling, reduced-motion rules, and responsive reflow preserved.