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: workshop-index
status: active-supporting-workspace
updated: 2026-09-06

Story-development workshop

Twenty decision packets address the missing causes in this story. Eighty alternatives began as non-canon proposals. All twenty modules now have author-accepted results; intentionally deferred implementation questions remain labeled inside the packets. No Story Completion task has been marked complete through the workshop.

Start without losing the active thread

The active execution gate remains SC-010 Question 7. This workshop expands the existing workflow's decision support. It is not another TODO list. Preparing all modules is authorized; switching the author-led execution order remains an explicit choice.

For a short mobile session: choose one packet, read its central gate, write an answer, and export Markdown. For a desktop session: review sources and prerequisites, compare alternatives, run the scene and adversarial tests, and record acceptance only after the author confirms the restatement.

First five high-impact sessions

  1. 01 · Purpose: determines what counts as success beyond defeating Samuel.
  2. 02 · Entry and knowledge: determines consent, refusal, and the fairness of evaluation.
  3. 03 · Placement: turns success into a concrete future while separating competence from authority.
  4. 04 · Reconstruction: determines which costs are real, what can change, and whom safeguards protect.
  5. 05 · Luminai generations: resolves what the comparative test can show and prevents a silent implant-model substitution.

The full causal pass is complete. The accepted answers define the governing structure, Konrad's bargain, George's cross-planet role, Sylvan and Orzai's partnership, declining endgame influence, the inner circle's recognition, Samuel's final attempted deal, procedural finality, and flexible later-book order. Open mechanics should now be developed from those constraints rather than reopening the accepted gates.

Dependency order

Use 01 → 02 → 03 → 04 → 05 → 06 → 07 → 08 → 09 → 10 → 11 → 12 → 13 → 15 → 14 → 16 → 17 → 18 → 19 → 20 when preparing a full causal pass. Module 15 comes before 14 because George's final role depends on what observation can still affect. Numbers identify topics, not mandatory execution sequence.

Decision packets

Persistence and authority

Browser answers are local drafts on that browser and origin. They are not synchronized between sites or devices, and clearing browser storage can remove them. Export produces a Markdown file; importing a previous export restores the text for further work. No browser control writes to the vault, creates a canon decision, or sends data to an AI provider.

To integrate: place the exported answer in a dated session, restate it exactly, obtain author acceptance, update the current task and QA decisions, then update the affected canonical notes. Rebuild the websites with python3 scripts/build_story_sites.py.

Keep private answers out of a public repository unless the author has reviewed them for publication. The existing Explorer is public and read-only; spoiler disclosure is not access control.

Sources: 07 Coordination/Story Completion Workflow/WORKFLOW, 07 Coordination/CURRENT-PICKUP, 07 Coordination/Weekly Synthesis/CURRENT-COMPLETION-TODO, 07 QA/2026-09-05 - Comprehensive Story Assessment.