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 08 Story Loop/CREATIVE-INTEREST-LOOP.md

Creative Interest Loop

Purpose

The structural Gauntlet answers: Does the story work?

The Creative Interest Loop answers a different question: Is the material likely to produce situations a reader wants to experience?

It does not attempt to predict audience taste with certainty. It evaluates practical reader-interest proxies and generates alternatives for the author to judge.

The loop runs after raw brainstorming has been extracted but before weakly imagined material is treated as sufficiently developed merely because it is causally coherent.

Governing rule

Do not confuse a functioning skeleton with an interesting story.

A component may be structurally necessary and still be generic, abstract, repetitive, visually empty, emotionally remote, or predictable. When that happens, preserve the structural function and creatively pressure-test the presentation.

The loop may propose situations, reversals, recurring motifs, complications, and alternative implementations. None become established story facts without an Author Gate.

Input

For the selected Story Unit or brainstorm, retrieve:

  • accepted structural function;
  • established character state and motives;
  • preceding and following units;
  • world/system constraints;
  • current unresolved choices;
  • any concrete images, incidents, artifacts, locations, dialogue ideas, or emotional beats already supplied by the author.

Separate the load-bearing function from its current implementation. Creative passes may attack the implementation without casually reopening the function.

Pass 1 — Curiosity Critic

Ask what makes a reader want the next page.

  • What unanswered question is active?
  • What does the reader understand that the character does not, or vice versa?
  • Is there a changing interpretation rather than merely more information?
  • Does the section contain a discoverable pattern?
  • Is there a promise whose payoff the reader can anticipate?
  • Where does curiosity flatten because the outcome or mechanism is obvious?

Output: strongest curiosity engine, weak points, and 2–4 possible curiosity upgrades.

Pass 2 — Situation and Image Generator

Convert abstractions into things that can actually happen.

Ask:

  • What could the reader see, hear, encounter, or remember?
  • What ordinary situation could carry the strange or advanced layer?
  • What repeated place, object, routine, record, mistake, ritual, or interaction could accumulate meaning?
  • What scene could summarize the section without an exposition paragraph?
  • What image would still be recognizable if all explanatory text were removed?

Prefer concrete situations over lore expansion.

Output: 3–6 candidate situations/images, clearly labeled proposed.

Pass 3 — Character Pressure Critic

Interest increases when the mechanism forces a meaningful choice rather than merely happening to the protagonist.

Ask:

  • What does the character want right now?
  • What does the environment make costly?
  • What tempting easier choice would damage something important?
  • What belief, pride, loyalty, fear, embarrassment, or attachment is being tested?
  • How can the character make a reasonable mistake?
  • What choice changes the situation rather than merely enduring it?

Output: pressure points, missing choices, and proposed dilemmas.

Pass 4 — Surprise / Anti-Generic Critic

Attack the first obvious implementation.

Ask:

  • Is this the version a reader would predict from the premise?
  • Does it resemble a generic conspiracy, simulation, evil-AI, workplace, dystopia, humiliation, or chosen-one sequence?
  • Which existing Seeds mechanism can make it specific to this story?
  • Can the apparent advantage conceal a different real advantage?
  • Can success create a new problem?
  • Can an antagonist action accidentally train, reveal, or empower the target?
  • Can the reader's interpretation change without contradicting the facts already shown?

Do not add randomness for novelty. Surprise should become plausible in retrospect.

Output: clichés/generic risks and 2–4 Seeds-specific reversals.

Pass 5 — Escalation and Payoff Critic

Ask whether the idea grows rather than repeats.

  • What is different the second or third time a pattern appears?
  • What accumulates: evidence, skill, cost, suspicion, relationship change, public consequence, or antagonist desperation?
  • What early detail can become useful later?
  • What does this section set up that the endgame can pay off?
  • Does the final state make the next environment necessary?

Output: escalation ladder and candidate setup/payoff links.

Pass 6 — Interest Integrator

Produce a compact creative packet containing:

  1. Structural function to preserve — what cannot be lost.
  2. What is already interesting — concrete strengths in the author's brainstorm.
  3. What currently feels skeletal/generic — without treating personal taste as objective fact.
  4. Three strongest proposed upgrades — preferably different in kind, not cosmetic variants.
  5. One high-risk/high-reward possibility — optional, clearly labeled.
  6. What should remain quiet or ordinary — avoid making every scene maximally dramatic.
  7. Author Gate — the smallest set of creative choices that would materially improve the unit.

Interest dimensions

Use these as diagnostics, not a mechanical scorecard:

  • curiosity;
  • visual/concrete specificity;
  • character desire and pressure;
  • surprise with retrospective plausibility;
  • emotional consequence;
  • escalation;
  • distinctiveness to Seeds of the Throne;
  • scene potential;
  • setup/payoff potential;
  • contrast and pacing;
  • memorable ordinary detail;
  • reader-facing evidence rather than explanation.

A section does not need maximum intensity in every dimension. Quiet sections may score through intimacy, strangeness, pattern recognition, atmosphere, or anticipation.

Relationship to the Structural Gauntlet

Recommended brainstorm cycle:

author brainstorm -> extraction -> structural architect -> Creative Interest Loop -> structural critics -> author gate -> integration

For material that is already structurally sound but dull:

existing unit -> Creative Interest Loop -> author choices -> structural re-check -> integration

For wild but exciting ideas:

creative proposal -> author interest gate -> causality/character/continuity critics -> repair or reject

Creative interest never overrides continuity or author authority. Structural correctness never automatically counts as creative success.

Audience humility

The loop cannot know with certainty what other people will enjoy. It should therefore avoid claims such as "readers will love this." It may instead identify whether a concept provides recognizable drivers of attention and whether it can be dramatized clearly enough to test later through excerpts, public posts, beta readers, or other real audience feedback.