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.

Interpretive still life of recovered records aligned against hidden-system evidence.

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.

Read the story overviewRead the complete current stateRead the latest accepted decisionsOpen the current assessment

Black-and-orange Resistance infographic centered on an ark preserving people, belief, culture, memory, testimony, and sanctuary through persecution.
The Resistance. The ark preserves people and truth through persecution without claiming supremacy.
Infographic showing Samuel outside an altered reality, George White, Konrad Fitzgerald, Aiden Fitzgerald, and other leaders trapped inside it, and Sylvan standing outside their hierarchy as the leaders recognize Samuel as the deceiver.
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.

  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 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.

    Open the current assessment
  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.

Vault overview

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.
  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 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 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. Normalize the records for one small complete path.
  2. Automate the affected-file report for accepted decisions.
  3. Bundle reliable browser checks for every required screen size.
  4. Prove one complete path from conversation to approved manuscript material.
  5. 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.

Read the latest focused assessment

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.

Open the current assessment

Story files

Browse the files used to develop the story.

Search 717 documents about the world, characters, plot, research, decisions, workshops, and earlier ideas.

Current document 07 Coordination/Authoring System/Voice Key Guided Transcript Workshop.md

Voice Key Guided Transcript Workshop

Purpose

Collect enough varied, guided speech and creative-choice reasoning to improve Voice Key's four functional layers:

  1. Authorial Decision Fingerprint;
  2. Prose Topology Profile;
  3. Residue Filter;
  4. Pattern Memory.

The workshop does not train the system to reproduce raw speech. It uses conversation to discover how the author prefers information to be selected, arranged, emphasized, demonstrated, left implicit, and concluded.

Status and priority boundary

This workshop is planned for later. It does not replace the active Dynamic Story Workshop or change its author gate. Start it only when the author explicitly says Open the Voice Key workshop.

Format

  • Eight modules.
  • Approximately 10–15 minutes of dictation per module.
  • Modules may be completed separately across several sessions.
  • Ask one prompt at a time.
  • Use natural follow-ups rather than reading a long questionnaire.
  • Do not name the trait being tested before the response.
  • Preserve exact dictation and a separate lightly corrected transcript.
  • Keep at least one complete response per dimension out of profile extraction for later validation.
  • End each module with a short reflection, not a large trait-approval screen.

Estimated complete workshop time: 80–120 minutes across multiple sessions.

Why the workshop mixes tasks

Natural monologues reveal attention, causal reasoning, certainty, and explanation habits. Comparative decisions reveal preferences more directly. Editing reactions reveal prose topology and residue sensitivity. Project-specific tests show whether a general preference improves Seeds rather than merely fitting unrelated conversation.

No single mode is allowed to define the fingerprint.

Module sequence

ModulePrimary evidenceHeld-out element
VKW-01 Natural reasoningunperformed explanation across unrelated topicsfinal topic response
VKW-02 Attention and relevancewhat receives space and what gets ignoredone unfamiliar source
VKW-03 Causality and constraintsbelievable consequence and redirectionone counterfactual problem
VKW-04 Evidence and judgmentwhat makes conclusions convincingone ambiguous case
VKW-05 Reveal and surpriseinformation order and earned non-default choicesone blind reveal comparison
VKW-06 Ambiguity and closurerequired answers versus productive opennessone unfamiliar ending
VKW-07 Prose topology and residuerhythm, structure, vocabulary, and summary preferencesone unseen prose set
VKW-08 Seeds calibrationproject-specific selection and blind passage testingfinal three-way comparison

VKW-01 — Natural reasoning

Goal

Collect unperformed speech across unrelated subjects without asking the author to sound literary.

Prompt types

  1. Explain a system or routine that outsiders misunderstand.
  2. Describe an idea that changed after encountering practical limits.
  3. Tell a story whose meaning became clear gradually.
  4. Defend a judgment that depends on the purpose of the activity.

Follow-up behavior

Use questions such as:

  • What changed your interpretation?
  • Which part mattered more than it appeared to at first?
  • What would somebody misunderstand about that?
  • What happened because of that limitation?
  • What would count as success in that situation?

Do not suggest a desired answer shape.

Output

  • raw transcripts;
  • corrected transcripts;
  • candidate attention and causal traits;
  • certainty contour;
  • possible topic-specific contamination;
  • one untouched held-out response.

