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.
Private idea workspace
Purpose
The private idea workspace captures and manages multiple product ideas.
Its job is to help the owner:
- Capture ideas quickly.
- Understand what each idea is.
- See the current stage of every idea.
- Record the next action.
- Keep notes and observations.
- Pause, archive, or continue ideas.
- Later test optional tools inside individual ideas.
It is not an AI idea generator, startup operating system, project-management platform, market-research tool, public directory, or validation framework.
Core model
The existing experiments table is the idea record. Internal code may still use the word experiment where renaming would add risk. The private admin UI uses idea, Ideas dashboard, and Idea workspace.
Primary private surface after admin login:
- Ideas dashboard:
/devsite/iainreiddotdev/admin/experiments.php - Idea workspace:
/devsite/iainreiddotdev/admin/experiment.php?id=…
The public /devsite/iainreiddotdev/saas-lab/ page is the VibeKB portfolio showcase, not the management interface.
Idea lifecycle (status)
Status answers: Where is this idea in its lifecycle?
| Status | Meaning |
|---|---|
inbox | Freshly captured |
exploring | Clarifying the idea |
validating | Checking the problem/user fit |
building | Building a usable loop |
testing | Testing with real use |
launched | Live / shipping |
paused | Held, still active (not archived) |
archived | Retired; kept for history |
Legacy statuses from the first visibility phase are remapped on schema init:
framing→inboxself-testing→testinginvite-testing→testingpublic→launched
building and archived keep their values.
Visibility
Visibility answers: Who is allowed to access a gated experiment page?
private— administrators onlyinvite— administrators plus invited registered userspublic— anyone
Status and visibility are independent. Authorization is derived only from visibility (plus admin/invite). Never from status. Archiving does not delete records and does not by itself change who can access a gated route.
Priorities
Application-validated priorities: low, normal, high.
New ideas default to status = inbox, priority = normal, visibility = private.
Codes and slugs
- Idea codes are generated as
IDEA-001,IDEA-002, … by inspecting existing
IDEA-NNN codes (not row count). Legacy codes are left unchanged.
- Slugs are generated from the idea name (ASCII-safe, unique with
-2,-3, …).
Slug editing remains under Access and deployment in the workspace.
Future tool rule
A future tool earns its place only when it:
- Runs inside a specific idea,
- Saves a useful result, and
- Helps decide or perform the next action.
Intentionally deferred
AI integrations, competitor/market research, idea scoring, kanban/tasks, notifications, email, billing, teams, uploads, charts, and external APIs are out of scope for this phase.
Related docs
- Authentication:
docs/AUTH.md - Visibility gates:
docs/EXPERIMENT_VISIBILITY.md - Deployment:
docs/DEPLOYMENT.md