Project Explorer
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.
Story development tools
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.
The system records those ideas and separates confirmed decisions from suggestions and unanswered questions.
Read how the system is designedEach question helps the author decide a missing cause, character choice, relationship, world rule, or event.
Open a workshop questionAn accepted decision can update character notes, the timeline, world rules, plot events, and the list of remaining questions.
Review decisions and supporting informationThe 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 planSeeds of the Throne is the working example. The notes, decisions, and workshop below are the live project, not a demonstration mockup.
Current story development
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
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 changed9 / 27major story problems resolved
Story files
Search 561 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.
Choose one legible hinge that grants durable advantage without owning people.
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.
Konrad's experienced Daemon examines the proposed arrangement and reports that separation and dominance appear genuine. Konrad then authorizes reactivation of his people, hierarchy, programs, records, and infrastructure. Because the separation is false, reactivation places them inside Samuel's actual containment sphere. The precise false evidence, Daemon failure, and timing of control remain unresolved.
performed vulnerability → false autonomy offer → Daemon verification → Konrad authorization → reactivation → hidden attachment
These constraints inherit their source status. A working physical model, timing estimate, or accepted macro constraint does not establish every implementation detail.
Modules: 07, 09, 10. 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.
Which single action changes Samuel’s authority when Konrad reactivates the group?
AUTHOR-ACCEPTED: Konrad's authorization of reactivation is the legible hinge that attaches the revived system to Samuel's hidden hierarchy.
PROPOSED: Konrad registers an apparently separate domain as a child of Samuel’s existing sphere. Clean hierarchy; danger is overbroad automatic inheritance unless protected domains stay explicit.
PROPOSED: Konrad delegates restoration services while retaining political authority; administrator visibility enables later compromise. Plausible gradual capture; the legal distinction must matter in scenes.
PROPOSED: A crisis authorizes Samuel across several domains temporarily; dependencies survive the mandate. Strong political causality; avoid emergency-rule cliché and explain failed expiry.
PROPOSED: Conflicts between the two domains go through Samuel’s earlier Primary standing. Preserves genuine Konrad authority; slow bureaucratic leverage needs one decisive scene and protected appeal.
Non-canon situation: Konrad completes a restoration step to activate his lineage archive; an innocuous authority line later becomes the historical exhibit the inner circle recognizes.
Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives.
Module: 11 · Exact takeover lock
Gate: Which single action changes Samuel’s authority when Konrad reactivates the group?
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:docs/faction.html, the matching source in 05 Public/Atlas/, and the workshop projection.SC-001 Question 5 names Samuel Jr. in the activation-related government takeover; current character/history notes place Samuel and George in the prewar attempt and Samuel Jr. later. Confirm the actor before locking the permission sequence. Do not silently correct an accepted task packet.