Glossary

Term	Plain-English meaning	Example
Agent	A coding assistant that can call tools while helping you work.	Claude Code, Codex, or Cursor.
MCP	The connection format that lets an agent use Lore's tools.	The agent calls search to ask Lore a question.
Repository	A project's files and change history on GitHub.	acme/payments.
Organization	The team whose membership, plan, and shared memory you are using.	Your company's Lore workspace.
GitHub App installation	The permission that lets Lore process selected GitHub repositories.	Installing Lore on two repositories in an organization.
OAuth	Browser-based sign-in and approval for a client connection.	Signing in when your agent first connects to Lore.
SSO	Your organization's additional company sign-in requirement.	Signing in through your employer's identity provider.
Fact	One piece of knowledge saved in Lore.	“Payment retries reuse the original request ID.”
Claim	The text of a fact.	The sentence explaining the retry rule.
Evidence	Information showing where a fact came from.	A GitHub comment, document, or source-file location.
Scope	The part of the repository where a fact applies.	src/payments.
Repository-relative path	A file path starting inside the project, without your computer's folders.	src/payments/retry.ts.
Ingestion or scan	Reading a connected repository and extracting useful memory.	The first scan after installation.
Cleanup PR	A proposed GitHub change that you can review before merging.	Removing an eligible duplicate note from code.
Retired fact	A fact hidden from normal retrieval whose history remains.	An old rule removed after a redesign.
Embedding	A numeric representation used to find related meaning in text.	Matching a search about authentication to a fact about sessions.
Read quota	The shared monthly allowance for search and get_context calls.	One million reads for a Team organization.