A scope, not a folder
Documents, attachments, and the crystals distilled from them form the project's world. The interface says it plainly: the AI answers only from these.
PROJECTS · LIVE
Draw the boundary. AI stays inside.
Bind files and conversations into a project, and the AI answers only from what's inside — no bleed, no guessing, no contamination between workstreams.
HOW IT WORKS
Context with walls.
Boundary that holds under orchestration
Multi-step tasks snapshot the project boundary at launch. A long-running job cannot wander out mid-run.
Parallel without contamination
Client A's strategy never leaks into client B's draft. Each project is its own sealed context.
FAQ
QUESTIONS, ANSWERED
01Can a file belong to multiple projects?
A project binds the sources you select; you can include the same vault file wherever that source is relevant.
02Do chats inherit project scope?
Yes. Attach a conversation to a project and it answers within that project's selected sources.
03Can orchestrated tasks cross projects?
No. The project boundary is snapshotted when the task launches.
Keep parallel work parallel, even when the tasks run long.
Choose the world the AI may see.
