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 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.

See what the analysis foundSee where development continuesEnter the story

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

What the story needs next

  • Terminal chain
  • Constructive ending
  • Proof and recognition
Follow the full story roadmap

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 07 Coordination/Story Completion Workflow/Reassessment Workshop/README.md

Document metadata
type: workshop-index
status: active
updated: 2026-09-09
assessment: 07 QA/2026-09-09 - Current Story Reassessment.md

Current reassessment workshop

This workshop replaces the unfinished remainder of the old 27-task question set. It begins from the current story and ending rather than trying to finish questions written for an earlier version.

It is adaptive. The author does not have to answer all ten modules in a fixed order. Each accepted decision can combine, remove, or reorder later work.

Priority 1 - Make the terminal chain inevitable

  • [ ] RW-01: Book One terminal sequence. Define the exact state change that makes separation inevitable.
  • [ ] RW-02: Samuel's rapid resource burn. Make the $15 million collapse within days materially credible.
  • [ ] RW-03: Processing and exposure. Establish how zero balance triggers processing and releases the record.

Priority 2 - Make the constructive ending tangible

  • [ ] RW-04: Sylvan and Orzai's placement. Define enough of the placement they accept for the ending to feel real.
  • [ ] RW-05: Orzai's indispensable action. Give Orzai one decision or contribution the ending cannot work without.

Priority 3 - Make the proof fair

  • [ ] RW-06: Bond and evidence authentication. Integrate theft resistance, provenance, and tamper detection into the terminal sequence.
  • [ ] RW-07: George and Konrad's distinct functions. Prevent their recognition arcs from competing with the Samuel separation climax.

Priority 4 - Make the middle earn the ending

  • [ ] RW-08: Employment-stage preparation. Connect resource discipline, group cooperation, and reality anchoring to terminal survival.
  • [ ] RW-09: Institutional accountability and repair. Decide what the leaders and process must admit, protect, and change.

Priority 5 - Make Book One launch the series

  • [ ] RW-10: Reverse-series handoff. Close Book One while creating dramatic questions for the earlier history.

Weekly completion gate

  • [ ] The terminal sequence has an established causal order.
  • [ ] Samuel's resource burn and zero-balance rule are set up before payoff.
  • [ ] Sylvan and Orzai's accepted future is specific enough to carry emotional closure.
  • [ ] Exposure protects victims and descendants while proving command responsibility.
  • [ ] The ending creates a compelling reason to enter the earlier books.

Current starting point

Start with 07 Coordination/Story Completion Workflow/Reassessment Workshop/01 - Book One terminal sequence. Ask one author question at a time. Record the answer in a dated session before promoting it.

Historical workflow

The old 27-task registry and the first twenty-module workshop remain available as development history. They are not active author-facing routes.