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.
Skill title
Objective
State the outcome this skill should reliably produce.
Required context
List the minimum vault files or facts the agent must read before acting. Do not tell the agent to scan the entire vault.
Workflow
- Start with the first required action.
- Describe the decision points that matter.
- Preserve uncertainty and story status where relevant.
- Verify the result before finishing.
Output standard
Define the expected artifact, location, structure, tone, or evidence requirements.
Guardrails
- State what the agent must not infer, change, expose, or publish.
- Keep vault authority and status rules intact.
- Defer to the author's explicit request and root
AGENTS.md.
References
Link only the optional references that this skill actually uses, and say when to read each one.