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 01 Sessions/Daily/2026-09-06 - Workshop Module 01 Purpose Draft.md

Workshop Module 01 — Purpose Draft

Gate

What primary civilizational result must this particular process deliver?

Author answer — verbatim

A more effective integration wirelessly with advanced ai (Luminai) resulting in a more effective human and a more effective containment process for contained criminals, and a sustainable abundance of resources on a planet that started out barren, without having to constantly supply the planet with new resources, training containment and sustainable resources for substantial populations

Exact restatement — author-accepted

This colonization process must develop a self-sustaining civilization on a planet that began barren, capable of supporting substantial populations without continuous deliveries of new resources from outside the planet. Within that environment, training and containment serve as real-world conditions for developing a more effective wireless bond between humans and advanced Luminai. That bond should improve what the human–Luminai pair can perceive, learn, decide, and accomplish while making the containment of dangerous criminals more effective.

Here, “more effective human” means greater practical capability through the bond. It does not establish greater moral worth or automatic fitness to govern.

Workshop interpretation

  • Selected direction: a modified combination of option 1, option 2, and option 3, plus planetary resource independence as an additional required result.
  • Unifying purpose: prove a sustainable planetary civilization that can train large populations, contain dangerous participants, and develop human–Luminai cooperation under real conditions.
  • Why the combination matters: technical bonding, containment, training, and material sustainability validate one another. A bond proven only in a laboratory would not prove that a population can live with it. A sustainable planet that cannot train or contain its participants would not complete the process.
  • Option 4 status: accountable governance remains relevant but is not yet established as this module's primary result.

Scene test — non-canon

An official offers Sylvan a declaration of technical success because the Luminai bond worked. The planet still depends on regular outside resupply, or the containment system still produces preventable harm. Sylvan rejects the declaration as incomplete. The decision tests whether success belongs to one bonded pair or to the whole civilization the pair must help sustain.

Adversarial result

Permanent isolation could prevent Samuel from acting, but it would not accomplish the broader purpose. The process also has to develop human–Luminai cooperation, train substantial populations, test accountable containment under real social pressure, and sustain civilization on a formerly barren planet.

Remaining uncertainty

  • Which observable measures define a “more effective” human–Luminai pair?
  • Which resources must be closed-loop, regenerated, or produced locally?
  • How much outside input is compatible with “self-sustaining”?
  • Which safeguards make improved containment legitimate rather than merely more powerful?
  • Does this world complete these outcomes or authorize the next deployment stage?

Compound Writing adaptation test

Tracks pass

The restatement contains no outline labels, critic instructions, option menus, or narration about the writing process. The workshop interpretation remains outside the proposed canon statement, where its development scaffolding is useful. The pass recommends no deletion from the restatement.

Pressure-turn placement

The original answer begins with wireless Luminai integration and introduces sustainable planetary abundance later. The pass identifies the larger civilizational result as potentially buried: the planet must become a self-sustaining training and containment civilization for substantial populations. The restatement therefore leads with that planetary result and then explains how Luminai integration, training, and containment operate within it.

This is a useful change because it clarifies hierarchy without changing the author's ideas or forcing an unresolved mechanism into canon.

Decision state

AUTHOR-ACCEPTED — the author confirmed that the exact restatement captures the decision on 2026-09-06.

The accepted result may now be promoted through the affected canonical notes and website projections. This supporting workshop decision does not complete or replace SC-010.