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
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.
Control must protect people.
Final-years control is established. Stopping authority, cumulative harm, privacy, and remedies still need concrete rules.
Test the leaders' safeguardsAutonomy 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 resultGeorge 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 roleStory 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 record9 / 27story tasks complete
Current checklist completion33%
- Current sweep
- Macro Shape
- Current task
- SC-010
- 01 Macro
- 02 Causal
- 03 Agency
- 04 Systems + evidence
- 05 Sequence
- 06 Scene map
- 07 Scene development
- 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.
Story website projections
The public atlas sources are reviewed Markdown in 05 Public/Atlas/. Canon remains in 02 Story/; each public page links the notes from which its copy was selected. Canonical changes still require editorial review before changing public copy. The builder prevents drift between a reviewed source and its generated views; it does not decide canon.
The workshop source of truth is 07 Coordination/Story Completion Workflow/Workshop/. Each module is Markdown with explicit status, one author gate, prerequisites, alternatives, tests, and a decision template.
Run from the repository root:
python3 scripts/build_story_sites.py
python3 scripts/check_story_sites.py
git diff --checkPython's standard library is sufficient. Commit generated output with the sources so both GitHub Pages and shared PHP hosting need no build service or package manager. Do not hand-edit generated pages, JSON, workflow snapshots, or workshop downloads.
The builder creates eight atlas pages, the workshop page, shared JSON for the Explorer, Markdown downloads, and local snapshots of existing workflow pointers and their targets. docs/todo.html, ideas.html, and visuals.html retain their original interactions; their scripts now read the bundled workflow snapshot. Changes to pointer targets need a rebuild.
The Explorer keeps the existing PHP Markdown browser, search, request allowlist, and portfolio styling. Its new workbench reads the same generated JSON as the atlas. Both must be deployed from the same repository revision.
Browser verification
Playwright and a Chromium executable are development-only test prerequisites; they are not website dependencies. Start PHP 8.2 at the repository root, then run:
php -S 127.0.0.1:8766 -t .In another terminal:
node scripts/test_story_browser.cjsOptional variables: SEEDS_TEST_URL, SEEDS_TEST_OUTPUT, and SEEDS_CHROMIUM for a compatible custom executable. Screenshots and results default to a temporary folder outside the repository. Never commit test draft answers.
Draft persistence
The browser editor saves only to that origin's local storage, with an in-page fallback when storage fails. It provides Markdown export and import. It does not write to the vault, synchronize devices, invoke AI, or approve decisions. The author must review and accept an exported answer before integrating it through the existing workflow.
Deployment layout
GitHub Pages serves docs/. Shared hosting uses .cpanel.yml to archive the full committed repository under the existing deployment root. Do not upload only project-explorer/: it needs the portfolio includes, vault Markdown, and docs/assets/story-*.json plus docs/workshop.js and styles.