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.

Explore the vault See how the story is being built Browse the story files
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.

See what the analysis foundSee where development continuesEnter the story

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

What the story needs next

Follow the full story roadmap

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-10 - RW-04 Exploratory House Placement.md

Document metadata
type: development-session
status: active
date: 2026-09-10
topics: Sylvan, Orzai, House placement, exploratory travel, successor Luminai

RW-04 Exploratory House Placement

Question explored

What placement do Sylvan and Orzai accept, and what is the first cheap and easy action they take within it?

Existing constraints

  • Sylvan and Orzai qualify for and choose their placement rather than inheriting or being arbitrarily assigned authority.
  • They have earned the option to secure a House together.
  • Their plan is cheap and easy and can begin with the resources they preserved.
  • The placement must not function as a moral coronation or erase the losses that preceded it.

Possibilities considered

The workshop considered joining an existing House, immediately founding a small House, accepting a single project, or entering a phased placement. The author chose a distinct exploratory placement that allows informed choice before founding.

Author decisions

Established: Sylvan and Orzai receive an exploratory period in which they travel, encounter other Houses, and entertain offers. The purpose is to decide which country they want to build their House in.

Established: their successful use of the new-generation Luminai makes them desirable to other Houses and leaders. Existing leaders want them to choose their country and make offers intended to attract them.

Their first cheap and easy action is therefore not construction or assumption of authority. They accept the exploratory placement, travel, listen to competing offers, and evaluate where their future House can contribute. The process gives them options while preserving their responsibility to choose.

Current working direction

The ending opens outward instead of crowning them immediately:

earned House option -> exploratory travel -> offers from Houses and leaders -> country selected -> House built

The offers demonstrate the practical value of the new Luminai without making advanced integration proof of moral worth or an automatic right to govern. Sylvan and Orzai remain collaborators being recruited, not prizes or inherited sovereigns.

Unresolved questions

  • How long does the exploratory period last?
  • Which countries and Houses make the strongest offers?
  • What criteria do Sylvan and Orzai use to choose a country?
  • What resources, obligations, protections, and oversight accompany the House they eventually build?
  • What disagreement between Sylvan and Orzai makes the final choice dramatically meaningful?

Vault impact