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 QA/Migration Ledger.md

Document metadata
type: migration-ledger
status: complete
updated: 2026-09-03

Migration Ledger

September 5 implementation intake

The foundation audit, shared website projections, and twenty-module workshop were implemented for review. No story answers were invented and no new publication authorized. See 07 QA/2026-09-05 - Comprehensive Story Assessment and 07 Coordination/2026-09-05 - Website Rebuild Handoff for verification and remaining deployment work.

Source: 01 Sessions/Daily/2026-09-05 - Integrated Foundation Audit and Workshop Build.

Carried forward

  • Core colonization, containment, and cultivation premise
  • Planet, moon, synthetics, awakening, influence, AI-agent, scoring, identity, and schedule systems
  • Throne and Wakeful mechanisms
  • Witness, Inheritor, and unresolved first-person Protagonist designs
  • Recurrence, erosion, solvency pressure, public phase change, and costly-victory structure
  • Tone, narrative method, safety rules, and unresolved questions

Deliberately excluded

  • All raw and cleaned transcripts
  • Sensitive mapping material
  • Extraction schemas, queues, agent logs, and deprecated pipeline instructions
  • Empty public-bible scaffolding
  • Direct real-world historical models and identity coding
  • Any implication that an inherited working name is final

Archive policy

The archived vault remains the historical source and is not part of routine AI context. Useful old concepts enter this vault only when the author deliberately restates or approves them.

The iCloud mobile vault is a separate private capture queue. Historical figures may remain there as private development analogies, but only author-approved abstractions and freshly invented story material enter this repository.

2026-09-03 foundational migration

  • Integrated the 2026-09-02 mobile premise handoff into dedicated bridge-world, Book One, and criminal-ecosystem notes.
  • Reclassified AI soul as the broad historical category, Daemon as an evil AI soul, and Luminai as Sylvan's successor generation.
  • Reordered the public series architecture so Book One begins at the outcome and later books reconstruct the Great War and takeover.
  • Preserved older forward chronology as historical dependency rather than required narrative order.
  • Promoted Konrad's voluntary postwar continuation, Daemon challenge, redemptive delusion, false autonomous group, and reactivation as the causal hinge into Samuel's takeover.
  • Preserved the accepted alpha/beta permission model while leaving detailed weighting, registration, evidence, and reset limits unresolved.
  • Reframed faction opposition through invented behaviors and tactics, excluding direct contemporary analogies and refusing fascist purity language as neutral description.
  • Reclassified the George-centered final environment as a subordinate thread requiring reconciliation with the new Samuel-Konrad outcome presentation.
  • Added the approved Konrad appearance anchor to the visual system without treating symbolic scene details as story canon.