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
task_id: SC-005
status: active
depth: MACRO
phase: COMPLETE
validation: NOT-RUN
authority: author-accepted

SC-005 — Define Sylvan's Irreversible Choice and Loss

Objective

Define how the escalating startup attacks irreversibly change Sylvan's life and force the modern story into its next environment.

Source

Inherited macro rules

  • The first modern incident is intentionally small and plausibly coincidental.
  • Sylvan's physical server-hosting center loses external connectivity for several hours during a convention presentation.
  • He can still present, but cannot perform the live demo.
  • The hosting provider gives a plausible but slightly suspicious explanation.
  • The event causes no major immediate business loss; its importance is that it is the first incident in a long sequence of attacks that later escalates substantially.

Accepted SC-005 macro result

The startup collapse is not caused by a single optional heroic gamble Sylvan could avoid by walking away. The attacks descend into increasing chaos until the startup's social structure is deliberately broken around him.

Samuel and George manipulate Sylvan's partners inside a separate wireless/story environment, making promises and shaping their interpretation of events outside Sylvan's awareness. Over time the partners turn against Sylvan.

The irreversible loss is therefore the collapse of the startup team and the trust/working relationships that made the venture viable. By the time the structure fails, there is no clean path where Sylvan simply chooses to stop and preserves what existed.

The consequence is a forced transition: Sylvan leaves the failed startup environment and moves into the next stage of the story in another city.

At Macro Shape, this replaces the earlier assumption that Sylvan must make one avoidable decision that causes the collapse. His agency should instead be developed in how he responds to the forced breakdown and what he does in the next environment.

Boundary

Do not yet design the full escalating attack sequence, the exact promises made to each partner, or the detailed mechanics of the separate wireless environment. Those can be developed in later sweeps/tasks.

Dependencies

  • Prerequisites: SC-004
  • Direct downstream: SC-006, SC-025
  • Review reach: SC-027

Sweep records

Macro Shape

Complete. The startup is progressively destabilized; Samuel and George manipulate Sylvan's partners in a separate wireless/story environment until the team turns on him. The loss of the startup/team forces Sylvan into the next story stage in another city.

Later sweeps

Not started.