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.

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.

See what the analysis foundSee where development continuesEnter the story

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

What the story needs next

  • Terminal chain
  • Constructive ending
  • Proof and recognition
Follow the full story roadmap

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 07 Coordination/2026-09-05 - Website Rebuild Handoff.md

Document metadata
type: implementation-handoff
status: verified-ready-for-deployment
started: 2026-09-05
updated: 2026-09-06

Integrated vault and website rebuild handoff

Implemented

The explicit author corrections now govern the premise, AI terminology, timeline, character and system boundaries, context, and pickup notes. Historical records remain traceable with supersession notices. The preliminary research brief is preserved with an audit qualifying its technical and security claims.

07 QA/2026-09-05 - Comprehensive Story Assessment contains Astra's central analysis, source conflicts, human stakes, and proposed development sequence. 07 QA/2026-09-05 - Review Coverage records 167 content-reviewed source notes and all unreviewed archive material. The repository inventory covers 610 tracked baseline files.

The public atlas has eight rebuilt pages and a new workshop. The Explorer has a development map, source index, evidence/decision view, and workshop editor while preserving the existing search, document rendering, tree navigation, and progress view. Approved Sylvan, Samuel, and Konrad portraits are reused unchanged.

The workshop has twenty Markdown modules and eighty non-canon alternatives. Each includes prerequisites, sources, a single gate, consequences, follow-ups, scene and adversarial tests, a checklist, and a decision template. The first five recommended preparation sessions are purpose, entry, placement, reconstruction, and generation differences. No task completion changed; SC-010 Question 7 remains the active gate.

Open story decisions

  • Implant-free learned channel versus a physical-interface research path.
  • Which harms are prohibited and which independent authority stops observation.
  • Exact reactivation/permission lock, including the SC-001 Samuel Jr. actor discrepancy.
  • What Sylvan can still lose under decisive control, and George's distinct final role.
  • Authentication, protected disclosure, individual accountability, and placement after exposure.

Open the deliverables

  • Public atlas: docs/index.html.
  • Public workshop: docs/workshop.html.
  • Development workspace: iainreiddotdev/project-explorer/?view=overview.
  • Full workshop editor: iainreiddotdev/project-explorer/?view=workshop.
  • Durable modules: 07 Coordination/Story Completion Workflow/Workshop/.

Use an HTTP server for interactive pages. Draft answers save only in the current browser/origin; export Markdown to preserve or transfer them. Nothing in the editor writes or approves vault canon.

Verification

Completed: generated content hashes, local HTML links/assets/anchors, all twenty module schemas and source links, curated stale-claim checks, JavaScript syntax, PHP 8.2 syntax, and PHP HTTP responses for all four development views, search, and document rendering. A traversal request returns 404.

Final Chromium verification passed across 32 desktop/mobile route checks at 320px and 1440px. Menu keyboard behavior, draft persistence across reload and module changes, Markdown export/import, packet disclosure, Explorer search, traversal rejection, and unavailable-storage handling passed with no JavaScript errors. Legacy Ideas and Visuals mobile overflow was found and fixed. Representative atlas, workbench, and workshop renders were visually inspected. This is not a full screen-reader audit or real-device Safari test. See 07 QA/2026-09-06 - Website Verification. The build and checks are documented in scripts/README.

Synchronization and approval

The initial cloud checkout and a later pre-publication fetch both matched origin/main at 3ae563dbf296477f98410870627af733bf32f0bf. This does not verify the author's Mac vault. Existing remote work was preserved; no conflict was guessed away.

The author's later instruction, “when you are finished, publish to github so i can deploy,” authorizes a commit and push after verification, superseding the original hold on GitHub publication. Hosting deployment remains with the author. A push may trigger the repository's existing GitHub Pages workflow; this run does not change its configuration or operate cPanel.

Deployment handoff

After the final push is confirmed, fetch/pull the repository on the desktop, preserving any local changes. Review a clean fast-forward before deploying. Run the documented build/check commands if changing source content; generated assets are already committed.

Use the existing cPanel Git deployment for the updated main revision. The existing .cpanel.yml archives the complete committed repository into its configured deployment root. Keep docs/, iainreiddotdev/, and the Markdown vault from the same revision. After deployment, verify the September 5 integrated review, workshop module 11, export/import, and source search. Deployment success is not claimed by this handoff.