Project Explorer · working sheet

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.

Interpretive still life of recovered records aligned against hidden-system evidence.

Recovered records held against the working evidence.

Story development tools

See how the authoring system turns ordinary language into finished story work.

The Project Explorer shows the live notes, decisions, and workshop used to develop Seeds of the Throne. Each step keeps confirmed decisions separate from suggestions and unanswered questions.

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 current workshop asks one consequential 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.

Vault overview

See the whole story-development system at a glance.

605 notes work together as one system. The vault remembers where ideas came from, what the author decided, what remains uncertain, and what should happen next.

The vault turns conversations into organized story memory. It preserves sources, separates decisions from suggestions, finds missing connections, supports research and workshops, prepares scenes and prose, checks continuity, and publishes selected material without surrendering author control.

  • Working now Capture, memory, workshops, and research already operate.
  • Needs repair Current-state agreement, automatic checks, and decision updates still drift.
  • Planned next Durable answers, manuscript production, and mobile save are not built yet.
  1. Capture

    Conversations, mobile notes, and raw ideas are preserved.

  2. Understand

    Current context and compiled notes explain what the project means now.

  3. Decide

    Workshops ask one important question and preserve the author's answer.

  4. Develop

    Research, alternatives, story structure, and focused tests strengthen the work.

  5. Create

    Scene plans, prose, images, and manuscript material are produced for review.

  6. Share

    Selected material becomes the story site, Project Explorer, and public posts.

What lives where

Each area has a job. Folder names are secondary detail.

  • New material

    Preserves incoming ideas and the order in which they developed.

    00 Inbox, 01 Sessions

  • Story memory

    Keeps the detailed working knowledge and a smaller briefing used to resume work.

    02 Story, 03 Context

  • Research

    Separates questions, reports, and usable findings from story decisions.

    04 Research

  • Public work

    Holds reviewed material prepared for readers.

    05 Public

  • Drafts

    Holds scenes and manuscript candidates awaiting review.

    06 Draft

  • Decisions and direction

    Records choices, contradictions, current work, handoffs, and verification.

    07 QA, 07 Coordination

  • Development tools

    Diagnoses missing connections and tests possible story directions.

    08 Story Loop, 09 Story Exploration

  • Reusable methods

    Provides repeatable methods for writing, research, images, websites, and checks.

    skills, scripts

What already works, what needs repair, and what is still planned

Working well

  • Idea and session capture
  • Human-readable story memory
  • Author authority and decision boundaries
  • Research kept separate from story truth
  • Workshop questions that wait for an answer
  • Decisions, contradictions, and open questions
  • Visual identity and image controls
  • Markdown files and recoverable history
  • Searchable file access

Needs repair

  • One trustworthy current-state view
  • Automatic checks before a change is merged
  • Shared labels and stable record identifiers
  • Updating every affected note after a decision
  • Keeping the weekly cycle current
  • Clearer boundaries around older folders
  • A cleaner split between the repository and the live site

Planned next Not built yet

  • Durable integration of conversational answers
  • Automatic reports of what a decision would change
  • Complete scene-to-manuscript production
  • Manuscript assembly and export
  • Reliable mobile save, resume, and synchronization

The next build order

  1. Make builds and checks reliable.
  2. Create one trustworthy current state.
  3. Normalize the records for one small complete path.
  4. Connect accepted decisions to every affected file.
  5. Prove one complete path from conversation to approved manuscript material.
  6. Expand only after that path works.

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 Make the formal separation, rapid financial collapse, processing, exposure, and accepted placement feel inevitable.

Read the current story assessment

0 / 10major story problems resolved

Current development pass0%
0%
Current sweep
Reassessment
Current task
RW-01
  1. 01 Reassessment
  2. 02 Causal sequence
  3. 03 Character agency
  4. 04 Systems + evidence
  5. 05 Scene design
  6. 06 Draft

Story files

Browse the files used to develop the story.

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

Current document 08 Story Loop/STORY-MAP.md

STORY-MAP

This is the master causal map for Seeds of the Throne. The order below is a working causal order, not an approved chapter order. Historical material may later appear as archive evidence, reconstruction, or earlier viewpoint material.

Status key

  • missing — load-bearing answer is absent.
  • partial — useful material exists but the unit cannot yet hand off cleanly.
  • testable — sufficient for a Gauntlet run.
  • integrated — author-approved and reconciled into affected compiled notes.
  • blocked — depends on an unresolved earlier unit or author choice.

Master map

