Projects & Provenance

Organize your work into projects, and see where every piece of knowledge came from.

8. Projects and Provenance: Organizing Your Knowledge

ENGRAM remembers not just what you know, but where it came from — its provenance — and lets you group related work into projects. Together these keep a growing knowledge base organized and traceable, no matter how many tools and conversations feed into it.

8.1 Where your knowledge comes from

Every article, document, and memory in ENGRAM remembers the activity that produced it. There are three kinds of sources:

• A conversation — a chat in ENGRAM, or an external chat (Claude Desktop, ChatGPT, and others) that you captured.
• A coding session — a Claude Code session you ingested from your terminal.
• A tool capture — when a connected agent saves a file or note directly through ENGRAM's tools, with no back-and-forth chat.

You'll see this as a Source line on an article or document, and as a source chip in the Memory Explorer. Provenance means you can always trace a piece of knowledge back to the work that created it.

8.2 Projects: one body of work

A project groups everything that belongs to one body of work — its conversations, coding sessions, captured research, and the articles and documents derived from them — no matter which tool produced them. A project is usually one repository or one topic you're researching.

Projects share a single namespace: a repo's coding sessions, the external chats you had about it, the articles you synced from it, and your in-app conversations can all live under the same project when they share a name. One project = one body of work.

Conversations you start in ENGRAM Chat without choosing a project land in your default project, named “ENGRAM KB” out of the box. (An administrator can change that default name in Administration → Settings → Projects.) Every project — including the default — is yours alone; the PRIVATE pill is a reminder that a project and its contents are visible only to you.

8.3 The Projects panel

Click the Projects icon (just left of the column title) on Chat, Knowledge Base, or Coding Sessions to open the Projects panel. It lists your projects, each tile showing a composite count — conversations · articles/documents · sessions — so you can see what's in it at a glance, when it was last active, a Default badge on your default project, and a PRIVATE pill. Search by name, or use + New to create a project — typing a name that already exists simply selects it.

8.4 Pinning an active project

Selecting a project pins it across Chat, Knowledge Base, and Coding Sessions at once, and the choice persists across reloads. The Project: <name> chip shows what's active; while a project is pinned, each area shows only that project's items, and new chat conversations file into it automatically. Click the × on the chip to return to All Projects — the no-filter view that shows everything, and the default when you first arrive.

8.5 Renaming and moving

Hover a project tile in the panel and click the pencil to give the project a friendly display name — this changes only how it's labeled, not what's in it.

To re-file something, open the actions menu (the ⋮ icon) on an in-app or external conversation, or on an agent-captured article, and choose Move to project, then pick a target (or create a new one). A few things move on their own, by design:

• Articles and documents derived from a conversation follow that conversation — move the conversation and they come along, so there's no separate “Move” on them.
• Coding sessions stay with their repository; regroup them by working with the project as a whole rather than moving sessions one at a time.

8.6 Projects across the app

• Chat — the conversation sidebar filters to the active project, and new chats file into it.
• Knowledge Base — the Library shows the active project's articles and documents.
• Coding Sessions — pick a project to see its sessions and insights dashboard, or choose All Projects to browse sessions across everything.

Because provenance is tracked and projects share one namespace, the knowledge you produce across many different tools converges into one organized, traceable knowledge base — and moving a conversation to a better-fitting project quietly brings its articles, documents, and memories along with it.