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 current workshop asks one consequential 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.

Vault overview

See the whole story-development system at a glance.

605 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 that wait for an answer
  • 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

0 / 10major story problems resolved

Current development pass0%
0%
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 605 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

Current document 05 Public/Atlas/characters.md

characters

Sylvan

Sylvan develops the new deeply integrated Luminai bond. The existing modern arc begins with a creative-development startup, sabotage, loss, and movement through increasingly hostile environments before the final reversal.

His task is larger than technical mastery. He and Orzai must resist Samuel's attempt to make each appear irrational to the other, preserve independent judgment inside intimacy, and survive until formal separation. They ultimately accept the placement they earned instead of trying to control the process.

Orzai

Orzai is a developing leader and Sylvan's partner, with her own interests in health, nutrition, creative design, and training systems. Her choices must matter independently of his success.

Their Luminai coordination cannot replace trust, consent, disagreement, or repair. They meet inside the same environment, choose partnership under attack, complete separate human–Luminai bonds, and earn a placement they can begin cheaply with the resources they preserved.

Konrad Fitzgerald

Konrad wants his ideology vindicated and his authority restored. He believes accumulated experience in his daemon can prove that he deserves to lead. One decisive victory, he thinks, will turn every earlier failure into preparation.

His approved appearance is locked. The portrait establishes identity, not a new scene or an additional story fact.

Samuel Franklin

Samuel builds private dependencies through manipulation, surveillance, compromise, blackmail, and isolation. He remains physically contained on the previous planet and must act into Sylvan's world through George and permitted connections.

When his control collapses, he blames George, reaches toward Samuel Jr., and tries to sell Sylvan another false bargain. His actions, rather than a real-person analogy, define the character.

George and the supporting cast

George can participate directly on the new colonization planet; Samuel and the older contained criminals cannot. That physical distinction makes George the operational bridge rather than another version of Konrad's isolated fantasy. Samuel ultimately attempts to make him absorb the blame.

The Witness, Orzai's family, Samuel's replacement heir, descendants, and survivors must carry choices and evidence that cannot all be delegated to Sylvan.

Spoilers: recognition is not the same as accountability

Konrad's inner circle recognizes Samuel's repeated takeover method before Konrad does. Some participants may be collaborators, some coerced, and some both at different times. Knowing the truth does not automatically settle culpability or repair harm.

The workshop tests each role through decisions the character can make, resist, or regret. The current reassessment workshop separates George's and Konrad's endgame functions from Samuel's terminal collapse.

Sources: 03 Context/CAST, 02 Story/Characters/Konrad Fitzgerald, 02 Story/Characters/Samuel Franklin, 02 Story/Components/Book One Outcome Presentation and Reverse Discovery.