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 question helps the author decide a missing cause, character choice, relationship, world rule, or event.
Open a workshop questionAn 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
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.
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 assessment0 / 10major story problems resolved
Story files
Search 605 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.
This is synthesis analysis, not a second author-facing TODO.
| Order | Unit/task | Deliverable | Dependencies | Stop condition | Story Loop route |
|---|---|---|---|---|---|
| 1 | SC-010 | one accepted next setup category | current author answer | stop after exact restatement and acceptance | Story Completion author gate |
| 2 | SC-010 remaining Macro Shape | bounded category coverage result | completion of Question 5 and any required follow-ups | stop before exact scenes or device mechanics | macro-pass |
| Order | Exact author question | Why now | Context packet | Options/research needed |
|---|---|---|---|---|
| 1 | What event activates Samuel's first-primary status? | unlocks the containment truth table | existing hierarchy needs analysis | 2-4 narrow system options after author framing |
| 2 | What does Konrad personally reactivate or migrate? | makes his loss causal and evidenced | S-008 plus hierarchy notes | no new research unless a chosen mechanism needs it |
| 3 | What first anomaly cannot be explained by George? | converts hidden command into story action | S-015 and environment rules | scene alternatives after permission limits |
| Question/ambiguity | Value of leaving open | Revisit trigger |
|---|---|---|
| exact final ritual or venue | prevents premature convergence on an unreviewed possibility | select a lead proof family |
| narrated chronology and viewpoint split | preserves alternate story forms | evidence handoff and causal order stabilize |
| exact command-role grammar | avoids turning research vocabulary into canon | author accepts it as an SC-010 category or later system rule |
Resume at SC-010 Question 5. Do not work the hierarchy questions in parallel with the protected author gate. When SC-010 closes at Macro Shape, return to the existing Samuel-Konrad hierarchy packet one question at a time.