Project Explorer · working sheet

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.

Interpretive still life of recovered records aligned against hidden-system evidence.

Recovered records held against the working evidence.

Current project summary

A colonization world tests who can be trusted with power.

Seeds of the Throne is a science-fiction series about an interactive colonization planet built to create resources, support civilization, train people for greater responsibility, and contain dangerous criminals. The story begins near the end of a conflict that has been unfolding across generations.

The world
Planet Three is a mature containment-and-cultivation world. Its criminal empires have real local power, but they do not control the larger process or its outer limits.
The human future
Sylvan and Orzai form separate bonds with a new generation of Luminai, advanced artificial cognition integrated with an accountable human mind. Their choices test whether this partnership is ready for life beyond containment.
The central conflict
Samuel Franklin has spent decades controlling people by controlling the explanation around them. Sylvan, the Luminai, and an independent Resistance must reconnect the evidence Samuel divided across families, institutions, and generations.
The current endgame
Samuel promises George White and Aiden Fitzgerald the same godlike authority, aims them at each other, and applies an existing prophecy to Sylvan. Their supposed superweapon fails as Sylvan publicly exposes the con, the bloodline betrayal, and Samuel's manufactured reality.
The Resistance
Its black-and-orange ark represents sanctuary and the preservation of people, belief, culture, memory, testimony, and truth through persecution. It preserves what must survive without claiming a right to rule.
What is being developed now
The ending foundation is established. The live workshop is defining the exact superweapon mechanism, the evidence that breaks its credibility, and the independent choices that let the trapped leaders fight their way out against Samuel.

Read the story overviewRead the complete current stateRead the latest accepted decisionsOpen the current assessment

Black-and-orange Resistance infographic centered on an ark preserving people, belief, culture, memory, testimony, and sanctuary through persecution.
The Resistance. The ark preserves people and truth through persecution without claiming supremacy.
Infographic showing Samuel outside an altered reality, George White, Konrad Fitzgerald, Aiden Fitzgerald, and other leaders trapped inside it, and Sylvan standing outside their hierarchy as the leaders recognize Samuel as the deceiver.
Trapped inside Samuel's altered reality. The leaders recognize Samuel as the deceiver and must fight their way out against him.

Story development tools

See how the authoring system turns ordinary language into finished story work.

The Project Explorer shows the live notes, decisions, and workshop used to develop Seeds of the Throne. Each step keeps confirmed decisions separate from suggestions and unanswered questions.

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 Dynamic Story Workshop asks the one question that matters now.

    Each desktop assessment updates the baseline, records new decisions, checks compatibility, and replaces the next question when the answer changes the story.

    Open the current assessment
  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.

Vault overview

See the whole story-development system at a glance.

717 notes work together as one system. The vault remembers where ideas came from, what the author decided, what remains uncertain, and what should happen next.

The vault turns conversations into organized story memory. It preserves sources, separates decisions from suggestions, finds missing connections, supports research and workshops, prepares scenes and prose, checks continuity, and publishes selected material without surrendering author control.

  • Working now Capture, memory, one current workshop, research, and checked public projections operate.
  • Needs repair Decision impact reporting and full browser-size automation still require manual work.
  • Planned next Durable answers, manuscript production, and mobile save are not built yet.
  1. Capture

    Conversations, mobile notes, and raw ideas are preserved.

  2. Understand

    Current context and compiled notes explain what the project means now.

  3. Decide

    Workshops ask one important question and preserve the author's answer.

  4. Develop

    Research, alternatives, story structure, and focused tests strengthen the work.

  5. Create

    Scene plans, prose, images, and manuscript material are produced for review.

  6. Share

    Selected material becomes the story site, Project Explorer, and public posts.

What lives where

Each area has a job. Folder names are secondary detail.

  • New material

    Preserves incoming ideas and the order in which they developed.

    00 Inbox, 01 Sessions

  • Story memory

    Keeps the detailed working knowledge and a smaller briefing used to resume work.

    02 Story, 03 Context

  • Research

    Separates questions, reports, and usable findings from story decisions.

    04 Research

  • Public work

    Holds reviewed material prepared for readers.

    05 Public

  • Drafts

    Holds scenes and manuscript candidates awaiting review.

    06 Draft

  • Decisions and direction

    Records choices, contradictions, current work, handoffs, and verification.

    07 QA, 07 Coordination

  • Development tools

    Diagnoses missing connections and tests possible story directions.

    08 Story Loop, 09 Story Exploration

  • Reusable methods

    Provides repeatable methods for writing, research, images, websites, and checks.

    skills, scripts

What already works, what needs repair, and what is still planned

Working well

  • Idea and session capture
  • Human-readable story memory
  • Author authority and decision boundaries
  • Research kept separate from story truth
  • Workshop questions with preserved author decisions
  • Decisions, contradictions, and open questions
  • Visual identity and image controls
  • Markdown files and recoverable history
  • Searchable file access
  • One live dynamic workshop and a verified public projection

Needs repair

  • Shared labels and stable record identifiers
  • Automatic decision impact reports across every affected note
  • Keeping the weekly cycle current
  • Clearer boundaries around older folders
  • A cleaner split between the repository and the live site
  • A stable browser-test dependency for every required screen size

Planned next Not built yet

  • Durable integration of conversational answers
  • Automatic reports of what a decision would change
  • Complete scene-to-manuscript production
  • Manuscript assembly and export
  • Reliable mobile save, resume, and synchronization

The next build order

  1. Normalize the records for one small complete path.
  2. Automate the affected-file report for accepted decisions.
  3. Bundle reliable browser checks for every required screen size.
  4. Prove one complete path from conversation to approved manuscript material.
  5. Expand only after that path works.

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, while an independent resistance network reconstructs the history Samuel kept divided across people and systems.

