Project Context Rules

• Most pages are project-scoped and show "select a project" when none is active.
• Assets, analysis outputs, department reads, and generation history are isolated per project.
• Switching projects changes source documents, queue visibility, and editor context everywhere.

Where Project Controls Live

• Dashboard: primary place to select/switch/rename/delete projects.
• New Project Modal: create a new workspace before writing or generating.
• Project Switcher Overlay: fast context changes without leaving current view.

Safe Switching Workflow

1. Finish or cancel in-flight tasks if you need clean handoff.
2. Switch project from Dashboard controls.
3. Confirm project name in top cards/headers before generating.
4. Open relevant page (Breakdowns/Storyboarding/Generators) and verify scene data belongs to that project.

When To Create a New Project

• Different screenplay/world with separate continuity requirements.
• You need separate asset lineage and queue history.
• You want isolated experimentation without affecting current production context.

Controls and Functions

Control	Function	Expected Result
Project cards/list rows	Select a project and make it the active workspace.	Navigation and project-gated pages update to the selected project.
New project	Creates a new workspace with its own documents, assets, tasks, and metadata.	The project appears in the switcher and becomes available for setup.
Rename	Changes the project display name while preserving project identity and storage.	Links and internal IDs remain stable.
Delete	Starts a confirmation path for removing a project.	Use only after verifying the project is no longer needed.
Permissions/share controls	Manage collaborators, studio roles, or project access where enabled.	Users see surfaces appropriate to their assigned role.
Status indicators	Show source-document, generation, or review state for quick triage.	Use these to decide which project needs attention first.