Konrad stands under Samuel's hidden red control while Sylvan observes from the clear opposing side.

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.

Open the workshop workspace Browse the project

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.

01 · Foundation

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

02 · Institutional gap

Control must protect people.

Final-years control is established. Stopping authority, cumulative harm, privacy, and remedies still need concrete rules.

Test the leaders' safeguards

03 · Causal result

Autonomy 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 result

04 · Two-planet endgame

George 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 role

Read Astra's integrated assessment Open Current Pickup Open the reader's atlas

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 record

9 / 27story tasks complete

Current checklist completion33%

33%

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

Current working fronts

Human–Luminai breakthrough
Evidence chain
Character agency

Open the full story roadmap

Project explorer

Browse the repository.

Search or browse 539 documents across canon, development systems, story loops, prose tools, public work, and session history.

3.3 KB Updated Sep 6, 2026 View source on GitHub

Document metadata

type: synthesis-config
status: active
version: 1.2
updated: 2026-08-24

Weekly Synthesis Configuration

Scheduled cycle

Author work days: Sunday through Thursday.
Synthesis: Thursday night after the day's work is captured.
Timezone: America/Los_Angeles.
Run date: the Thursday closing the work cycle.
Cutoff: record the exact Thursday-night timestamp in the run manifest.
Output use: an author-approved checklist governs the next Sunday–Thursday cycle.
After-cutoff material: hold for the next intake window; do not reopen the closed run by default.

Modes

Mode	Use	Core reports	Optional modules
Standard	normal weekly reset	all 10, concise	none by default
Deep	substantial capacity remains	all 10, expanded	choose 1–2
Exhaustive	deliberate end-of-cycle use	all 10, full	all 3 if evidence supports them

Retrieval scope

Always read START HERE.md, 03 Context/CURRENT.md, 03 Context/RULES.md, 03 Context/OPEN-QUESTIONS.md, 07 Coordination/CURRENT-PICKUP.md, 07 QA/Decisions.md, 07 QA/Contradictions.md, and the prior synthesis manifest if one exists.

Then inventory, without treating all as equal authority:

every signal in CURRENT-WEEK-INTAKE.md;
files changed since the last synthesis;
active Story Units, runs, and brainstorms;
implicated character/system/event notes;
TODO/QA changes;
journal/evidence registries;
public drafts only for extraction and spoiler review;
research only where it bears on a live mechanism.

For a first run, use a full-vault inventory but summarize sources before analysis. Do not dump raw files into every critic pass.

Authority order

latest explicit author decision;
recorded decisions;
current context;
status-labeled compiled story notes;
dated sessions;
advisory research and non-canon exploration.

A later date alone does not outrank an explicit decision. Report conflicts; do not flatten them.

Priority scoring

Score 1–5 for causal leverage, downstream blockage, character importance, evidence/setup urgency, and author-decision readiness. Subtract 1–5 for assumption cost. Use the score as a recommendation, not authority.

Queue classifications

BUILD NOW: sufficiently established/working and structurally ready for a Story Unit, sequence, scene specification, or approved vault task.
BRAINSTORM NEXT: important but blocked by an author decision, missing alternatives, research, or mechanism.
LEAVE OPEN: ambiguity currently creates value or the dependency is too remote to justify work.

These are analysis classifications, not parallel author TODO lists. Reconcile them into one proposed replacement completion checklist, deduplicated against the current task registry, and stop for author approval before changing the stable pointer.

Stop rules

Stop expanding a branch when it reaches a load-bearing author choice, source-authority conflict, missing mechanism that needs research, dedicated active brainstorm boundary, or unsupported canon proposal. Produce the exact next question instead.

Public boundary

Public-development ideas must label spoiler risk and source authority. Never expose private development, unresolved accusations as fact, raw transcripts, or real-person analogies.