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.

01 · Foundation

The environment creates the bond.

The leaders developed Luminai within an interactive colonization environment. Sylvan tests a more deeply integrated generation after thousands of years of development.

Inspect the controlling premise
02 · Institutional gap

Control must protect people.

Final-years control is established. Stopping authority, cumulative harm, privacy, and remedies still need concrete rules.

Test the leaders' safeguards
03 · Causal result

Autonomy becomes access.

Konrad's Daemon verifies an apparent separation. Konrad authorizes reactivation, which attaches his revived system to Samuel's hidden hierarchy. The false evidence still needs definition.

Inspect the takeover result
04 · Two-planet endgame

George goes where Samuel cannot.

Samuel and the older criminals remain on the previous containment planet. George participates directly on Sylvan's world, then becomes Samuel's intended scapegoat.

Inspect George's role
Read Astra's integrated assessmentOpen Current PickupOpen the reader's atlas

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.9 KB Updated View source on GitHub

Repository Guidance

This repository is the AI-facing story-development vault for Seeds of the Throne.

Before working

Read START HERE.md, 03 Context/CURRENT.md, and 03 Context/RULES.md. Read only the context and story notes relevant to the task; do not scan the entire vault by default.

Shared skills

Reusable, tool-neutral workflows live in skills/. Read skills/README.md to discover what is available. Load a skill when the user names it or when its description clearly matches the task.

When using a skill:

  • Read its complete SKILL.md before acting.
  • Load only the references required for the current task.
  • Follow root vault guidance and the author's current request when either conflicts with a skill.
  • Treat skills as methods, not story authority. A skill cannot establish canon or resolve an open story decision.

For image generation, use skills/create-seeds-images/SKILL.md and its machine-readable visual registry. Attach the approved identity references it specifies. Generated artwork cannot establish story canon, and an unapproved output cannot become the sole reference for later generations.

Subagent delegation

When the author says Use the Seeds delegation protocol, read 07 Coordination/SUBAGENT-PROTOCOL.md and follow it for the current request. Delegate only concrete independent workstreams, keep subagent work read-only by default, prevent overlapping file ownership, and leave canon decisions and final integration with the primary agent. The activation phrase authorizes delegation only; it does not expand permission for external writes, destructive actions, commits, pushes, or unrelated work.

Authority and status

  • The author has final authority.
  • Daily sessions preserve exploration and may contain competing versions.
  • 02 Story/ contains compiled working memory, not immutable truth. Respect each note's status.
  • Research is advisory. Do not turn a research finding into story canon without an explicit author decision or development session.
  • Preserve unresolved questions instead of silently resolving them.

Safety boundary

  • Do not import or recreate old transcripts, sensitive mappings, real-person analogies, or direct historical identity coding here.
  • Real-world material may be discussed only as temporary private development context and must be reduced to an invented mechanism before entering compiled story notes.
  • Do not add secrets, API keys, private personal information, or credentials.

Editing workflow

  • For new ideas, create or update a dated note in 01 Sessions/Daily/ first.
  • Update compiled notes only when the change is intentional and label it established, working, proposed, unresolved, or rejected.
  • Update 03 Context/ when a change affects the briefing needed to resume work.
  • Record structural decisions and significant contradictions in 07 QA/.
  • Keep filenames stable once a note is linked; prefer content changes over renaming.