Konrad stands under Samuel's hidden red control while Sylvan observes from the clear opposing side.

Project Explorer

Seeds of the Throne

Inspect the corrected story, trace unresolved causes, and work through source-linked brainstorming packets. The repository browser remains available below.

Open the workshop workspace Browse the project

Development workspace · September 6 workshop pass

Find the cause. Test the choice.

All twenty workshop gates have accepted directions. Their unresolved mechanics remain visible. The active Story Completion gate remains SC-010 Question 7.

Public, read-only development material with full spoilers. Draft answers stay in your browser until exported; they do not update the vault. A spoiler boundary is not privacy protection.

The complete pass is preserved below. Accepted directions do not erase each packet's alternatives, tests, or unresolved mechanics, and they do not replace the active completion list.

Browse all twenty decision packets

Loading the selected packet.

Read the full workshop index and Markdown source links

Story completion · Live from the vault

From architecture to manuscript.

The story advances horizontally: every active problem receives the same level of development before any one branch moves deeper.

Integrated foundation review · September 5, 2026

The environment develops the bond. The outcome tests responsibility.

The leaders created an interactive colonization environment and developed Luminai within it. Konrad tries to prove his experienced daemon superior; Samuel turns his reactivation into access. Sylvan already has decisive control during the final years. Exact safeguards and presentation mechanics remain open.

Current method Bound action, observe the method, compare the record, expose the hidden command.

Read the foundation update record

9 / 27story tasks complete

Current checklist completion33%
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

Current working fronts

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

Project explorer

Browse the repository.

Search or browse 539 documents across canon, development systems, story loops, prose tools, public work, and session history.

2.3 KB Updated View source on GitHub

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.