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.
Open Questions Ranked
| Rank | Question | Causal leverage | Downstream blockage | Character/evidence value | Readiness | Assumption cost | Recommended route |
|---|---|---|---|---|---|---|---|
| 1 | What is SC-010's next major setup category? | 5 | 5 | 5 | 5 | 1 | current one-question author gate |
| 2 | What exact event activates Samuel's negotiated first-primary status? | 5 | 5 | 5 | 3 | 3 | hierarchy brainstorm Question 4 |
| 3 | What does Konrad personally reactivate or transfer? | 5 | 5 | 5 | 3 | 3 | containment truth table after lock direction |
| 4 | Which powers are automatic, manipulated, resisted, audited, or resettable? | 5 | 5 | 4 | 2 | 4 | systems deepening after Questions 2-3 |
| 5 | What is the first observable anomaly proving a second decision-maker? | 5 | 4 | 5 | 3 | 2 | S-015 development packet |
| 6 | Which proof family leads the final reversal? | 4 | 4 | 5 | 2 | 3 | Creative Possibilities author review |
| 7 | What concrete but flawed command theory does Samuel believe? | 4 | 4 | 4 | 3 | 3 | bounded antagonist-model brainstorm |
| 8 | What exactly destroys the startup and what does Sylvan lose? | 4 | 4 | 5 | 3 | 2 | S-002/S-004 structure pass |
| 9 | Which scenes carry the three-environment progression? | 4 | 4 | 5 | 2 | 3 | S-005 sequence work |
| 10 | Which parent carries the Witness role and how does evidence reach Sylvan? | 3 | 4 | 5 | 2 | 3 | family/evidence author gate |
Ask this week
Ask only SC-010 Question 5. It is already the protected workflow boundary.
Research before asking
No additional broad research is justified. Use targeted research only after a selected system or evidence question cannot be answered from the vault.
Preserve as useful ambiguity
Narrated chronology, exact viewpoint distribution, some descendant identities, final venue, and whether one or several public events carry the collapse should remain open until the causal and evidence chains are stronger.
Repeated unresolved signals
Lock event, permissions, reactivation, surveillance limits, evidence custody, chronology anchors, startup loss, and endgame cost recur across current context, QA, Story Map, and the handoff.