The context layer
How source evidence becomes maintained Pages, organised into trees and linked back through citations.
The context layer
A context holds a shared, maintained account of a company or subject. It combines source evidence with Pages that explain what the evidence means and where to look for detail.
For example, a customer renewal may appear in a meeting note, a CRM record and an email. Pensieve brings those sources together in a customer Page that explains the relationship and cites the evidence behind its claims.
Sources
A source, called Data in the agent tools, is the material behind the account: a connected document, uploaded file, saved conversation or knowledge an agent has saved. Depending on the source, Pensieve retains its content, distils durable facts with supporting excerpts, or builds a separate tree describing a codebase or database.
Sources answer exact questions: what was written, which date was agreed, or what a table contains. Connectors explains how each source is read; Uploading and managing sources covers files you add directly.
Pages
A Page explains one subject: a customer, project, person, process or decision. It draws together relevant evidence instead of making the reader reconstruct the subject from every underlying document.
The customer Page might explain the current renewal position, who owns it and which conditions remain unsettled. As new evidence arrives, Pensieve updates the account. A Page also routes the reader to the sources that hold the details.
You can edit Pages and organise the tree. An edit changes the curated account; saving new source evidence gives Pensieve material that other Pages can also cite.
Citations
A citation links a Page's claim to its supporting source. Open it to inspect the passage behind a date, statement or decision. In the renewal example, the Page gives you the relationship's context; the cited note or email gives you the exact terms.
When a claim needs checking, follow its citation. When evidence is missing or contradictory, the useful answer is to identify that gap, rather than fill it with an assumption.
The tree
Pages are organised from broad subjects to their parts. The root overview introduces the context; branches might cover Sales, Product and Operations, with customer or project Pages below them. Links connect related subjects across branches.
The company map is not necessarily the only tree. GitHub codebases and connected databases have their own trees describing how those systems are structured. Your AI can list the available trees and choose the relevant one.
Read a relevant Page for understanding. Search for a specific question and open the matching Page or source passage. Use the tree outline when you want to understand how the map is organised.
How it stays up to date explains how Pensieve maintains this account as sources change.
Up next
With your tools