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.

3.2 KB Updated View source on GitHub
Document metadata
type: index
status: active
updated: 2026-08-24

Seeds of the Throne

This vault is persistent working memory for developing the story. It preserves the order in which ideas develop while also maintaining compact summaries of the current story.

Start each session

  1. Read 03 Context/CURRENT.
  2. Read whichever of 03 Context/CAST, 03 Context/WORLD, or 03 Context/STORY applies.
  3. Check 03 Context/OPEN-QUESTIONS.
  4. Record new work in 01 Sessions/Daily/ before updating compiled story notes.
  5. For author-facing story work, use only the checklist named by Current Weekly Completion TODO. Capture consequential new directions in Current Week Intake for the next synthesis rather than starting another task list.

Shared methods

Reusable AI workflows live in skills. Review the catalog and load only the skill that matches the current task. Skills guide process but never override the author, establish canon, or silently resolve uncertainty.

Coordination

Read 07 Coordination/CURRENT-PICKUP for the exact resume point, then Coordination for the mobile-versus-desktop convention. Current Pickup routes into the one completion TODO; it does not create separate story priorities. Work requiring local files, testing, commits, publishing, or durable cross-device handoff belongs in the desktop queue, which is a technical handoff rather than an author story list. The short instruction for resuming the project is: Open Current Pickup.

Current story-system directions are summarized in 02 Story/Systems/Advanced Technology Ecology, 02 Story/Systems/Human–Luminai Pairing and Bonding, 02 Story/Systems/Fascist Failure and Leadership Cultivation, and Visual Generation.

Current development work begins with 08 Story Loop/DEVELOPMENT-ORCHESTRATOR and 08 Story Loop/GAP-ANALYZER. Short, readable development prototypes are the default story-rendering mode at this stage. Archive Thriller / Dark Historical Reconstruction remains an available later manuscript register, not the default form for discovering the story. Jurassic Park-style exposition remains retired.

Memory layers

  • 01 Sessions/ — chronological development memory; exploration and contradiction are allowed.
  • 02 Story/ — compiled notes about characters, systems, groups, environments, reveals, and storyline.
  • 03 Context/ — the smallest useful briefing for a new GPT session.
  • 04 Research/ — research requests, reports, and extracted findings. Research is advisory, never canon by itself.
  • 07 QA/ — contradictions, decisions, migration records, and unresolved problems.
  • 07 Coordination/ — device conventions and the durable desktop implementation queue.

Authority

The author's direct statements and decisions control the story. GPT develops, organizes, questions, and maintains continuity. Research remains advisory regardless of the tool used. See 03 Context/RULES.