Project Explorer

Seeds of the Throne

Seeds of the Throne began as years of conversations and thousands of story ideas. The Project Explorer shows how those ideas are being organized into characters, a world, a timeline, and a finished series.

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

Story development tools

The workshop helps the author complete the parts of the story that are still missing.

It explains one story problem, asks one clear question, offers different possible answers, and shows what each answer would change. The author makes the decision. The accepted answer is then added to the characters, timeline, world, and plot.

This is a public, read-only look at the real project, so it contains full spoilers. You can try the workshop, but your draft stays in this browser unless you export it.

  1. The author explains the story in ordinary language.

    The system records those ideas and separates confirmed decisions from suggestions and unanswered questions.

    Read how the system is designed
  2. The workshop asks one question at a time.

    Each question helps the author decide a missing cause, character choice, relationship, world rule, or event.

    Open a workshop question
  3. Accepted answers are added where they belong.

    An accepted decision can update character notes, the timeline, world rules, plot events, and the list of remaining questions.

    Review decisions and supporting information
  4. Use the completed plan to write and revise scenes.

    The planned system will create scene outlines, draft prose, check continuity, revise weak sections, and assemble the manuscript for the author's approval.

    Read the system plan

Seeds of the Throne is the working example. The notes, decisions, and workshop below are the live project, not a demonstration mockup.

Current story development

See what the story already has and what it still needs.

The system checks the whole story for missing causes, weak character decisions, unclear rules, and unfinished events. The results show the author what to work on next.

Current story premise

The colonization process trains participants and contains dangerous criminals.

Humanity developed the Luminai inside an interactive colonization environment. Sylvan and his Luminai are tested against Samuel Franklin, a criminal already held inside the containment process.

The current story problem Explain how Sylvan can expose Samuel while Samuel still believes he can regain control.

See how the story changed

9 / 27major story problems resolved

Current development pass33%
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

Story files

Browse the files used to develop the story.

Search 561 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

AI Development Concepts for Luminai Integration

Accepted author direction

The development of Sylvan's human–Luminai integration should deliberately borrow conceptual tools from modern AI systems, software development, and iterative engineering.

This does not mean the story should read like a software manual or that the Luminai is merely a present-day AI assistant. The point is to use familiar technical principles as conceptual ancestors for how an advanced human could learn to work with a much more powerful cognitive extension inside a complex environment.

Core principle

Sylvan does not simply receive a powerful Luminai and know how to use it. He develops effective integration through repeated cycles of use, observation, failure, correction, and increasingly sophisticated coordination.

Useful conceptual ancestors include:

  • calibration;
  • feedback loops;
  • recursive evaluation;
  • adversarial testing;
  • provenance and source tracking;
  • hypothesis generation and falsification;
  • confidence and uncertainty management;
  • model correction after failed predictions;
  • permissions and bounded access;
  • separation of observation from interpretation;
  • error logging and failure analysis;
  • capability expansion only after demonstrated reliability;
  • cross-environment generalization;
  • red-team / critic functions that challenge first-pass interpretations;
  • preserving multiple competing explanations until evidence resolves them.

Story application

Environment 1 — unemployment / emergence

This phase functions like calibration and interface learning. Sylvan learns what his extended cognition can perceive, remember, infer, misunderstand, and initiate. Repeated ordinary routines create baselines against which anomalies can later be detected.

Environment 2 — hostile domination

This phase functions like adversarial evaluation. Samuel and George actively create misleading conditions, manipulated context, false patterns, and hostile feedback. Sylvan's recursive Luminai loop exists because one-pass interpretation is too vulnerable to adversarial framing and self-confirming error.

Environment 3 — multi-zone employment

This phase functions like generalization and systems integration. Sylvan tests what he learned across different settings, permissions, personnel, surveillance conditions, and institutional rules. A model that works in one environment is not automatically trusted everywhere.

Terminal inversion

By the time bounded control transfers to Sylvan, the control itself is not the source of his competence. It gives him a legitimate position from which years of calibrated observation, corrected models, preserved provenance, and accumulated evidence can finally be authenticated and exposed.

Important boundary

These are conceptual ancestors, not literal implementation details. The exact neurotechnical, computational, biological, and environmental mechanics of Luminai integration remain unresolved.

The reader should primarily experience these ideas through situations, failed predictions, corrections, choices, and consequences rather than through explanatory AI terminology.

Development principle

The same reason the Seeds Story Gauntlet uses multiple passes applies inside the fiction: first-pass reasoning can be coherent and still be wrong. Reliability comes from preserving evidence, challenging assumptions, testing predictions, learning from failure, and carrying forward an improved model rather than repeatedly starting from scratch.