A bond that has to be learned.
Luminai extend human minds. Sylvan's new generation deepens that relationship. The mechanics still need limits.
Source and canon links · Atlas view
Project Explorer
Inspect the corrected story, trace unresolved causes, and work through source-linked brainstorming packets. The repository browser remains available below.
Development workspace · September 6 workshop pass
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 same reviewed Markdown builds the atlas and this topic index. Open a source to inspect its authority; follow its canonical links before changing a claim.
Luminai extend human minds. Sylvan's new generation deepens that relationship. The mechanics still need limits.
Source and canon links · Atlas viewA development system that keeps evidence, invention, and approval separate.
Source and canon links · Atlas viewWhat they want, what they believe, and what their choices cost.
Source and canon links · Atlas viewThe environment has a purpose. The people inside it still have lives of their own.
Source and canon links · Atlas viewKonrad builds obedience in public. Samuel builds dependency in private.
Source and canon links · Atlas viewYou wake inside a civilization modeled on the distant past. Your future depends on learning what it is really for.
Source and canon links · Atlas viewThe science makes the questions sharper. It does not certify a Luminai.
Source and canon links · Atlas viewBook One begins near the outcome. Later books return to the choices that made it possible.
Source and canon links · Atlas viewStory completion · Live from the vault
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 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 record9 / 27story tasks complete
Project explorer
Search or browse 539 documents across canon, development systems, story loops, prose tools, public work, and session history.
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.
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.
03 Context/.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.
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 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.