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.
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.
The Resistance. The ark preserves people and truth through persecution without claiming supremacy.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.
The author explains the story in ordinary language.
The system records those ideas and separates confirmed decisions from suggestions and unanswered questions.
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.
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.
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.
Capture
Conversations, mobile notes, and raw ideas are preserved.
Understand
Current context and compiled notes explain what the project means now.
Decide
Workshops ask one important question and preserve the author's answer.
Develop
Research, alternatives, story structure, and focused tests strengthen the work.
Create
Scene plans, prose, images, and manuscript material are produced for review.
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 nextNot 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
Normalize the records for one small complete path.
Automate the affected-file report for accepted decisions.
Bundle reliable browser checks for every required screen size.
Prove one complete path from conversation to approved manuscript material.
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.
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.
The new decisions are compatible with the governing process boundary and strengthen the endgame causal chain. One direct framing conflict and two scope drifts required explicit reconciliation. The weapon mechanism and exact escape action remain open rather than silently resolved.
Findings
Impact
Class
Finding
Resolution
significant
Contradiction
Older endgame material gave George “divine purpose” and Aiden a distinct “promised reward”; the later author decision gives both the same exclusive godlike destiny.
The latest explicit decision controls. Both receive one throne promised twice. Different subjective framing may remain, but not different final rewards.
significant
Drift
The Resistance note said symbols were unresolved after the author locked black/orange colors and ark imagery.
Updated only the decided visual layer. The final name, organization, and broader internal culture remain unresolved.
significant
Tension
Earlier attack logic aims trapped leaders at Sylvan; the latest direction ends with them targeting Samuel and fighting out.
Preserved these as successive phases: Samuel first aims them at Sylvan; public weapon failure and duplicated-promise evidence reverse the conflict toward Samuel.
significant
Gap
“Superweapon” currently names a claimed function, not an established technology or evidence path.
Left the exact mechanism open and made it the next assessment gate. It may show bounded effects under asymmetry but cannot gain new process-level power.
significant
Gap
“Fight their way out” lacks an operational sequence and could accidentally imply Samuel owns the governing environment.
Constrained it to Samuel's story layer, proxies, dependencies, and local retaliation. Exact actions remain open.
minor
Status
The conversation attachment is neither the Resistance graphic nor the final corrected altered-reality diagram.
Did not import it. The dynamic workshop records the missing asset and approval requirement.
Asset follow-up
The author later supplied a different file: the clean Resistance Ark infographic. That asset was reviewed, approved, stored, and registered in 07 QA/2026-09-21 - Resistance Ark Infographic Visual Review. The finding above remains accurate for the earlier altered-reality attachment and does not apply to the newly supplied Resistance image.
Cross-file checks
Identity: George White and Aiden Fitzgerald remain separate marks with separate agency; Aiden remains Konrad's biological son.
Knowledge: neither mark initially knows the promise was duplicated. Comparison begins only after public failure disrupts Samuel's compartments.
Causality: apparent weapon success under disadvantage leads to belief; failure leads to comparison; comparison leads Samuel to repeat the con; repetition produces new evidence.
Systems: Samuel remains unable to control the governing colonization process. The exact weapon must be resolved within bounded technology and access rules.
Evidence: the Resistance retains indispensable ownership of the historical comparison. Sylvan's public record supplies live evidence rather than replacing the archive.
Theme: exposure attacks counterfeit authority and supremacy, not faith. Ark imagery centers preservation rather than chosenness.
Privacy: the bloodline campaign can be proven only through protected evidence and public patterns that do not expose descendants.
Status: explicit decisions are labeled established; technical and sequencing mechanics remain open.
Link verification scope
Verified the new dynamic workshop's wiki links against the current repository and updated the active workflow pointers. Legacy workshop files remain in place as historical records so inbound links do not break.
