The knowledge layer for Salesforce
See how your org connects, let the documentation agent write it up, and give your team and AI tools context they can check.
Nothing to install in Salesforce. Graph reads your org’s setup (its metadata), not your customer records.
Intake · Page 01
Case file 0417
Open
Nobody is sure what still uses it.
Page 02 · The evidence board
Four strings lead away from Renewal Date.
Graph found four places that use the field: the reminder email, the renewals dashboard, the automation that reminds account managers and the pricing rule.
email/Renewals/Renewal_Reminder.email · line 6
Go to chapter 02Page 03 · The source
Every string ends at a file and a line.
Before anyone replaces the field, they can read exactly where each of the four uses it.
flows/Create_Renewal_Task.flow-meta.xml · line 33
Go to chapter 03Page 04 · The report
The renewals page went out of date.
The automation changed. The documentation agent suggested one edit, and a person accepts or rejects it.
docs/sales/renewals.md · “30 days” → “45 days”
Go to chapter 04Page 05 · The briefing
AI assistants read the same evidence.
Through MCP, the standard way AI tools connect to your data, and only within the access you grant.
find_metadata_usages { "name": "Renewal_Date__c" }
Go to chapter 05Page 06 · What it can’t prove
Some strings stay dashed.
A field name assembled while code runs can’t be resolved, so it is flagged for a person to check.
RenewalPricing · line 48
Go to chapter 06Page 07 · Your case
Bring us the case your org can’t close.
Tell us about the question your team keeps reopening.
Go to chapter 07File closed, 7 pages
Chapter 02The evidence board · of 07
Graph maps how your org’s setup (its metadata) fits together. Each string on this board is a reference Graph found, and each one ends at a file and a line you can read.
Board · Renewal DateExhibit 1 of 44 references found
Subject
Renewal Date
Opportunity.
On a wide screen, use the arrow keys to move this exhibit, Shift for bigger steps, and Enter to pin it.
Exhibit 1email/
<p>Your renewal is due on {!relatedTo.Renewal_Date__c}.</p>
Exhibit 1 of 4
The email prints the renewal date. Change the field and customers could get a blank date.
Renewal_
Exhibit 2 of 4
The report groups deals by renewal date. Change the field and the dashboard goes empty.
Renewals_
Exhibit 3 of 4
It creates a follow-up task 30 days before the renewal date. Change the field and the tasks stop.
Create_
A Flow is a Salesforce automation.
Read the source for exhibit 3Exhibit 4 of 4
Code checks the date before applying the early-renewal discount. Change the field and the discount logic needs review.
RenewalPricing · Apex class · classes/
An Apex class is a piece of Salesforce code.
Read the source for exhibit 4Chapter 03The source · of 07
Graph keeps the file and line behind each reference it finds. Before anyone replaces Renewal Date, they can read exactly where each of the four uses it.
Evidence sheet · Exhibit 1 of 4
Indexed
6<p>The email prints the renewal date. Change the field and customers could get a blank date.
Chapter 04The report · of 07
When the automation that reminds account managers changed, the page that explains renewals went out of date. The agent proposed one edit. You decide whether it goes in.
docs/sales/renewals.mdKept in Git
Stale
Create_Renewal_Task · FlowRenewal_Date__c · Field
When a deal is close to renewal, Salesforce reminds the people who need to act.
Account managers get a follow-up task 30 days 45 days before the renewal date.
Customers get a reminder email that shows their renewal date.
Link the Salesforce parts a page is about and pick a template. The agent drafts explanations and diagrams from what it can read, in your team’s style.
Its edits arrive as tracked changes you accept or reject. Change requests carry them through review with your team.
A page is flagged stale when the Salesforce setup it describes changes. Ask the agent to refresh it, then review the draft.
Pages live in Git, the version history your developers already use, so every change to a write-up is reviewed and recorded.
Generation and refresh depend on your connected sources, metadata availability and workspace settings. Review drafts before you share them.
How the documentation agent worksChapter 05The briefing · of 07
AI assistants can read the same evidence through MCP, the standard way AI tools connect to your data. They see only what you authorize, and each answer cites the file and line it rests on, so a person can check it.
Briefing transcript · MCP
Found 4 references, the same four on the board
Matches come from synced source. Verify before you change anything.
Same drawer · separate folder
Your team’s docs in GitHub or GitLab, Confluence imports and captured processes sit in the workspace beside the graph. No string is drawn from them to your Salesforce setup.
Chapter 06What it can’t prove · of 07
Graph shows your org’s setup as of the last sync, not every live change. Sync runs on your schedule or on demand, so check when it last ran before you plan a change.
Some references can’t be pinned down. At line 48 of RenewalPricing, the code assembles a field name while it runs, so Graph draws that string dashed and you know to look.
Graph doesn’t watch Salesforce while it runs, and it can’t read setup your connection has no access to.
Note for the file
A missing connection does not prove that a component is unused or safe to delete.
Chapter 07Your case · of 07
Case file 0417 · Renewal Date
4 references, each with a file and a line. One dashed string noted for a person to check.
Open
Tell us about the question your team keeps reopening. The button opens an email to the people who build LivingContext.
Or write to hello@livingcontext.ai
The ones we hear most often, answered plainly.
No. Search for a field, flow, report, email template or another component. Explore where it is used and what it depends on in a visual map or a connection list. Technical source details are available when you want to check the evidence.
A place to understand your Salesforce beyond a list of components. LivingContext combines synced metadata, a dependency graph and your team’s documentation so people and AI tools can explore the org with source-backed context. The Graph connects Salesforce metadata; it does not turn every connected document or system into a graph node.
Yes. The documentation agent helps draft pages from linked Salesforce metadata and templates, explain and rewrite existing docs, and refresh pages when tagged metadata changes. Proposed editor changes are reviewable suggestions you can accept or reject. Templates and your team’s style guide shape the output; connected sources and workspace settings determine what is available.
No. Graph analyzes the accessible metadata included in your synced index. Coverage varies by component and type; dynamic references, inaccessible metadata and incomplete syncs can leave gaps. The explorer exposes coverage and unresolved references. A missing link is not proof that something is unused or safe to delete.
Graph reflects the saved metadata snapshot, not every live Salesforce change in real time. Sync runs on your configured schedule or on demand. Check the index status and coverage before relying on a result for a change review.