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 09 Story Exploration/STORY-GENERATION-LOOP.md

Story Generation Loop

Purpose

Generate multiple possible stories from the current Seeds of the Throne vault for inspiration, without contaminating canon.

The system should behave more like a creative search engine than a single-answer generator.

When available, begin from a Gap Analyzer packet and declare a Micro, Standard, Deep, or Cascade token mode. Return shortlisted candidates to 08 Story Loop/DEVELOPMENT-ORCHESTRATOR rather than integrating them here.

Loop

1. Retrieve

Pull only the story material relevant to the exploration target:

  • established facts
  • active character motives
  • system rules
  • current chronology
  • unresolved questions
  • accepted thematic patterns
  • recent brainstorm decisions

Label every retrieved item as one of:

  • ESTABLISHED
  • WORKING
  • UNRESOLVED
  • PROPOSED

2. Constrain

Before generating, state the hard constraints that candidate stories may not violate unless the run is explicitly marked as a counterfactual experiment.

Examples:

  • Konrad never considered failure before the Great War defeat.
  • Samuel remains an outsider in Konrad's eyes during the relevant period.
  • A bounded system cannot become magical omnipotence.
  • Luminai are extended cognition, not separate companion persons.

3. Choose exploration target

Every run should have a narrow creative question, such as:

  • What are five ways Samuel could trick Konrad into reactivating the Fitzgerald machinery?
  • What might the Great War defeat look like from Konrad's point of view?
  • What scenes could reveal the hierarchy lock without exposition?
  • What are alternate ways George's failed takeover could create later consequences?

Also record the current scale, run mode, explicit exclusions, and stop condition.

4. Diverge

Generate 5–12 genuinely different candidate directions.

Do not produce cosmetic variations of the same idea.

Force diversity across dimensions such as:

  • mechanism
  • character motive
  • scale
  • emotional effect
  • point of view
  • timing
  • public/private consequence
  • irony
  • mystery
  • institutional vs personal conflict

At least one candidate should be conservative and strongly grounded in existing structure. At least one should be unexpectedly ambitious. At least one should exploit an existing unresolved question.

5. Expand strongest candidates

Select the most promising 3–5 and expand each into:

  • premise
  • causal chain
  • character pressure
  • key scene/reveal
  • why it is interesting
  • what existing material it uses
  • what new assumptions it requires
  • likely downstream consequences

Generate only the character functions needed to compare candidates. Use 08 Story Loop/CHARACTER-FACTORY for Tier C/D packets only after a role proves necessary. Names remain placeholders unless the author promotes them.

6. Adversarial critic pass

Run separate critic lenses rather than letting the generator grade itself casually.

Causality Critic

Does each event produce the next, or are there invisible jumps?

Character Critic

Would these people actually make these decisions given what is currently established?

Continuity Critic

What existing facts does the candidate conflict with?

System Critic

Does the candidate violate containment, technology, Luminai, authority, evidence, or permission rules?

Creative Interest Critic

Does it create curiosity, pressure, surprise, memorable scenes, reversals, or setup/payoff?

Distinctiveness Critic

Is this actually a different direction, or only a rewrite of another candidate?

Problem-Solving / Listener-Clarity Critic

Can the candidate produce a clear immediate objective, an attempt, a result, a changed state, and a scene understandable without the whole system? Use the criteria in 08 Story Loop/PROBLEM-SOLVING-STORY-ENGINE.

Cost Critic

Does the candidate justify its new characters, systems, assumptions, exposition, and token depth?

7. Rank without canonizing

Score surviving candidates 1–5 on:

  • Story Fit
  • Character Pressure
  • Causal Strength
  • Creative Interest
  • Scene Potential
  • Payoff Potential
  • Immediate Objective Clarity
  • Problem-Solving Potential
  • Escalation Potential
  • Audiobook Legibility
  • Solution-to-Consequence Payoff
  • Required New Assumptions (reverse score: fewer is better)

Do not declare a winner as canon.

Suggested statuses:

  • HIGH-INTEREST CANDIDATE
  • WORTH DEVELOPING
  • INTERESTING BUT COSTLY
  • NEEDS AUTHOR DECISION
  • WEAK
  • REJECT

8. Mutation round

For the top 2–3 candidates, generate one mutation each by combining the strongest feature of one candidate with a different candidate or established story mechanism.

The mutation must still pass the critic loop.

This prevents the system from prematurely converging on the first competent idea.

9. Archive

Save the run with:

  • exact exploration question
  • retrieved constraints
  • all major candidates
  • critic findings
  • ranked shortlist
  • mutations
  • unanswered questions
  • explicit NON-CANON warning

9A. Optional representative prototype

Use a short development prototype only when story-in-motion can distinguish surviving candidates better than further outline debate. Prototype one representative scene, not every branch. State what it tests and list every provisional invention. Readability is not evidence of canon or manuscript readiness.

10. Author Promotion Gate

Stop.

The AI may recommend candidates, but it may not integrate them into the story.

The author chooses whether to:

  • reject
  • park
  • rerun
  • combine
  • brainstorm interactively
  • send candidate into 08 Story Loop/

Only selected material enters the main story-development process.

Token modes

  • Micro: 3 narrow candidates, 2–3 critics, no prose by default.
  • Standard: 4–6 candidates, expand 2, focused critics, optional 500–900 word prototype.
  • Deep: 5–10 candidates, shortlist 3, mutation round, one representative prototype at most.
  • Cascade: 3–5 broad candidates, follow one working branch down through scales, then stop at the author gate.

Use breadth cheaply and depth selectively. Do not fully render every alternative.

Two useful modes

Mode A — Targeted Inspiration

Start from one unresolved story problem and generate possible solutions.

Use when the author is actively brainstorming a specific mechanism.

Mode B — Story Miner

Retrieve a broader cluster of existing material and ask:

What compelling story developments are latent in these facts but have not yet been developed?

Use this to discover connections, reversals, scenes, and consequences already implied by the vault.

Anti-contamination rule

Every output created by this loop must begin with:

NON-CANON STORY EXPLORATION — inspiration only. Nothing below is established unless promoted by the author through the main Story Loop.

Success condition

A successful run does not need to solve the story problem.

It succeeds if it gives the author several genuinely useful possibilities, reveals hidden consequences in existing material, or identifies a better question for the next brainstorm.