The current story problem Define what made the supposed superweapon appear effective while Sylvan was severely disadvantaged and what verifiable change made it fail once he began publicly exposing Samuel.

Read the latest focused assessment

The project no longer treats a fixed checklist percentage as the live story state. The Dynamic Story Workshop carries one current assessment question and updates its baseline after every accepted answer.

Open the current assessment

Story files

Browse the files used to develop the story.

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

Current document 07 QA/2026-09-20 - Three-World and Reveal-Chain Canon Audit.md

Three-World and Reveal-Chain Canon Audit

Verdict

Compatible with targeted supersession and unresolved mechanical dependencies. The developments strengthen the existing colonization, containment, evidence, and endgame architecture. No accepted terminal outcome needs to be reopened.

Reinforced canon

  • Samuel never controls the governing colonization process; he converts bounded local power into a false sovereignty claim.
  • The same environment cultivates future leaders and exposes what dangerous people do when given consequential power.
  • Planet Three's mature institutions, archives, synthetics, off-world command structure, and adaptive criminals make it a credible human–Luminai proving ground.
  • Samuel captures structures through access, interpretation, dependency, succession, and compartmentalization rather than straightforward conquest.
  • Sylvan, the Luminai, and the Resistance win through connected evidence and accountable action rather than domination.
  • Konrad's commitment to expose Samuel remains locked and does not become redemption or subordination to Sylvan.
  • Protected evidence, public proof, individual accountability, and private descendant records must remain distinct.

Contradictions and required reframes

PriorityExisting wording or modelCurrent handling
HighSamuel Jr. is repeatedly called Samuel's preferred replacement heir and fallback continuity route.Supersede as objective canon. He may be presented or understood as an heir, but Samuel's controlling purpose is his testimony and symbolic existence in the mandatory presentation.
HighSome notes leave Konrad's final response open.His alignment is closed: he commits himself and his groups to Sylvan's separate exposure plan. Knowledge state, confession scope, timing, emotion, and consequence remain open.
HighThe Outcome Presentation can read as a special procedure applied only to Samuel.Reframe it as Samuel's part of a broader mandatory end-of-process presentation architecture. Exact scope and legal form remain unresolved.
HighThe largest-empire prize can read as the full scale of Samuel's desired victory.Preserve it as a real bounded offer to Konrad's group and as one capture route. Samuel's ambition expands across all Planet Three empire structures.
Medium“Two-planet endgame” and “previous/newer planet” lack stable numbering.Retain the two active locations but name them within the three-world map: Planet Two and Planet Three, subject to confirmation that the older containment world is Planet Two.
MediumThe Bridge World note leaves open whether Sylvan's planet is the final colony.Current direction: Planet Three closes the old construction/governance model; it need not end later physical expansion.
MediumCurrent context describes numerous earlier successful colonization planets.Supersede if this means numerous planets before Planet Three. Preserve the leaders' millennia of experience without inventing additional worlds.
MediumSamuel “becomes Konrad” through dynastic replacement.Reframe as capture of Konrad's structures, family history, institutional authorship, and interpretive authority. Literal legitimate succession is unnecessary.
MediumSamuel Jr.'s company chiefly preserves political control after George fails.Retain as a possible secondary use, but make evidence access, constructed testimony, and his ability to expose Samuel primary.
LowExisting Converging Revelation and the new reveal chain can appear duplicative.Distinguish them: Converging Revelation is the information effect; the reveal chain is the action-and-counteraction choreography that propagates it through the final act.

Redundancies to consolidate

  • The repeated statements that Samuel mistakes local access for control should be centralized in the Planet Three/process boundary and referenced elsewhere.
  • “George is the attack; Samuel Jr. is the fallback” is now too coarse. The cleaner distinction is: George supplies direct operational action on Planet Three; Samuel Jr. supplies testimony, institutional evidence, and the attempted authorship transfer.
  • The outcome presentation, public online story, protected evidence presentation, and mandatory participant presentations currently overlap without a hierarchy. They should become layers of one presentation system rather than four separate climaxes.
  • Konrad's disclosure choice appears in Resistance, Book One architecture, and endgame notes. The choice should remain locked once, while those notes develop different mechanics: evidence, first action, audience, and consequence.

Unresolved dependencies

  1. World identity: confirm whether Samuel and Konrad's “previous colonization planet” is Planet Two and whether anyone else acts across both locations.
  2. Empire taxonomy: distinguish parent-civilization empires, Planet Three surface empires, Houses, cities, and process jurisdictions.
  3. Authority: identify who requires presentations and what enforcement, appeal, privacy, and evidentiary rules govern them.
  4. Chronology: place Samuel Jr.'s birth, education, company rise, preparation, doubt, defection, and presentation against the Great War, containment century, and Sylvan's final years.
  5. Evidence: define what each actor uniquely supplies and what turns allegation into authenticated attribution.
  6. Causality: establish why Samuel's plan still needs Samuel Jr.'s testimony if the process possesses a governing record.
  7. Disclosure: decide the order in which Samuel Jr., Konrad, affected families, other empires, and formal evaluators learn and act.
  8. Safety: explain why the real leaders allow genuine local harm and empire capture without making the proving ground negligent or predetermined.
  9. Motivation: preserve self-interest, culpability, and ideology in Samuel Jr. and Konrad's turns; neither should become suddenly heroic.
  10. Aftermath: decide what happens to empire structures freed from Samuel and how Sylvan and Orzai's placement follows without making them automatic rulers.

Canon risk if left unresolved

The new ideas fail only if the story relies on labels instead of mechanics: “empire” without jurisdiction, “mandatory” without authority, “evidence” without custody, “disclosure” without audience or cost, or “defection” without a prior belief state. The Reveal Chain Mechanics Workshop now holds those author gates.