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.

See how the story is being built Browse the story files

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.

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
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
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
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.

See what the analysis found See where development continues Enter the story

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

01 Macro
02 Causal
03 Agency
04 Systems + evidence
05 Sequence
06 Scene map
07 Scene development
08 Draft

What the story needs next

Human–Luminai breakthrough
Evidence chain
Character agency

Follow the full story roadmap

Story files

Browse the files used to develop the story.

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

Repository
07 Coordination
Story Completion Workflow
Workshop
13 - Sylvan’s human arc.md

Document metadata

type: workshop-module
status: author-accepted
module: 13
title: Sylvan’s human arc
gate: What does Sylvan have to relinquish or revise even after he can contain Samuel?
prerequisites: 02, 03, 05, 06
updated: 2026-09-06
accepted: 2026-09-06

13 · Sylvan’s human arc

Purpose

Give the capable endgame protagonist an unfinished personal problem.

This packet supports the existing Story Completion Workflow. Its central gate was author-accepted on September 6. It does not answer SC-010 Question 7 or advance that checklist. Central synthesis: Astra, reviewed for integration on September 5.

Accepted result

Sylvan and Orzai are placed in the same environment and choose to partner despite Samuel's attempts to make each appear irrational to the other. Their trust and separate human–Luminai bonds develop while they are attacked. They become fully aware they face the same enemy, complete the process as independently assessed pairs, and earn the option to secure a House together. Their relationship strengthens the result without becoming the sole qualification.

separate manipulation → meeting → uncertain trust → chosen partnership → shared recognition → bonding under attack → completion

Relevant source notes

Confirmed facts and current working constraints

Sylvan is outgoing, collaborative and technically creative; startup collapse and prolonged struggle develop the bond.
Book One opens after decisive control, not before all human development is complete.

These constraints inherit their source status. A working physical model, timing estimate, or accepted macro constraint does not establish every implementation detail.

Unresolved gaps and contradictions

Present desire; cost of control; mistake; relation to parents and placement; why continue.

Prerequisite decisions

Modules: 02, 03, 05, 06. Read their accepted results before closing this gate. Open prerequisites can be explored provisionally, but do not mark dependent choices final. Module numbers are topic IDs; use the dependency order in the workshop index.

Central author gate

What does Sylvan have to relinquish or revise even after he can contain Samuel?

AUTHOR-ACCEPTED DIRECTION: Sylvan must trust Orzai's independent perception and preserve partnership under manufactured distrust rather than treating control or solitary certainty as sufficient.

Possibilities and tradeoffs

1. From proving himself to accepting a bounded result

PROPOSED: He stops treating perfect completion as the condition of worth. Directly opposes Konrad’s one-victory redemption; risk of making ambition inherently suspect.

2. From organizing everyone to respecting independent refusal

PROPOSED: His social talent becomes leadership when people can decline his plan. Strong Orzai and witness conflict; refusal must materially change events.

3. From solving the system to choosing a life beyond it

PROPOSED: He regains craft, partnership or ordinary commitments the test consumed. Humanizes long chronology; must not trivialize unresolved victims.

4. From filial trust to accountable loyalty

PROPOSED: He can love his parents while requiring review of their process. Strong institutional stakes; avoid replacing one total certainty with blanket cynicism.

Targeted follow-up questions

What ordinary thing does he want before the presentation?
Where does his best trait create pressure on someone else?
What would he choose if his placement were guaranteed?

Scene test

Non-canon situation: Orzai declines a useful synchronization or disclosure request; Sylvan’s first plan becomes impossible, and he must devise another without punishing her refusal.

Record what each person wants, can know, can refuse, and can actually change. Name the observable difference between the selected alternatives.

Adversarial questions

If he already understands Samuel and controls the conclusion, what can he still be wrong about that matters to someone he loves?
Which established constraint would this answer break, and what evidence would reveal that break before the payoff?

Completion checklist

[x] Answer the central question in the author's own words.
[x] Identify the chosen possibility, a modified combination, or a different answer; explain rejected tradeoffs.
[x] Resolve or explicitly defer prerequisites 02, 03, 05, 06.
[x] Run the scene test above and state the consequence for the people involved.
[x] Answer the adversarial challenge without granting unexplained knowledge or authority.
[x] Record what remains working, proposed, or unresolved.
[x] Obtain explicit author acceptance before updating canon or workflow progress.
[x] Trace the accepted answer through the affected notes and rebuild both projections.

Answer and decision record

Module: 13 · Sylvan’s human arc
Gate: What does Sylvan have to relinquish or revise even after he can contain Samuel?
State: DRAFT / PROPOSED / AUTHOR-ACCEPTED / REJECTED / DEFERRED
Author answer (verbatim):
Exact restatement:
Selected option or new answer:
Why this tradeoff:
Rejected alternatives and reasons:
Prerequisites resolved / deferred:
Scene test: choices, permissions, evidence, cost:
Adversarial result:
Remaining uncertainty:
Explicit acceptance wording and date:
Affected notes updated:
QA decision reference:
Workflow task and macro-depth effect:
Website rebuild and verification:

Notes and website sections affected

Public atlas: docs/characters.html, the matching source in 05 Public/Atlas/, and the workshop projection.
Development Explorer: the relevant topic view, this source packet, and linked evidence/decision records.
07 QA/Decisions, 07 QA/Questions, and 07 Coordination/Weekly Synthesis/CURRENT-WEEK-INTAKE. Update 07 Coordination/CURRENT-PICKUP and the current task only if the author accepts a workflow-relevant decision.