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 02 Story/Systems/Visual Generation/CHARACTER-IDENTITY-LOCKS.md

Character Identity Locks

Purpose

An identity lock answers who remains the same while allowing the photograph to become new. It protects stable human geometry and continuity without freezing pose, wardrobe, palette, or emotional state.

Identity hierarchy

  1. Primary identity master — the best approved face and body anchor.
  2. Required angle references — straight-on, strict profile, and front three-quarter when available.
  3. Supporting references — approved age, expression, body, wardrobe, or relational evidence.
  4. Scene candidates — useful interpretations that cannot redefine identity.

Follow skills/create-seeds-images/references/visual-registry.json for current approved files and reference priority.

Immutable packet

Record only traits that should survive almost every scene:

  • facial geometry and silhouette;
  • apparent age range;
  • stable hairline, hair texture, and facial hair logic;
  • eye placement, nose, mouth, jaw, ears, and distinguishing marks;
  • body proportions, height relationship, and habitual physical weight;
  • traits explicitly established by story canon.

Avoid poetic descriptors that models cannot test. Prefer relational geometry: narrower than, deep-set, high bridge, broad lower face, asymmetric brow, or compact build.

Flexible packet

Allow scene logic to determine:

  • clothing and grooming within era and role;
  • expression and emotional visibility;
  • pose, gesture, gaze, and hand use;
  • camera side, lens, crop, and distance;
  • palette, lighting, weather, and location;
  • age variation when the timeline requires it;
  • injury, fatigue, status, and environmental effects.

Multi-character scenes

Lock each character separately before describing the relationship. State relative height, distance, eyelines, touch, and who occupies foreground or background. Prevent face blending by giving each subject a distinct action and spatial position. Do not ask a model to infer two identities from one paired poster when separate identity masters exist.

Luminai presentation

Luminai and Daemon visual manifestation is energy radiating from the integrated person, concentrated around the head/brain and chest. It is not a separate face, body, holographic companion, monster, or romantic figure. The energy pattern may differentiate healthy integration from corrupted feedback, but it cannot replace the person's identity or imply a second embodied character. In-world observability remains unresolved.

Sylvan wardrobe

For ordinary surface scenes, resolve Sylvan's clothing from his age, role, activity, weather, and the scene's equivalent year. The development reference is middle-class urban Los Angeles and broader United States clothing from 1985 through the present, translated into the invented culture without real brands or locations. His black structured coat and pendant remain valid for later formal, integration, or symbolic scenes; they are not his universal costume.

Konrad Fitzgerald identity

The author approved Konrad's late-containment appearance on 2026-09-03.

  • apparent age: late sixties to early seventies;
  • silhouette: tall, broad, upright, squared military-command posture;
  • face: broad and square with a heavy jaw, blunt chin, strong compressed brow, deep-set eyes, and broad straight nose;
  • hair: close-cropped iron-gray, short at the sides and slightly fuller on top;
  • facial hair: clean-shaven;
  • expression: severe certainty and controlled authority;
  • distinction: never inherit Samuel's narrow hooked face, beard, receding wavy hair, stoop, or crown, and never inherit Sylvan's dark curls, beard, or younger athletic appearance.

The approved front three-quarter anchor is skills/create-seeds-images/assets/reference-images/konrad-fitzgerald-identity-anchor-v1.png. Straight-on and strict-profile masters remain pending. The exact high-collared coat, crimson control lines, blue connection lines, and moon architecture in the source image are scene-specific interpretation rather than locked story facts.

Drift checklist

  • Does facial width remain stable across camera angles?
  • Did apparent age change accidentally?
  • Did hair, beard, skin detail, or body proportions drift toward a generic archetype?
  • Did two characters blend traits?
  • Did the model preserve reference clothing or pose without scene reason?
  • Did a symbolic visual detail become accidental story canon?

Reject identity drift before polishing style. A beautiful wrong person is not a continuity success.