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 docs/assets/workshop/16.md

16 · Suspense under decisive control

Purpose

Move uncertainty to bounded but consequential outcomes rather than faking a threat already excluded.

This packet supports the existing Story Completion Workflow. Its central gate was author-accepted on September 6. It does not answer SC-010 Question 7 or advance that checklist. Central synthesis: Astra, reviewed for integration on September 5.

Accepted result

Samuel cannot seize the conclusion, but George and Samuel can still threaten Sylvan and Orzai's relationship, evidence, judgment, safety, and eligibility for future placement. The pair must preserve independent agency, complete their bonds, protect other people, expose the historical system, and qualify for a House without abusing their growing advantage. These linked outcomes remain uncertain even though decisive control does not.

Relevant source notes

Confirmed facts and current working constraints

  • Sylvan’s decisive control in the final years is established.
  • Samuel and others misinterpret that control.

These constraints inherit their source status. A working physical model, timing estimate, or accepted macro constraint does not establish every implementation detail.

Unresolved gaps and contradictions

  • Reader knowledge; present stakes; local reversibility; costs that do not negate containment.

Prerequisite decisions

Modules: 13, 14, 15. Read their accepted results before closing this gate. Open prerequisites can be explored provisionally, but do not mark dependent choices final. Module numbers are topic IDs; use the dependency order in the workshop index.

Central author gate

Which outcome remains genuinely uncertain even while Samuel cannot seize the conclusion?

AUTHOR-ACCEPTED: personal, evidentiary, ethical, relational, and placement outcomes remain at risk even though Samuel cannot take the final process outcome.

Possibilities and tradeoffs

1. Attribution and defensible proof

PROPOSED: Containment can hold while a particular charge remains unproven. Strong archive thriller; justice cannot depend on proving every secret.

2. Human trust and voluntary cooperation

PROPOSED: People can reject Sylvan’s account or leave the process. Strong agency; disagreement must not be treated as system failure or villainy.

3. Privacy versus public credibility

PROPOSED: More revealing evidence could persuade faster but harm descendants. Strong concrete choice; establish alternatives beyond secrecy or total exposure.

4. Placement and institutional legitimacy

PROPOSED: Sylvan can win tactically and still fail to show the process deserves continuation. Large stakes; ground them in one affected life and one actual decision.

Targeted follow-up questions

  • What does the reader know before Samuel knows?
  • Which mistake can cost Sylvan something permanent without freeing Samuel?
  • What will Sylvan refuse to do merely to make the audience believe?

Scene test

Non-canon situation: A witness retracts permission to use decisive private material minutes before a public stage; containment remains sound but Sylvan must prove less or find another route.

Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives.

Adversarial questions

  • Does the scene create uncertainty about a real choice, or merely hide a safety system until a surprise rescue?
  • Which established constraint would this answer break, and what evidence would reveal that break before the payoff?

Completion checklist

  • [x] Answer the central question in the author's own words.
  • [x] Identify the chosen possibility, a modified combination, or a different answer; explain rejected tradeoffs.
  • [x] Resolve or explicitly defer prerequisites 13, 14, 15.
  • [x] Run the scene test above and state the consequence for the people involved.
  • [x] Answer the adversarial challenge without granting unexplained knowledge or authority.
  • [x] Record what remains working, proposed, or unresolved.
  • [x] Obtain explicit author acceptance before updating canon or workflow progress.
  • [x] Trace the accepted answer through the affected notes and rebuild both projections.

Answer and decision record

Module: 16 · Suspense under decisive control
Gate: Which outcome remains genuinely uncertain even while Samuel cannot seize the conclusion?
State: DRAFT / PROPOSED / AUTHOR-ACCEPTED / REJECTED / DEFERRED
Author answer (verbatim):
Exact restatement:
Selected option or new answer:
Why this tradeoff:
Rejected alternatives and reasons:
Prerequisites resolved / deferred:
Scene test: choices, permissions, evidence, cost:
Adversarial result:
Remaining uncertainty:
Explicit acceptance wording and date:
Affected notes updated:
QA decision reference:
Workflow task and macro-depth effect:
Website rebuild and verification:

Notes and website sections affected