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.

Explore the vault See how the story is being built Browse the story files
Interpretive still life of recovered records aligned against hidden-system evidence.

Recovered records held against the working evidence.

Current project summary

A colonization world tests who can be trusted with power.

Seeds of the Throne is a science-fiction series about an interactive colonization planet built to create resources, support civilization, train people for greater responsibility, and contain dangerous criminals. The story begins near the end of a conflict that has been unfolding across generations.

The world
Planet Three is a mature containment-and-cultivation world. Its criminal empires have real local power, but they do not control the larger process or its outer limits.
The human future
Sylvan and Orzai form separate bonds with a new generation of Luminai, advanced artificial cognition integrated with an accountable human mind. Their choices test whether this partnership is ready for life beyond containment.
The central conflict
Samuel Franklin has spent decades controlling people by controlling the explanation around them. Sylvan, the Luminai, and an independent Resistance must reconnect the evidence Samuel divided across families, institutions, and generations.
The current endgame
Samuel promises George White and Aiden Fitzgerald the same godlike authority, aims them at each other, and applies an existing prophecy to Sylvan. Their supposed superweapon fails as Sylvan publicly exposes the con, the bloodline betrayal, and Samuel's manufactured reality.
The Resistance
Its black-and-orange ark represents sanctuary and the preservation of people, belief, culture, memory, testimony, and truth through persecution. It preserves what must survive without claiming a right to rule.
What is being developed now
The ending foundation is established. The live workshop is defining the exact superweapon mechanism, the evidence that breaks its credibility, and the independent choices that let the trapped leaders fight their way out against Samuel.

Read the story overviewRead the complete current stateRead the latest accepted decisionsOpen the current assessment

Black-and-orange Resistance infographic centered on an ark preserving people, belief, culture, memory, testimony, and sanctuary through persecution.
The Resistance. The ark preserves people and truth through persecution without claiming supremacy.
Infographic showing Samuel outside an altered reality, George White, Konrad Fitzgerald, Aiden Fitzgerald, and other leaders trapped inside it, and Sylvan standing outside their hierarchy as the leaders recognize Samuel as the deceiver.
Trapped inside Samuel's altered reality. The leaders recognize Samuel as the deceiver and must fight their way out against him.

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 Dynamic Story Workshop asks the one question that matters now.

    Each desktop assessment updates the baseline, records new decisions, checks compatibility, and replaces the next question when the answer changes the story.

    Open the current assessment

  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.

See the latest assessmentSee where development continuesEnter the story

Vault overview

See the whole story-development system at a glance.

717 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, one current workshop, research, and checked public projections operate.
  • Needs repair Decision impact reporting and full browser-size automation still require manual work.
  • 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 with preserved author decisions
  • Decisions, contradictions, and open questions
  • Visual identity and image controls
  • Markdown files and recoverable history
  • Searchable file access
  • One live dynamic workshop and a verified public projection

Needs repair

  • Shared labels and stable record identifiers
  • Automatic decision impact reports across every affected note
  • Keeping the weekly cycle current
  • Clearer boundaries around older folders
  • A cleaner split between the repository and the live site
  • A stable browser-test dependency for every required screen size

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. Normalize the records for one small complete path.
  2. Automate the affected-file report for accepted decisions.
  3. Bundle reliable browser checks for every required screen size.
  4. Prove one complete path from conversation to approved manuscript material.
  5. 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, while an independent resistance network reconstructs the history Samuel kept divided across people and systems.

The current story problem Define what made the supposed superweapon appear effective while Sylvan was severely disadvantaged and what verifiable change made it fail once he began publicly exposing Samuel.

Read the latest focused assessment

The project no longer treats a fixed checklist percentage as the live story state. The Dynamic Story Workshop carries one current assessment question and updates its baseline after every accepted answer.

Open the current assessment

Story files

Browse the files used to develop the story.

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

Current document 07 QA/2026-09-21 - Public Story and Explorer Update Verification.md

Document metadata
type: qa-report
status: complete-with-limitation
date: 2026-09-21
scope: public-story-site-project-explorer

Public Story and Explorer Update Verification

Verdict

The Story pages and Project Explorer now project the 2026-09-21 canon state from one current Dynamic Story Workshop. The Resistance identity, duplicated-throne endgame con, superweapon failure, bloodline betrayal, and escape reversal are visible in the appropriate public surfaces. Older Book One and Endgame workshop packets remain accessible as historical development records rather than competing current workflows.

Source and build verification

  • Dynamic workshop contract tests: passed, 14 tests.
  • Story-site build: passed, producing 8 Atlas pages, 1 live Dynamic module, 22 historical workshop modules, and 73 tracked projections.
  • Story-site consistency checker: passed for local links, assets, anchors, generated hashes, dynamic workshop source agreement, and curated canon markers.
  • JavaScript syntax checks: passed for the public workshop and Project Explorer.
  • PHP syntax checks: passed for the Project Explorer index, workbench, and vault overview.
  • Whitespace and patch integrity check: passed.

Visual review

The following local routes were inspected in the available in-app browser at approximately 590 pixels wide:

  • Story home: current Resistance infographic, ark explanation, endgame framing, and Dynamic Story Workshop entry point rendered without visible horizontal overflow.
  • Dynamic Story Workshop: DW-01 loaded as the only live assessment, with the current gate, source context, response area, and export controls readable at the inspected width.
  • Project Explorer workshop view: the Dynamic workshop, latest canon feature, Resistance image, updated vault links, and current assessment language all rendered coherently.

The automated multi-viewport browser suite could not run because the repository does not currently provide its Playwright dependency. No dependency was installed during this content update. Full automated captures at 320, 430, 1024, and 1440 pixels therefore remain a known verification gap; the direct responsive browser review and source-level checks passed.

Projection decisions

  • The Resistance's black-and-orange ark identity is suitable for the public story site because it expresses sanctuary, testimony, and cultural preservation without disclosing private process notes.
  • The duplicated promise to George White and Aiden Fitzgerald is treated as spoiler-visible endgame canon.
  • The apparent superweapon's dependence on Sylvan's disadvantage, its failure during public exposure, and the bloodline betrayal are treated as spoiler-visible endgame canon.
  • The Dynamic Story Workshop and update system are development-process material and are visible in Project Explorer and the public development pages.

Files governing the next update

  • 07 Coordination/Story Completion Workflow/DYNAMIC-WORKSHOP.md is the only live workshop.
  • 07 Coordination/PUBLIC-SITE-UPDATE-SYSTEM.md defines the repeatable assessment-to-publication process.
  • scripts/build_story_sites.py creates the public projections.
  • scripts/check_story_sites.py checks drift, links, assets, and required canon markers.

Project Explorer summary follow-up

After review, the focused “one con, two promises” feature was identified as too narrow to represent the current project. The Explorer overview now places a project-wide current-state summary before the authoring-system explanation. It covers the world, the human and Luminai future, the central conflict, the current endgame, the Resistance, and the next development work. The duplicated promise remains visible as one part of the endgame rather than standing in for the entire project.

The revised summary was visually and structurally checked at 320, 375, 430, 768, 1024, and 1440 CSS pixels. The page and body widths matched every viewport, the summary changed from one column to two only when space allowed, and all summary links remained inside the viewport. The 320-pixel rendered review showed clear reading order and no visible horizontal overflow.