Use files and project knowledge with AI

Attach turn-specific sources, build a durable knowledge library, and tell the assistant what evidence to use.

Attachments and Knowledge serve different time scales

Files attached during project creation or chat provide context for that workflow. Project Knowledge is a durable library shared by the project. Use attachments for a current task and Knowledge for sources the team or assistant must revisit later.

Supported idea-start attachments include DOCX, PDF, TXT, and Markdown. A file is evidence, not an instruction to copy every sentence. Tell the assistant whether it should summarize, extract constraints, match a voice, or compare facts.

Make sources findable

Use descriptive filenames and separate unrelated subjects. The assistant receives a knowledge index and can list, search, inspect, and read relevant files on demand. This selective reading avoids injecting an entire library into every conversation.

A precise request names both source and use:

Read Harbor_Tide_Research.pdf and the current episode outline. List any scene whose tide timing is impossible. Do not edit yet.

Distinguish evidence from story rules

Knowledge stores source material. Worldview stores concise rules you have chosen for the fictional project. The assistant can read both, but it may write Worldview only when the latest message explicitly requests specific values. It cannot silently promote research into canon.

Verify high-impact claims

AI can misunderstand scans, tables, ambiguous terminology, or conflicting sources. Ask it to identify the file and relevant passage in its reasoning, then verify legal, medical, historical, financial, or safety-critical facts independently before production.

Keep the screenplay readable: reference source facts through visible action and dialogue rather than pasting research prose onto the page.