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

Project Explorer

Seeds of the Throne

Inspect the corrected story, trace unresolved causes, and work through source-linked brainstorming packets. The repository browser remains available below.

Development workspace · September 6 workshop pass

Find the cause. Test the choice.

All twenty workshop gates have accepted directions. Their unresolved mechanics remain visible. The active Story Completion gate remains SC-010 Question 7.

Public, read-only development material with full spoilers. Draft answers stay in your browser until exported; they do not update the vault. A spoiler boundary is not privacy protection.

01 · Foundation

The environment creates the bond.

The leaders developed Luminai within an interactive colonization environment. Sylvan tests a more deeply integrated generation after thousands of years of development.

Inspect the controlling premise
02 · Institutional gap

Control must protect people.

Final-years control is established. Stopping authority, cumulative harm, privacy, and remedies still need concrete rules.

Test the leaders' safeguards
03 · Causal result

Autonomy becomes access.

Konrad's Daemon verifies an apparent separation. Konrad authorizes reactivation, which attaches his revived system to Samuel's hidden hierarchy. The false evidence still needs definition.

Inspect the takeover result
04 · Two-planet endgame

George goes where Samuel cannot.

Samuel and the older criminals remain on the previous containment planet. George participates directly on Sylvan's world, then becomes Samuel's intended scapegoat.

Inspect George's role

Story completion · Live from the vault

From architecture to manuscript.

The story advances horizontally: every active problem receives the same level of development before any one branch moves deeper.

Integrated foundation review · September 5, 2026

The environment develops the bond. The outcome tests responsibility.

The leaders created an interactive colonization environment and developed Luminai within it. Konrad tries to prove his experienced daemon superior; Samuel turns his reactivation into access. Sylvan already has decisive control during the final years. Exact safeguards and presentation mechanics remain open.

Current method Bound action, observe the method, compare the record, expose the hidden command.

Read the foundation update record

9 / 27story tasks complete

Current checklist completion33%
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

Project explorer

Browse the repository.

Search or browse 539 documents across canon, development systems, story loops, prose tools, public work, and session history.

5.0 KB Updated View source on GitHub

Public site gauntlet — 2026-08-24

Design contract

  • Visual thesis: an editorial science-fiction field guide where darkness is the unknown, warm ivory is the recoverable record, and signal-gold marks paths back to reality.
  • Content hierarchy: story promise → human conflict → world and cognition → evidence/conspiracy → author-controlled development → live progress.
  • Interaction thesis: a quiet first-view reveal, one navigable story-path line, and native disclosure for high-spoiler or deep-development material. Motion never carries meaning and is disabled by reduced-motion preference.
  • Public spoiler boundary: the premise, core cast, dual-purpose colony, Luminai/Daemon contrast, startup collapse, historical conspiracy, and evidence theme are public. Private criminal-history details, sensitive family mechanics, exact endgame disposal and proof mechanisms, unresolved hierarchy mechanics, and unapproved artifact text stay out of promotional pages. Deep structural spoilers require an explicit disclosure action.

Scorecard

Dimensions are scored 1–5: story clarity, narrative pull, world connectivity, visual thesis, navigation, accessibility, status honesty, and progress integrity.

PassStoryPullConnectionsVisualNavigationA11yStatusProgressTotal
Baseline3232222420 / 40
Cycle 14442434530 / 40
Cycle 24555445537 / 40
Cycle 34555555539 / 40

Baseline findings

  • The opening copy is atmospheric but long, low contrast, and more abstract than the central dramatic situation.
  • Nine equally weighted navigation destinations create label conflict and decision fatigue.
  • Dossier grids repeat across pages, making story, world, and development pages feel structurally interchangeable.
  • Some pages publicly expose material the synthesis explicitly says not to publish.
  • Several established/working/unresolved labels overstate details or combine status categories unclearly.
  • The weekly dashboard correctly reads repository Markdown, but its source link is hard-coded to one dated run.
  • Mobile navigation depends on JavaScript and the closed state leaves almost no orientation in the first viewport.

Cycle log

Cycle 1 — narrative and information architecture

Status: complete.

Goal: make the story exciting before explaining the vault, give every page one job, reduce repeated exposition, and enforce the spoiler boundary.

Delta: rewrote the opening around Sylvan's destroyed company and the hidden maintainer; reduced the primary navigation to stable destination language; removed unsafe promotional details; replaced repeated summaries with distinct world, cognition, character, conspiracy, chronology, development, visual, and progress routes; added explicit status language at the point of uncertainty.

Cycle 2 — editorial visual system

Status: complete.

Goal: use approved assets as narrative anchors, establish a consistent type/color/spacing system, and replace generic panels with diagrams, rails, dossiers, and full-bleed media.

Delta: established one dark editorial field with signal-gold provenance; made the confrontation image carry the first viewport; gave the world, Luminai, conspiracy, chronology, and development pages different dominant diagrams inside one system; used approved identity masters as character anchors; replaced card mosaics with rails, ledgers, axes, and full-bleed bands.

Cycle 3 — interaction, accessibility, and integrity

Status: complete.

Goal: harden keyboard/mobile/no-JS behavior, reduced motion, contrast, live dashboard provenance, link integrity, and final cross-page continuity.

Delta: made mobile navigation progressive-enhancement safe; added Escape close and focus return; retained native disclosure semantics; added visible focus treatment, forced-colors support, reduced-motion behavior, 320 px reflow, descriptive links, one H1/main per page, and complete image alt coverage; made the weekly source link follow the live pointer instead of a dated URL; verified all local links/assets and the 27-task live render.

Final verification

  • Desktop: 1440 × 1000 key-page renders reviewed.
  • Mobile: 390 × 844 key-page renders reviewed.
  • Reflow: every page checked at 320 px; no horizontal overflow remains.
  • Keyboard: mobile menu opens, Escape closes, and focus returns to the trigger.
  • Live data: 27 completion tasks load from the current pointer, registry, and workflow state with no dashboard error.
  • Structure: every page has one h1, one main, a skip link, consistent primary navigation, and descriptive image alternatives.
  • Contrast: primary text/background pairs range from 6.17:1 to 17.47:1 under WCAG contrast calculation.
  • Motion: animation is opt-in under prefers-reduced-motion: no-preference; reduced-motion mode removes meaningful movement.
  • Code: JavaScript syntax, pointer parsing, local file links, local assets, and whitespace checks pass.