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: session
status: development
updated: 2026-08-20

Seeds Story Gauntlet v0.1

Source and purpose

This note reconciles the author's August 20 mobile brainstorming with the live desktop vault. It creates a Markdown-first story-development loop for finishing Seeds of the Throne piece by piece before attempting chapter prose.

The mobile handoff described a prior 07 Coordination/Seeds Story Gauntlet.md, but that file was not present in the live repository at the start of this desktop session. The concept is therefore implemented here from the author conversation and current vault, without assuming that any missing mobile-generated wording became canon.

Author-established direction

  • Build a linear story skeleton from what already exists.
  • Work on one unit, or at most two or three adjacent units, at a time.
  • Prepare focused questions before asking the author to brainstorm.
  • Separate story quality from prose quality.
  • Use distinct builder and critic roles.
  • Preserve unresolved questions instead of silently inventing answers.
  • Keep the system in ordinary Markdown and Obsidian links.
  • Improve the loop from recorded failures across repeated runs.
  • Pilot one comparatively well-defined section and one genuinely unresolved section.
  • The same obsession, expectation, and desperation Samuel and George once used against other contained criminals ultimately contributes to their downfall when Sylvan turns the mechanism back on them.

v0.1 boundary

Version 0.1 covers story structure only:

map -> retrieve -> brainstorm -> propose -> critique -> author gate -> integrate -> log -> advance

It does not autonomously establish canon, write final chapters, imitate audiobook authors, or update compiled story notes without author approval.

Initial pilots

  1. 08 Story Loop/Units/S-002 - Sylvan Modern Inciting Event — missing, high-value, and blocking the modern protagonist trajectory.
  2. 08 Story Loop/Units/S-018 - Obsession Reversal and Inverted Containment — comparatively well-defined in thematic function but incomplete in mechanism and staging.

Package created

Authority boundary

The author chooses story facts and final prose. The loop may retrieve, organize, diagnose, propose, compare, and revise. A proposal remains proposed until an author gate explicitly accepts it. Research remains advisory. Existing components are preferred over new expansion.