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.

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 current workshop asks one consequential question at a time.

    Each question helps the author decide a missing cause, character choice, relationship, world rule, or event.

    Open a workshop question
  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.

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.

  • Working now Capture, memory, workshops, and research already operate.
  • Needs repair Current-state agreement, automatic checks, and decision updates still drift.
  • 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 that wait for an answer
  • Decisions, contradictions, and open questions
  • Visual identity and image controls
  • Markdown files and recoverable history
  • Searchable file access

Needs repair

  • One trustworthy current-state view
  • Automatic checks before a change is merged
  • Shared labels and stable record identifiers
  • Updating every affected note after a decision
  • Keeping the weekly cycle current
  • Clearer boundaries around older folders
  • A cleaner split between the repository and the live site

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. Make builds and checks reliable.
  2. Create one trustworthy current state.
  3. Normalize the records for one small complete path.
  4. Connect accepted decisions to every affected file.
  5. Prove one complete path from conversation to approved manuscript material.
  6. 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, 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 assessment

0 / 10major story problems resolved

Current development pass0%
0%
Current sweep
Reassessment
Current task
RW-01
  1. 01 Reassessment
  2. 02 Causal sequence
  3. 03 Character agency
  4. 04 Systems + evidence
  5. 05 Scene design
  6. 06 Draft

Story files

Browse the files used to develop the story.

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

Current document 02 Story/Artifacts/Journals/Characters/Konrad Fitzgerald/Journal Profile.md

Konrad Fitzgerald — Journal Profile

Authority and scope

Konrad's patriarchal authority, bloodline doctrine, contempt for Samuel, genuine pre-defeat control, brilliant organizational leadership, cult persuasion, authorship of Samuel's impossible mission, and post-defeat migration mistake are established or working story memory. Whether Konrad personally writes the proposed exile artifact and the existence/form of this ledger remain unresolved.

Physical design, handwriting, and diagrams: working visual development, not approved artifact canon. Approved identity or journal references: none. Return NEEDS DEFINITION if a generation requires Konrad's face, hands, exact crest, signature, or family insignia.

Physical identity

  • Working object: a monumental dynastic ledger rather than a confessional diary, approximately 260 × 360 mm and intended for a desk or stand rather than a pocket.
  • Cover: dark oxblood full-grain goatskin stretched over rigid boards, blind-tooled double rules, protected dark-metal corners, and one functional clasp. The central cartouche stays blank until a family mark is approved.
  • Binding: raised bands and a durable sewn structure intended to imply institutional continuity. No invented antique date or manufacturing claim is permitted.
  • Paper: thick warm rag-like leaves with formal vertical ruling, wide inner gutter, numbered folios, and prepared spaces for rank, duty, sanction, and attestation.
  • Instruments: broad-nib dark sepia-black ink for declarations; narrower matching ink for quantities and attestations. No decorative red unless a later administrative code is established.
  • Navigation: generations and jurisdictions receive tabbed edge cuts or restrained linen markers. Headings are centered and more visually dominant than dates.
  • Wear: squared corners soften, clasp contact leaves dark pressure marks, and frequently reaffirmed folios show impressed writing. The object remains maintained even as its claims fail.
  • Unresolved: provenance, exact era, ownership succession, maker, metal composition, cartouche design, and whether any sections are written by clerks or dictated.

Handwriting identity

Large, confident, disciplined, traditional, with strong capitals, straight margins, decisive punctuation, and few visible corrections. Where Samuel draws networks, Konrad writes declarations. Increased pressure should appear as heavier force and sharper terminal marks, not sudden chaos.

Short rhetorical formulations may be drafted and recopied until they appear inevitable. Controlled repetition, parallel syntax, and carefully placed terminal phrases reflect his ability to turn complicated conditions into language followers can carry.

Full construction rules and reusable exercises: 02 Story/Artifacts/Journals/Characters/Konrad Fitzgerald/Writing and Drawing Samples.

Drawing and diagram grammar

Vertical lines of descent, rigid boxes, formal brackets, ordinal ranks, sanctioned and removed branches, sparse territorial or administrative plans. Diagrams presume hierarchy instead of exploring alternatives.

People are classified by role in the order—service, ancestry, reliability, susceptibility to collective grievance, capacity for discipline, and risk of public dissent. Avoid duplicating Samuel's intimate pressure maps: Konrad absorbs a person into a category and shared destiny, while Samuel models the person's unique vulnerabilities.

His unique integration rule is declaration becomes structure: a centered proposition acts as the load-bearing beam for a descending hierarchy, lineage, or territorial classification. Counterevidence can be accurately copied yet placed outside the ruled field, allowing the page itself to deny its power to revise the conclusion.

Recurring motifs

Unbroken line, root and crown, numbered generations, sealed branch, boundary, duty, inheritance, removal without reconsideration, victory through every transition.

Emotional and chronological evolution

StateStory periodWritten/layout changeMeaning
sovereign certaintybefore defeatperfect margins, compressed doctrine, audience and loyalty classificationsReality and family order are presumed permanent; persuasion and administration reinforce one another.
Samuel disposalprewar exileclipped administrative contemptSamuel is beneath rivalry and treated as a problem to remove.
Great War collapsedefeat and processingaccurate material totals paired with euphemistic phase language; no explicit defeat headingKonrad preserves the winner's identity by refusing the event's plain meaning.
false restorationearly containmentolder headings reactivated in a new environment; migration called reclamation or continuationKonrad mistakes continuity of form for continuity of control.
isolationlater middle/endgamestill formal, but with triumphant headings over shrinking totals, missing attestations, harsher loyalty categories, ritual reaffirmations, and proxy marksOrder and victory survive on the page as independent evidence and external reality diverge.

Content and knowledge rules

Konrad writes doctrine and decision, not authorial truth. He cannot record awareness of Samuel's jurisdictional coup before he has evidence of it. His contempt can coexist with technical dependence. He avoids the vocabulary of defeat: withdrawals become consolidations, destroyed structures become completed phases, containment becomes transferred jurisdiction, and dependence becomes delegated implementation. Distinguish entries written by Konrad, dictated by him, countersigned by others, or added by later hands.

Evidence and forensics

Potential evidence includes original exile authorization, program migration approvals, old lineage conventions, missing attestations, later false annotations, differences between Konrad's hand and Samuel's imitations, and the widening contradiction between declining material totals and increasingly triumphant classifications. Authorship and custody remain essential.

Visual generation contract

Preserve disciplined hierarchy, exact transcription, object-version rules, and the absence of accidental introspective remorse. Avoid generic evil scribbles, fascist real-world insignia, ornate fantasy heraldry, omniscient foresight, or treating formal beauty as moral approval.

Approval state

  • [ ] identity reference approved
  • [ ] physical object approved
  • [ ] handwriting sheet approved
  • [ ] diagram sheet approved
  • [ ] crest/ownership mark approved
  • [ ] cover/interior spread approved

Current candidate board and exact sample transcriptions are indexed in 02 Story/Artifacts/Journals/Candidate Images/2026-08-23 - Four Journal Candidate Boards and 02 Story/Artifacts/Journals/Characters/Konrad Fitzgerald/Writing and Drawing Samples.