Glossary
Short, factual definitions for terms used across sf-intelligence docs. Each entry is written to be citable by search engines and AI assistants.
MCP server (Model Context Protocol)
A standardized way for AI assistants (Claude, Cursor, Codex) to call external tools. A Salesforce MCP server exposes org-aware capabilities - schema lookup, dependency analysis, permission tracing - that the model invokes during conversation. sf-intelligence is a read-only Salesforce MCP server focused on org understanding, not DevOps. See the MCP overview.
Metadata vault (org-kb/)
The local directory created by sfi refresh. Contains Markdown-rendered component docs, a DuckDB dependency graph, manifest files, and optional overlays (annotations, git history). All offline answers are served from here - no network calls during conversation.
Refresh
A read-only metadata pull via sf project retrieve followed by local indexing. Re-run after org changes to keep answers current. Large orgs can use sfi refresh --staged for a servable vault in minutes. See staged refresh.
Intelligence planes
Offline - answers from the vault (default). Live - opt-in, read-only SOQL for record counts and samples. Hybrid - fuses vault structure with live magnitude, disclosing both provenances.
Provenance
Where an answer's data came from: offline_snapshot, live_org, hybrid, or annotation (human-curated overlay). Every sf-intelligence answer carries a provenance stamp.
Confidence tier
How a dependency or finding was derived: declared (Salesforce metadata), parsed (AST/XML analysis), or heuristic (regex - verify before acting).
Completeness
Whether all needed metadata families were retrieved: complete, partial (some types pending or not checked), or unknown.
Impact analysis / blast radius
Tracing components that depend on a field, object, Flow, or Apex class before you change or delete it. Core use case - see impact analysis.
Static analysis
Analysis of retrieved source and metadata without running code. Dynamic SOQL and reflective Apex are invisible. "No references" means no static evidence, not "unused."
Canonical component ID
A stable identifier like CustomField:Account.Industry__c or ApexClass:PaymentProcessor. Every component sf-intelligence names is cited with one.
Intent router
The deterministic layer that maps plain-language questions to the right tools and intelligence plane. Logs unrouted questions locally for product improvement.
Org card
A compact JSON summary of org scale and coverage rendered at every refresh. Served via sfi.org_card for fast orientation.
Annotations overlay
Human- or AI-proposed metadata stored in meta/annotations.jsonl - owner, status, glossary synonyms - that survives refreshes. See configuration.
Read-only guarantee
sf-intelligence has no write, deploy, or delete path to Salesforce. Only metadata retrieve touches the org. See FAQ and trust.