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-11 - Book One Buildability Assessment.md

Book One Buildability Assessment

Assessment result

The story's ending is now substantially stronger than its path to that ending.

The vault can explain what ultimately happens, why Samuel fails, why Sylvan and Orzai succeed, and why the result matters to the larger humanity. It cannot yet produce a dependable Book One scene list without inventing major causal material during drafting. That is the next bottleneck.

The most valuable next pass is therefore not another general reassessment. It is a Book One architecture workshop that converts the accepted ending into a dramatic objective, countdown, chain of choices, evidence progression, and sequence map.

What is already strong

AreaCurrent strength
Terminal causalityQualification, separation, the $15 million attempt, genuine failure, processing, exposure, and placement have a governing order.
Thematic contrastSamuel needs limitless control; Sylvan and Orzai succeed through bounded cooperation, reality contact, and acceptance of a legitimate result.
Institutional meaningThe process tests conduct under a genuine opportunity and produces evidence relevant to larger moral debates.
Reverse-series engineThe real offer of the largest empire and Samuel's lie to Konrad create a consequential earlier history to uncover.
Constructive endingSylvan and Orzai leave Samuel's conflict, travel, consider offers, and choose where to build their House.

Sources: 07 Coordination/Story Completion Workflow/Reassessment Workshop/README, 02 Story/Components/Book One Outcome Presentation and Reverse Discovery, 02 Story/Systems/Competitive Environments - Control Inversion and Sylvan Endgame.

What prevents scene construction

1. The contest has a prize and deadline but no exact victory condition

“Take Sylvan” is not yet a playable story rule. Until the story defines what must happen to Sylvan, what must remain voluntary, what evidence certifies success, and why the offer is safe, readers cannot measure progress or understand the failure at forty-two.

2. Samuel's lie is functional but not dramatized

The lie explains why Konrad remains, but its content, supporting evidence, and breaking truth are open. This prevents the reverse mystery from having a specific false proposition that scenes can confirm, strain, and overturn.

3. The birthday is a date, not yet a dramatic clock

The vault needs to establish when Book One begins relative to the birthday, who knows the deadline, who misunderstands it, and how pressure becomes visible without repetitive countdown exposition.

4. There is no selected opening event

The current vault contains several viable entry points but no author-accepted opening viewpoint, ordinary situation, first disturbance, or promise to the reader. A strong ending cannot compensate for an undefined beginning.

5. The middle has capacities but not indispensable episodes

RW-08 defines what Sylvan and Orzai learn—resource discipline, independent cooperation, and reality-and-ethical anchoring—but not the events that teach those capacities. Without a small causal ladder, the long process risks reading as repeated pressure rather than development.

6. Sylvan and Orzai's final unity lacks a mapped relationship arc

Their ending is emotionally promising, but the story still needs disagreements, independent actions, costs, and repaired trust that make Orzai's final leadership and Sylvan's acceptance feel earned.

7. Exposure lacks an audience-and-revelation sequence

The story knows that complete conduct is presented while privacy is protected, but not what George, Konrad, affected groups, Sylvan, Orzai, and the wider public learn first. Evidence without revelation order becomes explanation rather than drama.

8. George and Konrad have functions but not final choices

George is Samuel's intended scapegoat, and Konrad is forced into reality with substantial influence. Their consequential decisions remain open, so the climax currently acts upon them more than it resolves their agency.

9. Book One has no executable sequence contract

The manuscript directory is correctly empty because the structure is not ready. The next workshop should finish with a compact sequence map that can feed scene packets without silently inventing new canon.

Sources: 06 Draft/Scenes/README, 06 Draft/Manuscript/README, 02 Story/Characters/George White - The Collapse of the Lie, 02 Story/Characters/Konrad Fitzgerald, 02 Story/Characters/Orzai.

Ranked next-work priorities

RankWork areaWhy nowOutput needed
1Exact “take Sylvan” ruleGoverns every antagonist action and the terminal failure.Observable success/failure contract.
2Samuel's lie to KonradGives the reverse mystery a precise false belief.Lie, evidence, concealed truth, breaking point.
3Birthday countdownTurns macro causality into pressure.Start distance, knowledge map, visible thresholds.
4Opening frameGives the reader a human entry into the system.Viewpoint, ordinary objective, disruption, first discrepancy.
5Middle causal ladderMakes training and endurance cumulative.Four to six indispensable episodes.
6Sylvan–Orzai relationship arcEarns their shared ending and preserves independent agency.Disagreements, costs, repair, leadership transfer.
7Evidence and presentation orderMakes exposure dramatic and fair.Audience layers and revelation sequence.
8George's final choicePrevents him from being only a scapegoat mechanism.Choice, cost, evidence effect, accountability.
9Konrad's final moveConverts a century of false reality into consequence.Decision using his retained influence.
10Book One sequence contractConverts answers into buildable story architecture.Ordered sequences, transitions, reveals, open scene questions.

Dependency logic

The objective must be defined before the lie can be precise. The objective and lie determine who understands the birthday clock. Those three decisions constrain the opening. The opening establishes the promises the middle must fulfill. The middle then earns the relationship turn and creates the evidence used by George and Konrad. Only after those choices exist should the workshop lock a sequence map.

What this workshop intentionally postpones

  • Complete reverse chronology across every earlier book.
  • Exhaustive governmental, religious, economic, and technical worldbuilding.
  • Exact chapter count and prose drafting.
  • Every House offer and the complete post-Book-One placement system.
  • Full civilizational findings from the completed planet.
  • Detailed daily accounting of Samuel's final $15 million unless the sequence map proves it is needed now.

These are not unimportant. They are simply less constraining than the missing Book One spine.

Proceed through 07 Coordination/Story Completion Workflow/Book One Architecture Workshop/README one author gate at a time. Reassess after every accepted answer. Modules may be combined or retired when an earlier answer resolves them, but the final sequence contract must account for every dependency that remains.

The first question is:

What exact, observable condition would have counted as successfully taking Sylvan before his forty-second birthday?