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.

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 completed workshop records ten consequential decisions.

    Each answer establishes a cause, character choice, relationship, world rule, or event while keeping exact scene work visible.

    Review the ten decisions
  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.

615 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, workshops, and research already operate.
  • Needs repair Current-state agreement, automatic checks, and decision updates still drift.
  • 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

Needs repair

  • One trustworthy current-state view
  • Automatic checks before a change is merged
  • Shared labels and stable record identifiers
  • Updating every affected note after a decision
  • Keeping the weekly cycle current
  • Clearer boundaries around older folders
  • A cleaner split between the repository and the live site

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. Make builds and checks reliable.
  2. Create one trustworthy current state.
  3. Normalize the records for one small complete path.
  4. Connect accepted decisions to every affected file.
  5. Prove one complete path from conversation to approved manuscript material.
  6. 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, a criminal already held inside the containment process.

The current story problem Make the formal separation, rapid financial collapse, processing, exposure, and accepted placement feel inevitable.

Read the current story assessment

10 / 10major story problems resolved

Current development pass100%
100%
Current sweep
Reassessment
Current task
RW-01
  1. 01 Reassessment
  2. 02 Causal sequence
  3. 03 Character agency
  4. 04 Systems + evidence
  5. 05 Scene design
  6. 06 Draft

Story files

Browse the files used to develop the story.

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

Current document 01 Sessions/Daily/2026-09-11 - RW-10 Permanent Empire Bait.md

RW-10 Permanent Empire Bait

Question explored

Which unresolved human question sends the reader from Book One into the earlier history?

Author decisions

Established: the primary group of real leaders deliberately baited Konrad's contained leadership with a genuine possibility. If they teamed up with Samuel and successfully took Sylvan under the governing rules, they would gain permanent control of the largest empire.

Established: the prize is limited to the largest empire. It does not include the colonization planet as a whole, the overall colonization process, the larger humanity, or authority to rewrite the process rules.

Established: when the attempt to take Sylvan fails, the permanent-imperial path closes. The group's only remaining constructive option is to stop the rampage and cooperate with Sylvan and the legitimate leaders in order to receive control of a city.

Established: the deadline for taking Sylvan is Sylvan's forty-second birthday. If the group has not completed the governing victory condition by that birthday, the permanent-largest-empire path fails and closes.

Established: this supersedes the earlier active description of the Sylvan victory condition as wholly false and the description of cooperation as the only path from the beginning. Samuel's unsupported fantasy of using Sylvan to unlock the planet and conquer the wider process remains false. Any promise that the failed imperial opportunity can still be recovered is also false.

Established: Samuel gets Konrad to remain in containment by lying about what Sylvan and his new-generation Luminai really are. He makes the genuine imperial bait appear achievable on terms Konrad's worldview and older Daemon can dominate. Konrad's confidence that his Daemon can contain Samuel and outperform the successor bond remains part of the choice, but Samuel's false account of Sylvan and the Luminai is what turns that confidence into continued participation.

The primary leaders make the bounded imperial prize real because a merely imaginary offer would prove less. Konrad, Samuel, George, and the older group leaders receive a consequential opportunity to reveal what they choose when domination appears genuinely obtainable. Their failure therefore cannot be dismissed as resistance to a reward that never existed.

Reverse-series handoff

Book One resolves Samuel's present action, but exposes an earlier choice that later books must dramatize:

Why did the primary leaders offer the contained group permanent control of the largest empire, and what did each leader choose when the bait became real?

Readers know the group ultimately fails. The unresolved drama is how the offer was constructed, why the real leaders considered it safe and necessary, what Samuel told Konrad about Sylvan and the Luminai, why Konrad accepted Samuel as the required partner and stayed in containment, which members participated or resisted, and which choices created the century-long path to Sylvan.

Preserved boundaries

  • Samuel never controls the overall process.
  • The real leaders and embedded process rules remain above the bounded imperial contest.
  • Samuel's living-god fantasy and proposed conquest of the planet and larger humanity have no sound mechanism.
  • Sylvan's forty-second birthday is the fixed deadline. Failure by that point closes the imperial route; it cannot be restored through escalation, reinterpretation, or another bargain.
  • Cooperation after failure offers a city, not the largest empire.
  • The exact false description Samuel gives Konrad of Sylvan and the Luminai remains unresolved.
  • The exact legal transfer condition, meaning of “take Sylvan,” deadline-time convention, city-placement terms, safeguards, and reason the leaders could safely make permanent imperial control available remain unresolved.
  • The story grounds culpability in voluntary conduct, coercion, ideology, and responsibility rather than mental illness, identity, ancestry, or harmless interests.

Vault impact