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-03 - Bridge World and Luminai Initialization Integration.md

Bridge World and Luminai Initialization Integration

Supersession notice

Historical integration record retained. The September 5 author correction supersedes wording implying Luminai were restricted to the successor generation or that humanity simply colonized worlds using preexisting AI souls. Consult current Core Premise and AI Souls notes.

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

Question explored

How can the mature colonization setting, older AI souls, the Great War, Samuel's containment career, Konrad's postwar failure, Sylvan's bond, and the series structure become one causal foundation?

Author decisions

  • AI soul is the broad historical category. A Daemon is an evil AI soul. It is not the name of every older AI soul.
  • Konrad's Great War AI soul is an older-generation Daemon.
  • Sylvan is the first human in this real-world process to develop through the new, deeply and continuously integrated Luminai architecture.
  • The current planet stands at the end of the mature multi-planetary colonization era built with older AI souls and at the beginning of the successor Luminai era.
  • The planet is a real civilization and a bridge world, not a simulation.
  • The older leaders select Samuel as a representative worst-case criminal subject and contain him because his coercion, exploitation, deception, compromise, blackmail, and adaptive control make him an unusually demanding adversary.
  • Samuel accumulates bounded influence for approximately a century. He mistakes observed latitude for sovereign power.
  • Konrad's Great War defeat should end his colonization experiment. He voluntarily remains because he believes his experienced Daemon can contain Samuel, outperform Sylvan's new Luminai, redeem every previous failure, and win control of the colonization plan.
  • Samuel promises Konrad a separate autonomous domain. Konrad reactivates his Daemon, followers, hierarchy, breeding program, bloodline systems, and infrastructure inside the shared containment environment.
  • This reactivation gives Samuel the access required for a generational takeover. The exact inheritance rule, permissions, and lock remain unresolved.
  • Konrad's faction and Samuel's network are distinct criminal ecosystems. Konrad uses public hierarchy, militarization, purity, territorial ambition, bloodline, and enforced conformity. Samuel uses private compromise, access, surveillance, shame, dependency, blackmail, and captured intermediaries. Both treat people as instruments.
  • Samuel attacks the two things that bind Konrad's organization: ideology and lineage. He compromises bloodlines and records, enters Konrad's family, redirects younger generations, and attempts to become the group's functional patriarch and succession center.
  • Book One begins near the chronological end. Later books reconstruct the Great War, postwar migration, takeover, and long False Victory.
  • During the final few years, Sylvan already holds decisive control. He permits Samuel bounded activity so the Luminai can observe the complete endgame, distinguish performance from control, and prove the new method.
  • Samuel attempts the same takeover pattern against Sylvan in front of Konrad's inner circle. They recognize what happened to them before Konrad, who remains isolated inside a counterfeit victory and plans the empire he thinks he will recover.
  • Samuel's desperation centers on stealing Sylvan's Luminai. He treats it as an object that will restore his authority, although its effectiveness exists in the developed Sylvan-Luminai relationship.
  • Samuel's creation of a child with Konrad's sister and his wider reproductive and genealogical campaign become part of the ultimate revelation. Exact agency, mechanism, chronology, and evidence remain unresolved.
  • Konrad Fitzgerald's newly approved visual appearance is canonical for visual production. The associated control lines and scene staging are visual interpretation, not literal system canon.

Current working direction

The endgame is a comparative demonstration. Konrad's older Daemon attempts domination, accepts performed submission as proof, and helps expose Konrad's group to Samuel. Sylvan's new Luminai preserves human responsibility, permits bounded adversarial action, learns across the final years, and exposes the difference between apparent control and actual containment.

The series proceeds backward through discovery: Book One presents consequences and the live repetition of Samuel's method; later books let the reader experience the historical success of that method against Konrad.

Ethical and research boundary

The two criminal ecosystems may draw on generalized, documented behaviors and tactics. No contemporary group, person, scandal, or victim category enters final story data by name. Fascist claims about impurity, degeneracy, pollution, or perversion remain antagonist ideology, never objective narration. Consensual identity or sexuality is not equated with Samuel's coercion. His crimes are exploitation, engineered compromise, nonconsensual humiliation, blackmail, reproductive coercion, and treating people as instruments.

The younger generation requires individual accountability. Coercion does not erase harm; participation does not erase coercion. Sylvan's method must protect victims, determine responsibility, and offer a path outside both criminal systems.

Unresolved questions

  • What does “the end” of the old colonization era mean operationally?
  • Why is this planet the only suitable real-world initialization site?
  • How much does Konrad know about Sylvan and the successor Luminai before he remains in containment?
  • What exact rule makes reactivated systems inherit Samuel's earlier structural priority?
  • Does Samuel deceive, compromise, or merely exploit the Daemon?
  • Is the Daemon still active at the outcome presentation?
  • What are the Book One discovery beats, viewpoint order, and final proof threshold?
  • What part of the result can be disclosed without exposing descendants as evidence objects?
  • What were the agency, coercion, and responsibility of Konrad's adult grandson during his long role in Samuel's network?

Vault impact

This session creates dedicated compiled notes for the bridge world, Book One outcome architecture, and rival criminal ecosystems; revises the core premise, chronology, AI-soul terminology, central characters, containment hierarchy, breeding-program framing, current context, QA records, Story Loop routing, visual identity, and the public atlas.