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-10 - RW-03 Processing Among the Terrorized Groups.md

RW-03 Processing Among the Terrorized Groups

Question explored

How does zero balance cause Samuel's processing and full exposure, and what does processing mean for him afterward?

Existing constraints

  • Zero balance causes immediate processing without another violation, hearing, bargain, or equalized phase.
  • Processing exposes Samuel's full conduct.
  • Exposure must establish command responsibility without turning victims and descendants into public exhibits.

Author decisions

Established: processing does not remove Samuel from the colonization process. After processing, he remains inside the process and is placed among the groups he terrorized.

Established: everything Samuel did is presented while he is still present within the process. The affected groups receive the connected account rather than isolated fragments that Samuel can explain differently to different audiences. He no longer controls the presentation or the story joining his actions together.

The author stated: “After processing Samuel is placed in the groups that he terrorized and everything that he did is presented, while he is still in the process.”

Established terminal procedure: when Samuel's independently funded plan reaches genuine failure, the process acts immediately under specific rules. Samuel is placed into a stasis-like coma. His Daemon is deleted at processing because continued Daemon existence requires the human to remain an active participant. Samuel therefore loses the extended intelligence that helped him sustain the war, divide audiences, and protect his godhood story.

While Samuel is unconscious, biological synthetics physically transport him to a location containing the older leaders of the contained criminal groups. He remains inside the colonization process but no longer holds active-participant status or a Daemon. The connected presentation of everything he did occurs there, leaving Samuel alone to face the people, record, and consequences he spent decades separating from one another.

Established legitimacy rationale: the real leaders allow Samuel the finite independent attempt because ending it prematurely would leave him able to claim that he could have succeeded. The bounded final opportunity proves through Samuel's own choices that he will not voluntarily stop. Processing follows demonstrated failure rather than the leaders merely predicting what he would do.

Current working direction

Processing is a physical and cognitive transition: failed plan, Daemon deletion, stasis-like coma, synthetic transport, awakening among the older contained leaders, and complete presentation. It is not escape from the process, disappearance, or a final punishment delivered somewhere outside the story world.

“Everything” governs the completeness of Samuel's conduct record. It does not yet establish that every victim's private identifying information is released to every unrelated public audience. The affected groups can receive the full connected truth while unnecessary wider exposure remains restricted.

Unresolved questions

  • What exact interface makes the final balance and failed-plan status visible before stasis begins?
  • What is the physical location containing the older group leaders, and how long does Samuel remain there?
  • What authority and protections do the affected groups possess when Samuel is placed among them?
  • Which presentation layers are visible to affected groups, institutions, and the wider public?
  • What prevents retaliation, renewed coercion, or Samuel turning the presentation into another performance?

Vault impact