Project Explorer

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.

See how the story is being built Browse the story files
Konrad stands under Samuel's hidden red control while Sylvan observes from the clear opposing side.

Story development tools

The workshop helps the author complete the parts of the story that are still missing.

It explains one story problem, asks one clear question, offers different possible answers, and shows what each answer would change. The author makes the decision. The accepted answer is then added to the characters, timeline, world, and plot.

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 one part of the story. Each workshop explains what is known, what is missing, why the answer matters, and several different ways the story could work. Nothing becomes part of the story until the author accepts it.

Choose from twenty story workshops

Loading the selected workshop.

See every workshop and its source

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 Explain how Sylvan can expose Samuel while Samuel still believes he can regain control.

See how the story changed

9 / 27major story problems resolved

Current development pass33%
33%
Current sweep
Macro Shape
Current task
SC-010
  1. 01 Macro
  2. 02 Causal
  3. 03 Agency
  4. 04 Systems + evidence
  5. 05 Sequence
  6. 06 Scene map
  7. 07 Scene development
  8. 08 Draft

What the story needs next

  • Human–Luminai breakthrough
  • Evidence chain
  • Character agency
Follow the full story roadmap

Story files

Browse the files used to develop the story.

Search 561 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

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.