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 07 Coordination/Weekly Synthesis/CURRENT-WEEK-INTAKE.md

Current Week Intake

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.

This is an intake index, not a TODO list or work queue. It exists so useful discoveries made during the week cannot disappear before the next Weekly Story Synthesis.

The author's only story-development execution list is the checklist named by Current Weekly Completion TODO and shown on the public Story Completion dashboard.

The active author work cycle runs Sunday through Thursday. Thursday's work is included, then the full synthesis runs Thursday night in America/Los_Angeles. Its approved checklist becomes the execution list for the next Sunday–Thursday cycle. Material captured after the Thursday cutoff belongs to the next intake window.

Capture rule

  1. Record the actual brainstorm, decision, contradiction, research result, or new idea in a dated 01 Sessions/Daily/ note first.
  2. Use an 08 Story Loop/Brainstorms/ packet when a current completion task needs focused author questions or alternatives.
  3. Add one short intake signal below only when the new material may change completion scope, order, dependencies, validation, or the next weekly synthesis.
  4. Do not add checkboxes, priorities, due dates, or a working order here.
  5. Return to the current completion TODO after capture.

The weekly synthesis must also inventory files changed since its prior cutoff. This index is a safeguard and routing aid, not the only evidence source.

Intake signal format

YYYY-MM-DD — Neutral label

  • Source: link to the dated session, brainstorm, research note, QA record, or changed story note
  • Type: idea / decision / contradiction / research / dependency / maintenance / public-development
  • Possible relationship: existing SC-###, existing priority, or unknown
  • Signal: one factual sentence describing what may need reconciliation

Do not propose execution wording here. The weekly synthesis decides whether a signal is already covered, changes an existing task, becomes a new task, remains open with a revisit trigger, or requires no TODO change.

Signals awaiting the next synthesis

2026-09-07 — Encoded patterns and manufactured historical evidence

  • Source: 01 Sessions/Daily/2026-09-07 - Encoded Patterns and Manufactured Historical Evidence
  • Type: decision / research / dependency / structural-development
  • Possible relationship: SC-002, SC-005, SC-009, SC-010, SC-014, SC-020, SC-026
  • Signal: The author established individualized wireless direction and human–AI interpretation under adversarial false framing, with George White as the central corrupted-validation example, and established that apparent physical history is produced within terraforming and civilization construction; exact encoded layers and historical-evidence mechanics remain open.
  • Additional direction: Religious organizations are managed by synthetic extensions of the process AI at different awareness levels, allowing the real leaders to explore the larger humanity's religious beliefs; consent, disclosure, freedom, research limits, and manufactured-consent safeguards require development.
  • Information absence: Synthetics never identify themselves as synthetic, and no information identifying religious organizations as synthetically managed exists within the colonization planet's available information environment; this supersedes a hidden-secret framing and requires external accountability.

2026-09-06 — Workshop Modules 08–20 accepted in one batch

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Modules 08-20 Batch Integration
  • Type: decision / dependency / contradiction / public-development
  • Possible relationship: SC-003, SC-004, SC-007 through SC-020, SC-026
  • Signal: The completed causal pass establishes embedded rules, Konrad's false bargain and reactivation, the two-planet George bridge, Sylvan–Orzai partnership and House qualification, declining Samuel influence, comparative inner-circle recognition, a scapegoat-and-deal endgame replacing literal Luminai theft, procedural finality, and flexible later-book order.

2026-09-06 — Workshop Module 07 environment commitment accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 07 Environment Commitment Draft
  • Type: decision / dependency / governance
  • Possible relationship: SC-003, SC-007 through SC-010, SC-015, SC-018, SC-019
  • Signal: The author established that participants cannot use advanced capability to abandon, skip, replace, or rewrite an assigned environment while remaining in the process. Voluntary heirs retain whole-process exit by surrendering the unfinished result; convicted-participant release remains separate.

2026-09-06 — Workshop Module 06 multi-year bond development accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 06 Bond Development Draft
  • Type: decision / dependency / structural-development
  • Possible relationship: SC-007 through SC-010, SC-015, SC-018, SC-026
  • Signal: The author established multi-year adversarial learning loops as the recurring cost of Sylvan's deeper bond. Advanced systems provide opportunities to observe, adapt, minimize later harm, and survive; each environment teaches something new while accumulated learning carries forward.

2026-09-06 — Workshop Module 05 managed successor capability accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 05 Deeper Integration Draft
  • Type: decision / dependency / public-development
  • Possible relationship: SC-010, SC-018 through SC-020, SC-026
  • Signal: The author established deeper successor integration as a substantial general capability advantage proved under adversarial containment, followed by managed normalization and integration into a humanity that includes people without the successor bond. Capability does not create moral superiority or automatic authority.

2026-09-06 — Workshop Module 04 customized reconstruction accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 04 Reconstruction Draft
  • Type: decision / dependency
  • Possible relationship: SC-002, SC-005, SC-009, SC-020, SC-026
  • Signal: The author established that reconstruction uses technological changes, a Great War era, and public roles from the larger humanity's real history but customizes them for process effectiveness while preserving participants' ability to change the resulting history.

2026-09-06 — Workshop Module 03 self-placement accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 03 Placement Draft
  • Type: decision / dependency
  • Possible relationship: SC-004, SC-010, SC-019, SC-026
  • Signal: The author established extensive qualification assessment followed by human–Luminai self-placement among paths opened by actual decisions and developed skills, replacing arbitrary assignment by the older leaders; high performance can open a major House or group placement with substantial resources and colonization involvement.

2026-09-06 — Workshop Module 02 voluntary entry accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 02 Entry Draft
  • Type: decision / dependency
  • Possible relationship: SC-003, SC-004, SC-010, SC-019, SC-026
  • Signal: The author established that legitimate heirs voluntarily choose a self-made process path instead of inheritance and may exit at any time by trading away the unfinished process result; criminal containment and descendant rights remain separate open systems.

2026-09-06 — Workshop Module 01 purpose accepted

  • Source: 01 Sessions/Daily/2026-09-06 - Workshop Module 01 Purpose Draft
  • Type: decision / dependency / public-development
  • Possible relationship: SC-010, SC-018 through SC-020, SC-026
  • Signal: The author established a population-scale purpose combining a self-sustaining civilization on a formerly barren planet with training, improved criminal containment, and more effective wireless human–Luminai integration.

2026-09-03 — Bridge world and reverse-discovery foundation

  • Source: 01 Sessions/Daily/2026-09-03 - Bridge World and Luminai Initialization Integration
  • Type: decision / dependency / contradiction / public-development
  • Possible relationship: SC-004, SC-007 through SC-010, SC-018 through SC-020, SC-026
  • Signal: The author established a successor-Luminai bridge world, Konrad's Daemon challenge and voluntary postwar continuation, Samuel's worst-case containment role, two rival criminal ecosystems, a final-years outcome presentation, and Book One beginning near the chronological end.

2026-08-26 — Five-report endgame research integration

Weekly reset

At the next synthesis:

  1. close the intake after Thursday's work and create a run dated for that Thursday;
  2. copy every signal into that run's 13 Weekly Intake Reconciliation.md;
  3. reconcile it against the current completion TODO, task registry, dependencies, QA, and changed files;
  4. obtain author approval for any replacement completion TODO;
  5. update CURRENT-COMPLETION-TODO only after approval;
  6. reset this file for the next Sunday–Thursday cycle without deleting the reconciliation record from the dated run.