Project vs Knowledge Base vs attachment

Ampere gives Joule context in a few different ways. Use a project when the context belongs to a focused body of work, use the Knowledge Base when the source material should be reusable across the organization, and use an attachment when the file only needs to guide the current prompt or session.

The right choice depends on how long the context should last and who should be able to reuse it.

Quick choice

If you are not sure, ask: "Will I need this again later?" If yes, save it in a project or the Knowledge Base. If no, attach it to the prompt.

Use a project for focused work

Projects are reusable workspaces for related marketing work. A project can include a name, project brief, context summary, uploaded context files, generated files, project-specific chats, and reusable project assets.

Use a project when you want Joule to stay grounded in the same campaign, client, product, launch, or content program across more than one chat.

Good project context includes:

• A brief with the goal, audience, voice, brand guardrails, and key constraints.
• Source files that only belong to this project.
• Outputs and assets you want to keep with the same workstream.
• New chats that should start from the same project context.

Use the Knowledge Base for shared source material

The Knowledge Base is organization-scoped. Use it for material your team may want Joule to use across different projects, chats, and future requests.

The Knowledge Base supports uploaded files, nested folders, created documents, URL scrapes, website crawls, search, refresh, and compact browsing. It is a better home for durable material such as messaging notes, product details, research summaries, positioning documents, brand references, and public pages your team reuses.

Choose the Knowledge Base when the material should not be tied to one campaign or client. For example, a product positioning document your team keeps current belongs in the Knowledge Base; a temporary launch-outline file for one campaign usually belongs in that campaign's project.

Use an attachment for the current prompt

Attachments are best when the file is only needed right now. Add an attachment when you want Joule to look at a reference image, screenshot, or other prompt-specific material for the current request, but you do not need to save it as reusable context.

Attachments are useful for quick questions such as:

• "Use this image as reference for a launch post."
• "Review this screenshot and suggest clearer copy."
• "Turn this one source file into a draft for this session."

If the same material will guide future work, move it into a project or the Knowledge Base instead of repeatedly attaching it.

How to decide

Use this order when you are preparing context:

1. Start with a project when the work has a clear campaign, client, product, launch, or content program.
2. Add Knowledge Base material when the same source should help more than one project or team member.
3. Attach a file when the current prompt needs a reference that is not worth saving for reuse.

You can use more than one at the same time. For example, a launch campaign can live in a project, use shared company positioning from the Knowledge Base, and include a one-off screenshot attachment for a single prompt.

Keep context clean

Good context helps Joule stay focused. Before adding source material, check whether it is current, relevant, and allowed for your team to use.

Avoid saving every temporary note as reusable context. Keep project briefs concise, remove stale files when they stop being useful, and use attachments for one-off references. Clean context makes future prompts easier to write and easier for Joule to follow.