Separate knowledge, worldview, and story structure

Store research and durable story rules in the right project-level systems without bloating the outline.

Three different jobs

• Outline describes episode-specific dramatic progression.
• Knowledge stores source material and reference documents the assistant can inspect.
• Worldview stores concise project-level key/value rules such as technology limits, political systems, or a central premise.

Keeping these roles separate reduces contradictions. A research PDF should not be pasted into the outline; a one-sentence world rule should not require reopening a forty-page file every time.

Build a useful knowledge library

Give files clear names and keep each source focused. The assistant first sees a knowledge index and can then list, search, inspect metadata, or read relevant bodies. It does not need every file injected into every turn. In a request, name the source or fact you expect it to consult.

Use worldview as durable constraints

Worldview is a flat set of fields. Official templates add only missing fields and never overwrite existing values. You can edit values in the interface; changes save after a short quiet period.

The AI treats worldview as read-only unless your latest message explicitly asks it to write specific values. “Keep this in mind” is not permission to change the project. A safe request is: “Set communication_delay to Messages take nine years between colonies in Worldview.” The assistant may set values, but it cannot delete keys or silently fill the template.

Promote facts deliberately

Research becomes a project rule only after you decide it should. A project rule becomes plot only when an episode outline or scene applies it. This flow keeps evidence, design decisions, and dramatic execution traceable.