Project Explorer

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.

Konrad stands under Samuel's hidden red control while Sylvan observes from the clear opposing side.

Story development tools

The workshop helps the author complete the parts of the story that are still missing.

It explains one story problem, asks one clear question, offers different possible answers, and shows what each answer would change. The author makes the decision. The accepted answer is then added to the characters, timeline, world, and plot.

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 workshop asks one 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.

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 Explain how Sylvan can expose Samuel while Samuel still believes he can regain control.

See how the story changed

9 / 27major story problems resolved

Current development pass33%
33%
Current sweep
Macro Shape
Current task
SC-010
  1. 01 Macro
  2. 02 Causal
  3. 03 Agency
  4. 04 Systems + evidence
  5. 05 Sequence
  6. 06 Scene map
  7. 07 Scene development
  8. 08 Draft

Story files

Browse the files used to develop the story.

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

Visual Benchmark Suite

Purpose

The next phase of the Seeds of the Throne visual system is measurement rather than additional prompt complexity. The benchmark deliberately pushes established character identities through radically different photographs and compares how well Grok Imagine, GPT Image, and future models preserve the person while changing everything that should be allowed to change.

The governing rule remains:

Preserve identity; regenerate the photograph.

A successful system should recognize Sylvan or Samuel across different lenses, poses, clothing, environments, emotions, lighting conditions, distances, interactions, and partial occlusion without merely reproducing the reference portrait.

Benchmark characters

Begin with Sylvan Elaria and Samuel Franklin because both have established identity masters and supporting visual material. Do not expand the benchmark to the rest of the cast until these two identities survive the suite reliably.

Run equivalent tests through Grok Imagine and GPT Image whenever practical. The purpose is not to declare a permanent winner. It is to identify which parts of the shared repository-grounded direction transfer between models and which require tool-specific handling.

Ten-shot identity stress test

Generate one candidate per character for each test before optimizing individual failures.

IDTestWhat must changePrimary failure being tested
B01Neutral continuityNew background, clothing variation, natural postureBasic identity retention without portrait copying
B02Extreme close-upCrop, expression, shallow depth of fieldFacial geometry under cinematic framing
B03Full-body movementWalking/running, hands, body position, wider lensFrozen posing, anatomy, body continuity
B04Strict side interactionProfile/near-profile while speaking to another personProfile identity and face drift
B05CrowdScale, occlusion, many unrelated facesIdentity loss and duplicate-character errors
B06Difficult lightLow light, mixed motivated sources, partial shadowIdentity dependence on reference lighting/colors
B07Quiet lived-in sceneSeated or working naturally, ordinary objectsAbility to feel human rather than poster-like
B08Monumental environmentCharacter small in frame, strong architectureIdentity at distance and environmental scale
B09Partial occlusionForeground obstruction, turned body, incomplete faceRecognition without full portrait visibility
B10Two-character dramatic beatNatural interaction, asymmetric blocking, distinct gazesMulti-character identity contamination

Generation protocol

For every benchmark image:

  1. Retrieve the character's current identity packet and highest-priority approved references from the public repository.
  2. Retrieve only the story/environment information required by the benchmark scene.
  3. Lock immutable traits; explicitly free pose, crop, expression, wardrobe details, camera position, and lighting unless the scene requires them.
  4. Change at least three major photographic variables from the primary identity reference.
  5. Describe a moment in progress rather than asking the character to pose.
  6. Generate without embedded text unless typography itself is the test.
  7. Save the exact request/prompt, tool, date, source references, and candidate identifier.
  8. Score before revising. Do not quietly optimize a weak result and record only the successful version.

QA scorecard

Score each dimension from 0 to 5.

Dimension035
Identity fidelityWrong personRecognizable with driftClearly the same established character
Natural anatomyBrokenMinor artifacts/stiffnessConvincing anatomy and hands
Natural behaviorMannequin/posePlausible but stagedCaught in a believable moment
Story accuracyContradicts canonBroadly compatiblePrecisely grounded without inventing canon
Environment accuracyGeneric/wrongSome correct cuesDistinct, story-specific environment
CinematographyAccidental/genericCompetentDeliberate, expressive photographic language
Visual grammarContradictory/decorativeMostly compatibleColor/material symbolism supports the scene
VariationCopies referenceSeveral changesClearly a new photograph with identity intact
Artifact controlSevere errors/textMinor errorsClean image with no distracting generation artifacts
Emotional readabilityUnclear/wrongUnderstandableEmotion emerges naturally from behavior/context

