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
Project Explorer
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
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.
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 premiseFinal-years control is established. Stopping authority, cumulative harm, privacy, and remedies still need concrete rules.
Test the leaders' safeguardsKonrad'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 resultSamuel 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 roleStory completion · Live from the vault
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 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 record9 / 27story tasks complete
Project explorer
Search or browse 539 documents across canon, development systems, story loops, prose tools, public work, and session history.
Visual World Compiler v2 stores each active generation as a local scene workspace so author feedback can change the smallest relevant layer without losing successful choices.
Disposable scene workspaces live under .visual-workspaces/, which is ignored by Git. Generated candidates remain outside the repository until the author explicitly approves one. Durable visual authority remains in skills/create-seeds-images/references/visual-registry.json and approved source images remain under skills/create-seeds-images/assets/approved-images/.
Natural language is the primary interface. A useful response names both what passed and what should change:
Keep Sylvan's identity, the beach light, and the clothing. Change the standing pose into a natural running stride, lower the camera, and make the blue Luminai tighter around his head and chest with fewer sparks.
The workspace converts this into:
Preserve locks apply to later revisions until the author changes them. A candidate reference controls only the categories the author preserved. It never becomes identity or canon authority by implication.
The clean renderer directive contains approved visible instructions only. Scores, failure labels, author-evaluation language, source traces, and promotion metadata remain outside renderer context.
Every image must be assigned one or more limited roles: identity, appearance, wardrobe, movement, environment, composition, or edit-source. Author-supplied scene references are scene-local by default. Registry identity masters remain authoritative for identity geometry.
Create and resolve a scene:
python3 skills/create-seeds-images/scripts/visual_scene_workspace.py create \
--scene-id sylvan-beach-running-v2 \
--request "Sylvan runs naturally along a public beach while his Luminai manifests in clear blue" \
--character sylvan-elaria \
--birth-year 1985 --age 40 \
--location surface-civilization \
--environment-overlay coastal-public-beach \
--manifestation luminai --manifestation-color blue \
--render-style cinematic-photorealism
Register a generated candidate without copying it into Git:
python3 skills/create-seeds-images/scripts/visual_scene_workspace.py add-candidate \
--scene-id sylvan-beach-running-v2 \
--image /absolute/path/to/candidate.png
Record conversational feedback and compile a revision:
python3 skills/create-seeds-images/scripts/visual_scene_workspace.py review \
--scene-id sylvan-beach-running-v2 \
--candidate-id candidate-001 \
--feedback "Keep the face and beach. Make the running stride natural and reduce the blue energy loops."
python3 skills/create-seeds-images/scripts/visual_scene_workspace.py revise \
--scene-id sylvan-beach-running-v2
Use explicit --keep or --change category options when natural-language interpretation needs correction. Re-running a review creates a new immutable review record rather than overwriting the earlier interpretation.
Feedback defaults to scene scope. scene-local, reusable-guidance, and approved-reference still have no story-canon effect. Proposed world definitions and canon decisions require a separate author decision and permanent-vault integration. Repetition alone never promotes a preference.