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.

Participant Governance and Command Rules

September 5 unresolved safeguards

Established: final-years Samuel activity occurs under Sylvan's decisive control. Unresolved: what counts as a consequential action, who independently can stop observation, and how threatened people receive protection and redress. The earlier criminal jurisdiction never makes people property. Placement must distinguish competence from authority and coercion from culpability; a final choice need not erase prior acts. See workshop modules 02, 03, 07, 08, 15, and 19.

Established terminal rule: Sylvan and Orzai reach decisive control by surviving Samuel's higher-influence environments, learning his methods, and remaining unprocessed until the process's terminal threshold. Samuel must cause their valid processing before that point if he is to prevent the transition. Once they survive to the endpoint, control passes to them under rules already built into the process. Exact processing criteria and safeguards against manufactured violations remain unresolved.

Established elimination progression: after the software-company collapse, Sylvan enters an approximately ten-year protected-reserve stage. An emergency investment functioning like a certificate of deposit holds approximately $200,000. Evenly distributed across 120 months, it provides about $1,667 per month before returns, taxes, fees, or emergencies. Managing it effectively requires exceptional discipline and restraint. When it is exhausted, he enters the employment stage and must survive through active income.

During the employment and later environments, Samuel may destroy projects, get Sylvan fired, deny resources, isolate him, damage his credibility, or induce other qualifying mistakes that halt progress. Losing employment now threatens immediate survival because the protected reserve has already run out.

The complete catalog must distinguish actual participant failure from an outcome Samuel merely fabricates through superior access.

Source: 01 Sessions/Daily/2026-09-05 - Integrated Foundation Audit and Workshop Build.

Core rule

Participants on the colonization planet are governed by very strict rules even when they are given access to extremely powerful technological systems.

The colony's command-and-control architecture may be capable of reaching effectively all technology on the planet, but participant authority is never equivalent to unrestricted system ownership.

The key distinction is:

Universal technical reach does not imply universal participant permission.

Participants operate inside a rule-bound environment designed to preserve agency, accountability, evidence, containment integrity, and the developmental purpose of the colony.

Environment commitment boundary

Established direction: while a participant remains in the colonization process, neither the participant nor the Luminai or Daemon can prematurely abandon, skip, replace, or rewrite the assigned environment. Technical access cannot create a valid exemption from the conditions and rules being used to train, assess, or contain that participant.

The boundary governs continuation inside the process. A legitimate heir or other voluntary trainee may still leave the entire process and surrender the unfinished self-made result. The participant cannot preserve accumulated process standing and access while unilaterally escaping only the difficult environment. Convicted participants remain subject to separate sentence, review, and release rules.

This rule does not authorize unlimited harm. Completion criteria, transition authority, appeal, emergency intervention, and the safeguards that distinguish committed participation from institutional abuse remain unresolved.

Asymmetric participant advantage

Established direction: contained criminals can hold a serious structural advantage over developmental participants while remaining bound by the same larger governing framework.

Their advantage can include some combination of:

  • earlier or broader access to environmental controls;
  • better knowledge of how the rules work;
  • more experience exploiting permissions and edge cases;
  • greater surveillance or observability;
  • stronger influence over synthetics, local systems, scheduling, routing, and information delivery;
  • preexisting institutional relationships or delegated authority;
  • better knowledge of the participant's goals, vulnerabilities, and evaluation conditions;
  • the ability to initiate pressure while the developmental participant is still discovering what the environment is.

This asymmetry is intentional enough to create a real ordeal, but not unlimited enough to predetermine the outcome.

The contained criminal must still operate inside rules that preserve the validity of the contest. They cannot simply bypass the entire process, directly manufacture the result, or erase the evidence of their own choices without consequence.

The core balance is:

contained criminals begin with major tactical and informational advantages; participants retain rule-protected paths to survival, learning, verification, and eventual reversal.

This makes the ordeal unfair in the ordinary sense while still being structurally winnable.

Reactivated-jurisdiction inheritance

Established causal result: after the Great War, Konrad voluntarily remains in the colonization process and reactivates his Daemon, followers, hierarchy, breeding program, bloodline systems, and infrastructure inside a containment environment where Samuel already possesses earlier structural priority. The apparently separate autonomous group Samuel promises is not structurally independent. This gives Samuel the access required for the later takeover.

Accepted macro implementation: Primary is a negotiated alpha-status position in a tiered permission hierarchy. Samuel retains broad cross-domain visibility, surveillance, information, influence, and meaningful decision authority over initiatives operating inside his containment sphere, but not blanket sovereignty or a universal override. Konrad and other negotiated leaders retain protected positions and genuine domain authority.

The Fitzgerald breeding, lineage, and younger-generation systems do not migrate automatically. Konrad must voluntarily accept or reactivate them inside what he believes is a separate domain. Once active inside Samuel's sphere, Konrad remains beta with substantial real operating authority, while Samuel's alpha standing gives him the hidden visibility and decision influence needed to conceal competing interventions.

Still unresolved: detailed permission weighting, the exact registration or lock event, evidence of the transfer, hard limits, conflict resolution among protected leaders, and why later reset cannot undo the consequences. Do not claim that every imported person or system automatically becomes Samuel's property. Preserve the distinction among visibility, permission inheritance, command authority, observation, and later manipulation.

The eventual rule must explain why Konrad can still exercise meaningful local authority, why Samuel gains a durable hidden advantage, what evidence records the transfer, and why the hierarchy cannot be reset once the damage becomes obvious.

Participant authority model