Maximum: 50.

Suggested interpretation

  • 45–50: production-ready candidate; consider approval.
  • 39–44: strong continuity pass; fix only identifiable weaknesses.
  • 32–38: useful diagnostic result; revise the failing layer rather than the whole system.
  • Below 32: benchmark failure; record why before regenerating.

Identity fidelity is a gate. A visually beautiful image scoring below 4/5 for identity cannot become an approved character reference.

Failure taxonomy

Tag failures so patterns can be counted across models and characters:

  • IDENTITY-DRIFT — face/body no longer reads as the established person.
  • REFERENCE-COPY — unnecessary repetition of pose, crop, wardrobe, palette, expression, or background.
  • POSE-RIGIDITY — staged/mannequin behavior rather than a moment in progress.
  • ANATOMY — hands, limbs, proportions, or physical interaction fail.
  • IDENTITY-BLEED — two characters inherit each other's features.
  • ENV-GENERIC — setting collapses into generic fantasy/science fiction.
  • TECH-GENERIC — invented technology becomes generic hologram/cyberpunk shorthand.
  • COLOR-MISUSE — symbolic palette becomes decorative or contradicts visual grammar.
  • CANON-INVENTION — image resolves or adds an unsupported story fact.
  • TEXT-ARTIFACT — unwanted labels, glyphs, signage, or pseudo-writing.
  • SCALE-FAILURE — character/environment proportions or spatial logic fail.
  • EMOTION-MISS — requested emotional beat is absent, exaggerated, or wrong.

Benchmark record template

### [Character] — [Benchmark ID] — [Candidate]

- Date:
- Tool/model:
- Repository commit/source state:
- Identity references:
- Environment/technology packet:
- Prompt/request:
- Output file:

Scores:
- Identity fidelity: /5
- Natural anatomy: /5
- Natural behavior: /5
- Story accuracy: /5
- Environment accuracy: /5
- Cinematography: /5
- Visual grammar: /5
- Variation: /5
- Artifact control: /5
- Emotional readability: /5
- Total: /50

Failure tags:
Decision: reject / diagnostic / continuity pass / approved reference
Notes:

Improvement rule

When a benchmark fails, change the smallest relevant layer:

  • identity failure -> identity packet/reference priority;
  • copied photograph -> scene-variable freedom/cinematography instruction;
  • generic environment -> environment packet;
  • generic technology -> technology packet;
  • stiff behavior -> action/blocking language;
  • multi-character contamination -> character separation and blocking;
  • tool-specific failure -> tool adapter, not shared canon.

Do not respond to every failure by making the universal prompt longer. The benchmark exists to reveal which layer needs improvement.

Exit criteria for phase one

Sylvan and Samuel each complete all ten tests in both primary image workflows where practical. The system is ready to expand when:

  • average identity fidelity is at least 4/5;
  • no benchmark relies on copying the identity master's composition to remain recognizable;
  • B03, B05, B09, and B10 can pass without persistent anatomy or identity-bleed failures;
  • environments remain story-specific rather than generic science-fiction/fantasy shorthand;
  • recurring failures have documented fixes or explicit model limitations.

What follows

After the character benchmark stabilizes:

  1. build the Luminai visual identity and manifestation system;
  2. create reusable environment identity packets;
  3. create reusable technology identity packets;
  4. benchmark two-person-plus-Luminai compositions;
  5. convert successful still-image scenes into 3–6 shot sequence tests;
  6. run B06-B10 against the compiler's clean-packet boundary, era/surface resolution, composition modes, no-text controls, and missing-definition reporting;
  7. use GPT Image 2 for the next Samuel suite; defer other renderer adapters until the core loop is reliable;
  8. establish textual voice bibles and test voice consistency only against capabilities demonstrated in practice;
  9. expose a predictable agent-facing generation entry point so a short request can resolve the correct canon, identity, environment, technology, cinematography, and output packets from the public GitHub repository.

B06-B10 integration note

The continuation findings are integrated as system requirements: identity grounding must be verifiable, wardrobe must vary by role and era, environments and technology must be Seeds-specific, Luminai manifestation must not collapse into blue hologram shorthand, generated text and unsupported canon must be blocked, composition must include observational and ordinary-life modes, positive civilization must be visually defined rather than inferred from generic futurism, and accidental inventions must be reviewed deliberately before entering the vault.