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.

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.

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

Story files

Browse the files used to develop the story.

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

16 · Suspense under decisive control

Purpose

Move uncertainty to bounded but consequential outcomes rather than faking a threat already excluded.

This packet supports the existing Story Completion Workflow. Its central gate was author-accepted on September 6. It does not answer SC-010 Question 7 or advance that checklist. Central synthesis: Astra, reviewed for integration on September 5.

Accepted result

Samuel cannot seize the conclusion, but George and Samuel can still threaten Sylvan and Orzai's relationship, evidence, judgment, safety, and eligibility for future placement. The pair must preserve independent agency, complete their bonds, protect other people, expose the historical system, and qualify for a House without abusing their growing advantage. These linked outcomes remain uncertain even though decisive control does not.

Relevant source notes

Confirmed facts and current working constraints

  • Sylvan’s decisive control in the final years is established.
  • Samuel and others misinterpret that control.

These constraints inherit their source status. A working physical model, timing estimate, or accepted macro constraint does not establish every implementation detail.

Unresolved gaps and contradictions

  • Reader knowledge; present stakes; local reversibility; costs that do not negate containment.

Prerequisite decisions

Modules: 13, 14, 15. Read their accepted results before closing this gate. Open prerequisites can be explored provisionally, but do not mark dependent choices final. Module numbers are topic IDs; use the dependency order in the workshop index.

Central author gate

Which outcome remains genuinely uncertain even while Samuel cannot seize the conclusion?

AUTHOR-ACCEPTED: personal, evidentiary, ethical, relational, and placement outcomes remain at risk even though Samuel cannot take the final process outcome.

Possibilities and tradeoffs

1. Attribution and defensible proof

PROPOSED: Containment can hold while a particular charge remains unproven. Strong archive thriller; justice cannot depend on proving every secret.

2. Human trust and voluntary cooperation

PROPOSED: People can reject Sylvan’s account or leave the process. Strong agency; disagreement must not be treated as system failure or villainy.

3. Privacy versus public credibility

PROPOSED: More revealing evidence could persuade faster but harm descendants. Strong concrete choice; establish alternatives beyond secrecy or total exposure.

4. Placement and institutional legitimacy

PROPOSED: Sylvan can win tactically and still fail to show the process deserves continuation. Large stakes; ground them in one affected life and one actual decision.

Targeted follow-up questions

  • What does the reader know before Samuel knows?
  • Which mistake can cost Sylvan something permanent without freeing Samuel?
  • What will Sylvan refuse to do merely to make the audience believe?

Scene test

Non-canon situation: A witness retracts permission to use decisive private material minutes before a public stage; containment remains sound but Sylvan must prove less or find another route.

Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives.

Adversarial questions

  • Does the scene create uncertainty about a real choice, or merely hide a safety system until a surprise rescue?
  • Which established constraint would this answer break, and what evidence would reveal that break before the payoff?

Completion checklist

  • [x] Answer the central question in the author's own words.
  • [x] Identify the chosen possibility, a modified combination, or a different answer; explain rejected tradeoffs.
  • [x] Resolve or explicitly defer prerequisites 13, 14, 15.
  • [x] Run the scene test above and state the consequence for the people involved.
  • [x] Answer the adversarial challenge without granting unexplained knowledge or authority.
  • [x] Record what remains working, proposed, or unresolved.
  • [x] Obtain explicit author acceptance before updating canon or workflow progress.
  • [x] Trace the accepted answer through the affected notes and rebuild both projections.

Answer and decision record

Module: 16 · Suspense under decisive control
Gate: Which outcome remains genuinely uncertain even while Samuel cannot seize the conclusion?
State: DRAFT / PROPOSED / AUTHOR-ACCEPTED / REJECTED / DEFERRED
Author answer (verbatim):
Exact restatement:
Selected option or new answer:
Why this tradeoff:
Rejected alternatives and reasons:
Prerequisites resolved / deferred:
Scene test: choices, permissions, evidence, cost:
Adversarial result:
Remaining uncertainty:
Explicit acceptance wording and date:
Affected notes updated:
QA decision reference:
Workflow task and macro-depth effect:
Website rebuild and verification:

Notes and website sections affected