VKW-02 — Attention and relevance

Goal

Learn which information the author expands, compresses, or ignores.

Exercise

Present two short source packets containing more facts than a finished passage needs. Ask the author to dictate:

  1. what the passage is really about;
  2. which three details deserve the most space;
  3. which details can be removed;
  4. which apparently minor detail may become important;
  5. how the information should open.

Use one practical subject and one fictional subject. Keep a third packet held out.

Follow-ups

  • Why does that detail deserve more space?
  • What can the reader safely infer?
  • Which fact looks important but is actually decoration?
  • If only one detail could remain, which one carries the argument?

Output

  • attention weights;
  • omission profile;
  • specificity rhythm;
  • high-resolution-detail preference;
  • compression boundaries.

VKW-03 — Causality and constraints

Goal

Learn what makes change, failure, escalation, and surprise feel earned.

Exercise

Present a goal, available resources, system rules, and a new obstacle. Offer several possible next developments without labeling them. Ask the author to choose, combine, or replace them and explain the causal chain aloud.

Run three versions:

  • an everyday planning problem;
  • a technology or institutional problem;
  • a fictional conflict unrelated to Seeds.

Follow-ups

  • Which consequence feels convenient?
  • What cost should the workaround create?
  • Which limitation would genuinely redirect the plan?
  • What would make the surprising option feel inevitable afterward?

Output

  • constraint sensitivity;
  • preferred causal-chain depth;
  • coincidence tolerance;
  • workaround-cost preference;
  • surprise legitimacy rules.

VKW-04 — Evidence and judgment

Goal

Learn what must be shown before the author accepts a conclusion and how the author evaluates competing interpretations.

Exercise

Present several ambiguous situations containing testimony, behavior, records, incentives, and system outputs. Ask the author what can be concluded, what remains uncertain, and what additional evidence would change the judgment.

Do not use real criminal allegations or private individuals. Use invented or ordinary low-stakes situations.

Follow-ups

  • Which evidence is strongest, and why?
  • What are we being asked to assume?
  • What would make this conclusion premature?
  • Are the two sides measuring success differently?
  • What fact would reverse your judgment?

Output

  • evidence hierarchy;
  • certainty thresholds;
  • correction pattern;
  • competing-goal sensitivity;
  • qualification behavior.

VKW-05 — Reveal and surprise

Goal

Learn preferred information order independently of prose wording.

Exercise

For the same approved facts, present several reveal maps:

  • conclusion before evidence;
  • evidence before interpretation;
  • consequence before cause;
  • focal character misunderstanding before correction;
  • ordinary expectation before a system exception.

Ask the author to select or combine a route and explain when the reader should understand more than the focal character.

Follow-ups

  • What should the reader know first?
  • Which fact changes the meaning of what came before?
  • Is this suspense or merely missing information?
  • Where does surprise become manipulation?
  • Which version would remain interesting on rereading?

Output

  • reveal-order distribution;
  • delayed-recognition preference;
  • reread-value preference;
  • suspense versus confusion boundary;
  • earned-surprise profile.

VKW-06 — Ambiguity and closure

Goal

Learn what a passage, scene, or ending owes the audience and what may remain open.

Exercise

Present several short ending summaries with different levels of resolution. Ask the author to identify:

  • the primary promise;
  • the questions that must close;
  • the questions that may remain open;
  • the difference between future possibility and unfinished work;
  • the emotional consequence that should be demonstrated rather than explained.

Follow-ups

  • What would make this feel evasive?
  • Which unanswered question expands the story?
  • What should change permanently by the end?
  • Does the ending flow from the story or impose an effect on it?

Output

  • closure hierarchy;
  • open-perimeter tolerance;
  • required-state-change preference;
  • emotional-resolution preference;
  • ambiguity limits.

VKW-07 — Prose topology and residue

Goal

Learn the shape of writing the author finds effective without asking the author to produce polished prose.

Exercise

Present unlabeled versions of the same passage that vary only in selected dimensions:

  • uniform versus varied sentence lengths;
  • full sentences versus purposeful fragments;
  • balanced versus asymmetrical attention;
  • early versus delayed thesis;
  • explicit transitions versus logical proximity;
  • three-item versus irregular lists;
  • summarized versus pressure-changing paragraph endings;
  • abstract dramatic language versus concrete verbs and nouns.

Ask for spoken reactions, combination requests, and exact reasons. Do not identify one version as human or AI.

