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 docs/assets/workshop/06.md

06 · Bond development and costs

Purpose

Turn a premise-level breakthrough into lived human change.

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 does not acquire the deeper bond as an instant ability. He and the Luminai develop it through multi-year adversarial loops in which the contained criminals keep attacking him. The advanced systems do not simply end the danger. They give the pair ways to study what is happening, recognize patterns, adapt, reduce the effectiveness of later attacks, and survive.

Each environment changes the conditions and creates different opportunities to learn. The pair carries its learning forward, but a solution that worked in one environment cannot solve every later problem automatically. The recurring cost is sustained time under pressure and continuing exposure to real danger while the pair learns how to use its growing capabilities.

repeated attack → observation → adaptation → reduced harm → environmental transition → a new kind of attack

Relevant source notes

Confirmed facts and current working constraints

  • Human responsibility and consequential conscious decision remain load-bearing.
  • Source discrimination, cross-bond coordination and physical interfacing have accepted setup categories.

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

  • Noninvasive field versus interface hardware and developmental versus adult learning.
  • Which distinct capability or judgment skill each environment teaches.
  • Which specific losses make the years costly rather than merely long.
  • What the pair retains if environmental support is interrupted.
  • Who authorizes transitions and what prevents unacceptable harm during repeated attacks.

Prerequisite decisions

Modules: 02, 04, 05. 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 recurring cost forces Sylvan to learn how to use the bond rather than simply acquire it?

AUTHOR-ACCEPTED: years of sustained adversarial pressure and real danger across changing environments, with survival depending on cumulative observation, adaptation, and chosen use of the advanced systems.

Possibilities and tradeoffs

1. Attention and calibration burden

PROPOSED: Early signals compete with concentration; precision improves through practice. Easy to dramatize, but avoid making exhaustion a convenient switch that changes by scene.

2. Dependence and partial offline loss

PROPOSED: The bond persists while environmental reach narrows. Makes setting matter; distinguish retained human learning from unavailable tools.

3. Maladaptive shared habits

PROPOSED: Both layers learn an expedient shortcut that later fails ethically or perceptually. Gives a real internal arc; correction must be possible without pathologizing Sylvan.

4. Boundary and relationship cost

PROPOSED: Integration changes what Sylvan can keep private or responsibly share. Strong Orzai conflict; avoid treating intimacy as required data access.

Targeted follow-up questions

  • What skill survives disconnection?
  • What can the Luminai do during sleep, and what must wait?
  • Which intervention requires explicit consent to the body itself?

Scene test

Non-canon situation: An urgent signal feels certain, but Sylvan notices the bond is carrying old context; slowing down to recalibrate costs him a practical advantage.

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

Adversarial questions

  • If the Luminai can persuade Sylvan through subconscious channels, what makes his conscious approval meaningful?
  • 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, 04, 05.
  • [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: 06 · Bond development and costs
Gate: What recurring cost forces Sylvan to learn how to use the bond rather than simply acquire it?
State: AUTHOR-ACCEPTED
Author answer (verbatim): Preserved in [[01 Sessions/Daily/2026-09-06 - Workshop Module 06 Bond Development Draft]].
Exact restatement: Multi-year adversarial loops force cumulative learning; the systems provide opportunities to adapt, not automatic rescue.
Selected option or new answer: A new answer combining sustained danger, environmental progression, and retained learning.
Why this tradeoff: It turns bond development into the causal spine of Sylvan's prolonged struggle and gives each environment a distinct teaching function.
Rejected alternatives and reasons: A one-time calibration cost or instant capability would not explain the years of attacks or make Sylvan's choices necessary.
Prerequisites resolved / deferred: Modules 02, 04, and 05 are author-accepted; interface hardware, exact costs, safeguards, and transition authority remain deferred.
Scene test: A learned defense reduces one attack; the next environment changes the problem, requiring Sylvan to decide which accumulated lesson transfers.
Adversarial result: Every loop needs a materially different pressure, a retained skill, and a real failure consequence; advanced systems cannot save Sylvan regardless of his choices.
Remaining uncertainty: Environment lessons, losses, offline learning, safety limits, transition authority, and Samuel's power to change tactics or environments.
Explicit acceptance wording and date: “Yes,” 2026-09-06.
Affected notes updated: Learned Wireless Cognitive Channel; Pairing and Bonding; Competitive Environments; Storyline; context; public atlas; workshop projections.
QA decision reference: [[07 QA/Decisions]].
Workflow task and macro-depth effect: Workshop Module 06 closed; SC-010 Question 7 unchanged.
Website rebuild and verification: Generated projections rebuilt and checked after integration.

Notes and website sections affected