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.

Explore the vault See how the story is being built Browse the story files
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.

See what the analysis foundSee where development continuesEnter the story

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

What the story needs next

  • Terminal chain
  • Constructive ending
  • Proof and recognition
Follow the full story roadmap

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/Artifacts/Journals/Characters/Sylvan Elaria/Journal Profile.md

Document metadata
type: journal-profile
status: working
updated: 2026-08-23
character: Sylvan Elaria
journal_id: SE-JRN

Sylvan Elaria — Journal Profile

Authority and scope

Sylvan's evidence-oriented role, software/story-development background, Luminai development, discovery that Samuel is the hidden opponent, emerging-leader preparation, outgoing temperament, and complementary partnership with Orzai are established or working story memory. Exact notebooks, entries, investigative methods, shared-work permissions, and evidence sequence remain unresolved.

Physical design and hand: working. Journal-specific approved references: none.

Existing identity authority: sylvan-elaria in skills/create-seeds-images/references/visual-registry.json, including approved identity/angle references and the approved supporting private-study image. Those references do not approve the notebook, desk, room, handwriting, or props.

Approved identity inputs currently available:

  • skills/create-seeds-images/assets/reference-images/sylvan-elaria-identity-master-v1.png — canonical primary;
  • skills/create-seeds-images/assets/reference-images/sylvan-elaria-front-v1.png — canonical front angle;
  • skills/create-seeds-images/assets/reference-images/sylvan-elaria-profile-left-v1.png — canonical left profile;
  • skills/create-seeds-images/assets/reference-images/sylvan-elaria-private-study-v1.png — approved supporting reference with the visual registry's room/prop warning.

Checksums, provenance, limitations, and priority remain authoritative in the visual registry. No handwriting, notebook family, diagram sheet, or interior spread is approved.

Physical identity

  • Working object family: modular field/investigative notebooks, approximately 140 × 205 mm, rather than one ceremonial volume.
  • Cover: weather-resistant charcoal woven-composite cloth over thin flexible boards, rounded corners, visible warm-gray repairable stitching, and a simple elastic closure. No logo or inherited insignia.
  • Binding: exposed sewn signatures that lie flat and make removed pages obvious. Volumes are replaceable, date-ranged, and cross-indexed rather than treated as sacred objects.
  • Paper: warm-white mixed stock—faint dot grid for systems, blank leaves for maps, and occasional perforated provenance slips. Page ruling changes by function but stable indexing prevents ambiguity.
  • Instruments: blue-black waterproof fine-nib ink for durable observations, graphite for hypotheses, muted amber removable tabs for unresolved review. Exact commercial era equivalents remain undefined.
  • Navigation: volume code, date range, page number, source bracket, permission mark, and next-review date. A removable rear index card maps related digital records without pretending the paper contains them.
  • Wear: softened corners, rain spotting, flattened page edges, repaired thread, and graphite transfer from frequent comparison. Wear records use, transport, and retrieval rather than decorative distress.
  • Unresolved: why he preserves particular work on paper, exact surface-era material availability, manufacturer, volume chronology, and Luminai-assisted indexing limits.

Handwriting identity

Clear, economical, observational, and visibly conversational. Stable baseline, moderate spacing, legible dates, source codes, names and perspectives gathered from other people, small questions, restrained corrections, and enough blank space for later verification. Under pressure the page grows denser but remains traceable.

Full construction rules and reusable exercises: 02 Story/Artifacts/Journals/Characters/Sylvan Elaria/Writing and Drawing Samples.

Drawing and diagram grammar

Timelines, maps, system boundaries, evidence chains, competing hypotheses, witness links, behavior comparisons, permission paths, contradictions, and broad stakeholder maps. Samuel circles answers; Sylvan circles questions. His outgoing cognition often records an idea early enough for dialogue to change it.

His unique integration rule is conversation remains visible inside the map: prose observations open into incomplete question rings, alternatives retain their falsification tests, and every evidentiary arrow carries provenance and permission. Dense inquiry resolves into one bounded action line with a review date.

Recurring motifs

Open question ring, branching path with alternatives left intact, paired observations, provenance brackets, boundary boxes, timestamps, and later authenticated links among apparently separate evidence.

Emotional and chronological evolution

StateStory periodWritten/layout changeMeaning
builderstartupsystem maps and creative-development observationsHe looks for structures that help people develop.
disorientationcollapse/first environmentshort facts, repeated checks, protected uncertaintiesHe resists Samuel's imposed explanation.
adaptationenvironment laddercross-environment comparison and permission mapsExperience becomes method.
investigatorhidden-opponent discoverybehavior and evidence converge without erasing alternativesGeorge no longer explains the whole pattern.
exposurefinal bounded environmentconcise decision records and authenticated chainsKnowledge becomes accountable action.

Content and knowledge rules

Sylvan records hypotheses at their actual confidence. He cannot use later revelations in earlier notes. His Luminai may help index, compare, or authenticate only within unresolved capability and consent limits; the notebook must not become a magical answer engine.

Shared work with Orzai must preserve her independent judgment and privacy. Use cross-references, permissioned extracts, recorded disagreements, and separate confidence levels rather than visually merging their minds or making Orzai an anonymous source of conclusions.

Evidence and forensics

Sylvan's journals can preserve how a conclusion formed: initial anomaly, alternate explanations, falsification attempts, source provenance, permission boundaries, corroboration, and remaining doubt. This supports fair revelation and protects against retrospective certainty.

Visual generation contract

Preserve legibility, questions, evidence provenance, era fit, and the current stage of knowledge. Vary notebook volumes, settings, density, instrument, camera, and use-wear. Avoid detective-board cliché, omniscient diagrams, automatic gold glow, generic hacker interfaces, or copying the private-study reference as a fixed room.

Approval state

  • [ ] physical notebook family approved
  • [ ] handwriting sheet approved
  • [ ] diagram sheet approved
  • [ ] cover/interior spread approved
  • [ ] emotional-state variants approved

Current candidate board and exact sample transcriptions are indexed in 02 Story/Artifacts/Journals/Candidate Images/2026-08-23 - Four Journal Candidate Boards and 02 Story/Artifacts/Journals/Characters/Sylvan Elaria/Writing and Drawing Samples.