IDStory UnitFunctionCompletenessAuthorityPrimary dependency / gap
S-001The colonization leaders' son builds a pre-AI story-development startup while beginning the bond that will eventually stop Samuel and GeorgeEstablish a credible approximately-2015 surface world, earned creative/technical future, exceptional developmental purpose, and the endgame capability in an early limited formpartialestablished core / working detailProprietary story method, earlier projects, scale, collaborators, bonding stages, limits, and opening viewpoint
S-002[[08 Story Loop/Units/S-002 - Sylvan Modern Inciting EventContained criminals sabotage Sylvan and unknowingly begin completing his bond]]Turn the attack meant to derail Sylvan into the first ordeal that develops the human–Luminai integration capable of defeating Samuel and Georgepartialestablished causal spine / unresolved mechanism
S-003Witness evidence reaches Sylvan through Orzai's family lineJoin the Great War Witness and modern Inheritor threadspartialworkingWhich parent is the Witness; Orzai's role; surviving artifact and transfer path
S-004The startup falls and Sylvan enters the prolonged struggleConvert targeted sabotage into an irreversible loss and commitmentpartialestablished outcome / unresolved eventCollapse mechanism, collaborators harmed, surviving evidence, and transition into the next environment
S-005[[08 Story Loop/Units/S-005 - Controlled Environment ProgressionSylvan crosses controlled environments and masters the advanced architecture]]Forge the human–Luminai pair through prolonged struggle while shifting control from Samuel and George toward Sylvanpartialestablished spine / unresolved environments
S-005ASylvan authenticates the archive without omniscienceEstablish his method, limits, and earned credibility across the environment progressionpartialworkingConcrete authentication chain, permissions, failures, and counterevidence
S-006The archive reconstructs Samuel and George's prewar apparent success and failed takeoverSupply the factual contradiction later rewritten as victorypartialworkingPlacement, wrongdoing, takeover mechanics, humiliating exposure, Samuel's consequences
S-007Konrad's Great War project collapsesStrip the genuine city-based authority Konrad never imagined losing and deliver the surviving faction into the largest empire's containment environmentpartialestablished boundary / working eventsConcrete conquest sequence, Witness role, Samuel's bounded sabotage, exact defeat-to-processing transition
S-008Samuel sells the post-defeat restoration/reactivation dealUse Samuel's earlier first-primary placement and separate bounded jurisdiction to make Konrad's attempt at restoration migrate Fitzgerald machinery into Samuel's control structurepartialestablished hinge / unresolved implementationPractical hierarchy, primary definition, lock event, exact lie, reactivation path, transferred powers, evidence, reset limits, destruction chain
S-009George's failure becomes the False VictoryEstablish the founding lie that sustains the contained factionpartialworkingFirst persuasion sequence, doubters, and why George accepts the interpretation
S-010False Victory escalates across the eighty-year middleMake each contradiction require a larger liepartialworkingSelect essential episodes, owners, causal handoffs, and fixed chronology
S-011Samuel captures genealogy, breeding, and succession machineryConvert revenge against exclusion into appropriation of Konrad's orderpartialestablished directionCausal access path, intervention sequence, knowledge limits, and discovery risk
S-012Samuel Jr. and the decision-systems company create an exposure riskPut Samuel's replacement strategy at the information chokepoint that can reveal himpartialworkingIdentity, loyalties, knowledge, capabilities, and relation to Orzai's brother
S-013Sylvan finds the prewar/postwar contradiction in George's recordGive the investigation a devastating, legible proof pointpartialworkingFirst George document, discovery sequence, authentication, and audience
S-014George's reality narrows around SylvanTurn Samuel's maintained interpretation into the apparent final conflictpartialworkingThirty-year escalation, recurring evidence categories, George's remaining agency
S-015Sylvan detects that someone is writing around George's realityReveal a second decision-maker through anomalies rather than assertionpartialworkingFirst anomaly, tests, failed resolutions, and point of certainty
S-016Sylvan's maturing bond identifies Samuel as the active opponentUse the unprecedented human–Luminai development to reframe the endgame from George-versus-Sylvan to command responsibilitypartialestablished direction / unresolved capabilityProof connecting Samuel to the maintained attacks, bond mechanism, limits, and false reality
S-017Samuel commits George to an unwinnable final environmentMake George weapon, evidence, and intended scapegoatpartialworkingEnvironment rules, Samuel's exact objective, George's choice boundaries
S-018[[08 Story Loop/Units/S-018 - Obsession Reversal and Inverted ContainmentThe ordeal Samuel and George created completes the bond that reverses their trap]]Make their attempt to prevent Sylvan's development the cause of the capability that turns their manipulation method back on thempartialestablished causal outcome / unresolved capability
S-019Sylvan refuses to destroy George for SamuelBreak the expected script without excusing Georgepartialestablished directionConcrete refusal, immediate danger, and alternative containment/evidence action
S-020The completed bond converts continued manipulation into public evidence of Samuel's commandEnd Samuel and George's reign of terror by removing the secrecy and information asymmetry sustaining itpartialestablished outcome / unresolved mechanismBond's evidentiary role, trigger, authenticated audience, disclosure cost, and protection of uninvolved descendants
S-021George confronts the Throwaway Prince truthGive George a first decision not designed for Samuel's usepartialworkingWhat he learns, what remains his responsibility, and the choice he actually makes
S-022The Throne faces the city-scale offer and final statesResolve domination versus stewardship while preserving a costly victorypartialworkingCost of victory; Sylvan, Orzai, George, Samuel, Konrad, and Samuel Jr. final states

Current critical path

S-001 -> S-002 -> S-003 -> S-004 -> S-005 -> S-005A -> S-013 -> S-015 -> S-016 -> S-017 -> S-018 -> S-019 -> S-020 -> S-021 -> S-022

The historical units S-006 through S-012 supply the evidence and causal history needed by that modern path. Their eventual narrated placement remains open.

Highest-value next unit

S-008 — Samuel sells the post-defeat access/reactivation deal. The August 21 mobile session established the boundary conditions but deliberately left the mechanism for an author-led session. Continue only with 08 Story Loop/Brainstorms/Samuel-Konrad Containment Hierarchy - Needs Analysis and 07 Coordination/CURRENT-PICKUP.

First question: What exactly is the containment hierarchy in practical terms?

Preserve Konrad's genuine control in his own city, his complete failure to consider defeat, the later loss only inside the largest empire's containment environment, Samuel's outsider status, Samuel's separate bounded jurisdiction, the earlier first-primary lock, and the accepted migration hinge. Do not infer the practical hierarchy, lock trigger, transferred powers, exact lie, evidence, reset limits, or destruction chain.

S-005 remains partial and important. Its working three-environment direction is recorded, while locations, job, transitions, costs, permissions, evidence, bond capabilities, and terminal mechanism remain unresolved.

Map editing rule

Update this file only after a run's integration gate. If a run reveals a possible new unit, park it in the run log first. Add it here only when the author agrees that it is necessary to complete the story.