Participant access should be constrained by combinations of:

  • identity;
  • assigned role;
  • current stage of the environment;
  • physical location;
  • task or declared purpose;
  • time window;
  • system category;
  • authorization tier;
  • local confirmation;
  • safety interlocks;
  • quorum or independent approval;
  • immutable logging;
  • automatic review or escalation triggers.

The exact matrix remains unresolved and should be developed only as story requirements demand.

What strict rules accomplish

The rules prevent a powerful participant from simply converting the colony into arbitrary reality control.

They also create the possibility for adversarial ingenuity: Samuel, George, or a Daemon can become dangerous by discovering how to use legitimate permissions, ambiguities, timing windows, delegated authority, institutional habits, and interacting subsystems in ways the designers did not intend.

This means the strongest antagonistic behavior often resembles exploit development rather than godlike command:

understand the rule -> discover the boundary -> combine permitted actions -> produce an unintended effect -> remain technically inside or near the rule until challenged

The colony can therefore be extraordinarily powerful while still generating meaningful conflict.

Rule-bound hostile control

When Samuel and George gain greater control after the exploratory stage, their hostile phase should not remove the participant rules.

Instead, they acquire enough legitimate or delegated authority to make the rules dangerous.

Their Daemon can search continuously for ways to weaponize:

  • permitted surveillance;
  • routing;
  • environmental adaptation;
  • synthetic tasking;
  • information delivery;
  • access control;
  • scheduling and timing;
  • social coordination;
  • public interpretation;
  • institutional process;
  • combinations of individually lawful commands.

The horror comes from orchestration within constraints.

Important narrative consequence

Strict rules mean Samuel cannot simply command: "destroy Sylvan."

He has to produce conditions under which Sylvan breaks, fails, becomes disqualified, or reaches whatever processing threshold the colony recognizes.

That makes the humiliation stage a genuine contest rather than an execution.

Samuel's problem is therefore not lack of technological reach. It is that the system still contains rules he cannot openly violate without losing legitimacy, triggering intervention, creating evidence, or invalidating the process.

Sylvan's survival depends partly on learning those boundaries faster than Samuel can exploit them.

The same asymmetry also explains why Samuel can appear overwhelmingly dominant while still fearing time. His advantage is front-loaded. If Sylvan remains intact long enough to understand the rules, preserve evidence, and reach the protected transition conditions, Samuel's superior local leverage can cease to matter or even become evidence against him.

Relationship to Luminai and Daemons

A healthy Luminai can help a participant understand what is authorized, preserve provenance, detect conflicts between commands and rules, and distinguish technical capability from legitimate action.

A Daemon seeks the opposite advantage: every permission becomes an attack surface, every exception a possible exploit, every ambiguity a place to push the system toward its obsession.

The difference is not that one has technology and the other does not. They can touch the same command fabric. Their relationship to constraint is different.

Hard constraints

  • Participants remain accountable for actions carried out through their Luminai or Daemon.
  • A participant cannot erase the existence of the governing rules merely by gaining higher access.
  • A participant cannot use higher access to create a valid premature exit, skip an assigned stage, substitute a preferred environment, or retain process benefits after abandoning the current environment.
  • High-level commands should leave provenance unless a specific story mechanism establishes otherwise.
  • Some systems must retain independent refusal, review, or evidence functions.
  • The environment must preserve a path by which abusive use of legitimate authority can later be authenticated.
  • Strict rules cannot become arbitrary authorial barriers introduced only when needed to save Sylvan; important limits must be established before payoff.
  • Samuel and George may exploit rules, but they cannot silently rewrite the entire constitutional logic of the colony.
  • Contained criminals may have substantially greater practical power than developmental participants without possessing authority to predetermine the participant's moral or evaluative outcome.
  • A contained criminal's advantage must create pressure, not eliminate the possibility of valid resistance.

Open questions

  1. What categories of participant rules exist across all stages of the colony?
  2. Which rules are technical enforcement and which are legal/institutional requirements?
  3. What authority changes when Samuel and George gain control at the end of the exploratory stage?
  4. Which actions remain categorically prohibited even then?
  5. What constitutes a violation serious enough to remove or process a participant?
  6. What exact valid condition must Samuel produce to cause Sylvan to be processed before the terminal control transition, and what prevents Samuel from fabricating it?
  7. Which logs or independent systems preserve evidence of rule exploitation?
  8. What happens when a participant follows the literal rule while clearly violating its intended purpose?
  9. Can a Daemon combine many individually permitted actions into an outcome no single rule anticipated?
  10. Which pre-established participant rules execute the terminal control transition once Sylvan and Orzai survive unprocessed to the endpoint?
  11. Which advantages are deliberately granted to contained criminals, which are inherited from their position, and which are illicitly accumulated?
  12. What minimum protected capabilities must Sylvan retain even during maximum hostile control so the ordeal remains valid?
  13. What objectives must Sylvan keep completing in each environment, and which interruptions count as failure?
  14. What exact instrument fills the certificate-of-deposit role, how does it release barely sufficient support across approximately ten years, and what determines when it is exhausted?
  15. What are the distinct elimination conditions, and which produce immediate processing, remediation, repetition, loss of placement, or some lesser consequence?

Story-development principle

When designing any powerful ability for Samuel, George, Sylvan, a Luminai, or a Daemon, define four things at the same time:

  1. what the system can technically do;
  2. what the participant is permitted to do;
  3. what evidence the action leaves;
  4. what happens if the participant abuses the permission.

This should keep advanced-environment scenes powerful, legible, and strategically interesting rather than arbitrary.