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 single endgame function belongs to George, and what different function belongs to Konrad?
The workshop considered giving George corroboration, refusal, command identification, or protection of another person. The initial recommendation was a final refusal. The author rejected that direction and tied George directly to the terminal godhood campaign.
Established George function: Samuel drags George into his final attempt to become a living god and positions George as the scapegoat.
George is not granted a convenient redemptive refusal that closes Samuel's channel. Samuel uses George's physical presence, prior participation, public role, and accumulated culpability to make him the visible carrier of the terminal attempt and the person who can absorb blame when it fails.
This joins Samuel's two endgame needs. George helps give the apocalyptic campaign a living operational presence on Sylvan's planet, while the same involvement gives Samuel a target onto whom he can push responsibility for the collapse.
Established Konrad function: Konrad is forced out of the story environment that has enclosed him for almost a century and into direct contact with the reality of Samuel's conduct. His function is confrontation rather than a sudden redemptive act.
The most intense focus is the connected evidence of Samuel's reproductive and genealogical campaign against the faction's bloodlines. Konrad experiences this through his own ideology as the destruction of what he called bloodline purity; objectively, the wrongdoing is Samuel's reproductive abuse, falsification, unauthorized intervention, coercion, and instrumentalization of descendants. No child or mixed ancestry is pollution.
Konrad does not need an immediate final choice for this module. His forced return to reality demonstrates how completely Samuel captured him and collapses the false victory in which he has lived. What he says, refuses, admits, or attempts afterward remains open.
Established consequence: Konrad still possesses substantial influence inside the containment environment. His confrontation is therefore not passive closure. Whatever final moves he makes after encountering the truth will materially affect the older contained leaders, Samuel's remaining position, and the next state of the environment. The exact moves remain open for later scene development.
George's distinct function is scapegoat rather than witness or savior:
Samuel cannot act physically on Sylvan's planet -> George is dragged into the godhood attempt -> the attempt fails -> Samuel assigns the visible failure and wrongdoing to George
The exact acts George performs, what he understands, what he chooses voluntarily, and whether he eventually recognizes the sacrificial design remain open. His scapegoat status does not erase responsibility for actions he knowingly takes.
Konrad's distinct function is confrontation:
almost a century inside Samuel's story environment -> removal into shared reality -> connected bloodline evidence brought into focus -> false victory collapses
The two roles do not compete. George is pulled deeper into Samuel's final fantasy; Konrad is pulled out of the older fantasy and made to face what it concealed.