Project Explorer · working sheet
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.
Recovered records held against the working evidence.
Story development tools
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.
The system records those ideas and separates confirmed decisions from suggestions and unanswered questions.
Read how the system is designedEach answer establishes a cause, character choice, relationship, world rule, or event while keeping exact scene work visible.
Review the ten decisionsAn accepted decision can update character notes, the timeline, world rules, plot events, and the list of remaining questions.
Review decisions and supporting informationThe 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 planSeeds of the Throne is the working example. The notes, decisions, and workshop below are the live project, not a demonstration mockup.
Vault overview
615 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.
Conversations, mobile notes, and raw ideas are preserved.
Current context and compiled notes explain what the project means now.
Workshops ask one important question and preserve the author's answer.
Research, alternatives, story structure, and focused tests strengthen the work.
Scene plans, prose, images, and manuscript material are produced for review.
Selected material becomes the story site, Project Explorer, and public posts.
Each area has a job. Folder names are secondary detail.
Preserves incoming ideas and the order in which they developed.
00 Inbox, 01 Sessions
Keeps the detailed working knowledge and a smaller briefing used to resume work.
02 Story, 03 Context
Separates questions, reports, and usable findings from story decisions.
04 Research
Holds reviewed material prepared for readers.
05 Public
Holds scenes and manuscript candidates awaiting review.
06 Draft
Records choices, contradictions, current work, handoffs, and verification.
07 QA, 07 Coordination
Diagnoses missing connections and tests possible story directions.
08 Story Loop, 09 Story Exploration
Provides repeatable methods for writing, research, images, websites, and checks.
skills, scripts
Current story development
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
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 assessment10 / 10major story problems resolved
Story files
Search 615 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.
What exact completed condition makes Samuel's formal separation from Sylvan inevitable?
The workshop considered a qualification threshold, a final-refusal trigger, an evidence threshold, and a combined threshold. The accepted direction combines completed bonds, independently demonstrated qualification, voluntary partnership under interference, and final refusal as confirmation.
Established: Sylvan and Orzai complete the process when their individual human–Luminai bonds, preserved voluntary partnership, and demonstrated conduct satisfy the pre-established requirements for earned placement.
The process's assessment framework certifies that completed state and automatically executes the transition. Sylvan's final refusal of Samuel's bargain confirms that he will not renew controlled dependence, but the refusal does not create the qualification or function as a magical trigger.
The observable state change is immediate and irreversible:
Samuel cannot delay the transition by proposing another bargain or reinterpreting the outcome because certification has already completed.
The author accepted this direction with: “That's good.”
The final refusal is the human character beat that makes the completed qualification visible. The assessment and separation machinery must be established earlier enough that the audience understands why the transition cannot be reversed. The final room does not need to understand every score; the locked placement status, revoked access, and activated independent allocation make the result observable.