Follow-ups

  • Where did your attention drop?
  • Which sentence feels too written by a system?
  • Which irregularity improves the passage, and which feels performed?
  • What should be deleted rather than rewritten?
  • Does this ending conclude the thought or merely repeat it?

Output

  • sentence-length distribution preference;
  • fragment triggers;
  • paragraph-shape profile;
  • transition density;
  • list and symmetry tolerance;
  • thesis-position range;
  • project residue lexicon;
  • delete-versus-rewrite preference.

VKW-08 — Seeds calibration

Goal

Determine whether the extracted fingerprint improves actual Seeds of the Throne writing.

Required preparation

Use one approved scene contract and lock its facts, POV knowledge, revelation ceiling, entering state, and resulting state. The Book One outcome-presentation vertical slice remains the preferred first test when structurally ready.

Blind comparison

Create three unlabeled passages:

  1. strong project-aware baseline;
  2. surface speech-profile revision;
  3. Voice Key authorial-selection and prose-topology version.

Randomize their order. Keep length, facts, and scene purpose comparable.

Evaluation questions

  • Which passage is best?
  • Which feels most specific to Seeds?
  • Which makes the strongest presentation decisions?
  • Which cause-and-effect chain is most convincing?
  • Which contains an earned surprise?
  • Which feels polished but generic?
  • What should be combined?
  • Which exact decision should Voice Key remember?

Output

  • blind preference;
  • project-fit evidence;
  • accepted and rejected modifiers;
  • passage-level corrections;
  • updated confidence;
  • new held-out benchmark.

Capture model

Each response preserves three separate layers:

LayerContents
Sourceexact prompt, raw dictation, corrections, and situational context
Understandingcandidate trait, evidence, confidence, competing interpretation, and possible topic bias
Useproposed general preference, project modifier, topology range, residue rule, or no promotion

No inferred trait becomes active merely because it appears once.

Proposed evidence lifecycle

  1. Observed: appears in one response.
  2. Candidate: appears across two unrelated contexts or one explicit comparison.
  3. Working: survives a counterexample and improves a blind output.
  4. Author-approved: the author confirms the useful decision in plain language.
  5. Project-active: has a defined scope, trigger, and recent-use control.
  6. Revised or retired: later feedback weakens, narrows, contradicts, or removes it.

These stages prevent a single anecdote or speaking habit from becoming a permanent writing rule.

Training and validation split

  • Split by complete response or exercise, never random sentences from the same answer.
  • Do not use held-out responses to extract or phrase the profile before evaluation.
  • Keep general-profile validation separate from Seeds-specific validation.
  • Preserve at least one negative example showing when a normally preferred technique should not be used.
  • Re-run blind tests after major profile changes.

Pattern-memory capture

During every comparison, record whether the author rejects a passage because a device is intrinsically weak or because it appeared too recently. Store those as different findings.

The workshop should identify acceptable repetition windows for:

  • fragments;
  • short punchline conclusions;
  • delayed theses;
  • evidence-first reveals;
  • three-part lists;
  • contrast constructions;
  • abrupt paragraph endings;
  • behavioral emotion;
  • open questions.

Exact numerical windows remain an implementation test rather than an interview demand.

Success criteria

The workshop succeeds when it produces:

  • evidence across unrelated topics and actual project material;
  • at least one supported trait in each core fingerprint dimension or an explicit finding that the dimension should remain neutral;
  • a project-specific topology profile that does not imitate raw dictation;
  • negative preferences and counterexamples, not only positive rules;
  • a held-out validation set;
  • one blind comparison preferred for quality and project specificity;
  • no canon changes hidden inside writing preferences;
  • a clear list of traits still too uncertain to activate.

Stop and resume behavior

At the end of each module, record:

  • module completed;
  • raw sources captured;
  • held-out material protected;
  • candidate findings;
  • unresolved contradictions;
  • exact next prompt.

The author may stop after any response. Resume with a one-paragraph recap and the next single question. Do not repeat completed prompts merely because a new chat begins.

Start command

When the author says Open the Voice Key workshop:

  1. identify the earliest incomplete module;
  2. briefly explain that module's purpose without naming the hidden trait being tested;
  3. ask one natural-language prompt;
  4. wait for dictation;
  5. continue with adaptive follow-ups until the module has sufficient evidence or the author stops.