Project Explorer

Files

Story files

Browse the notes, research, decisions, and workshops used to develop the series.

Search 577 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.