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 · Workshop

Develop the story from its current ending.

The current workshop begins with Samuel's terminal separation and works backward into the causes the ending still needs. Each accepted answer can change which question comes next.

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.

Choose from ten current story workshops

Loading the selected workshop.

See every workshop and its source

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 README.md

Seeds of the Throne

This repository is the AI-facing Obsidian vault for developing Seeds of the Throne.

It is persistent working memory for story development: chronological sessions, compiled story elements, compact context files, research, drafts, public material, and continuity QA.

Public website

The complete tracked repository is published under https://iainreid.dev/devsite/ so its public-facing vault material can be explored directly. The iainreiddotdev/ directory contains the PHP portfolio previously maintained in the separate public iainreid.dev repository, and the root index.php redirects /devsite/ visitors into that nested application at /devsite/iainreiddotdev/. The Project Explorer provides a read-only folder tree, document search, and rendered view of every non-hidden Markdown file. Repository metadata and dotfiles remain blocked from web access.

Start here

  1. Read START HERE.
  2. Read 03 Context/CURRENT.
  3. Read 03 Context/RULES.
  4. For current cast, world, and story summaries, read the other files in 03 Context/.

Important separation

The old working vault is kept separately as Seeds of the Throne archive. It is not part of this repository and is not routine AI context. Old transcripts, sensitive mappings, and unsafe historical material were intentionally excluded from this vault.

Working roles

  • The author makes story decisions and controls final voice.
  • GPT is the story-development and organization command center.
  • Research is advisory and does not create canon automatically.

Session workflow

Record development in 01 Sessions/Daily/. Preserve competing possibilities and contradictions there. Promote deliberately selected material into 02 Story/, update 03 Context/ when the working summary changes, and record consequential resolutions in 07 QA/Decisions.md.

Mobile and desktop handoff

Mobile sessions may develop story material, research plans, vault-ready notes, and public copy. Local repository reconciliation, structural edits, code or website changes, verification, commits, pushes, and publishing happen on desktop. See 07 Coordination and the desktop implementation queue.