For one person, a few friends, or a whole company.
Knowledge goes missing in the same few ways whoever you are: it lives in one head, it goes out of date, or it is in five places at once. Pick who you are, and each case says what happens without Lore, what Lore does instead, and why that matters.
The cases
Who
Field
15 cases
Just meFreelancing
Every client's way of doing things, in one place
A self-employed consultant with a dozen clients · Monday morning, switching from one client to the next
Without Lore
Each client has its own rules: who approves invoices, the tone they like, what was agreed on the last call. It lives in old emails and in your head, and you ask a chatbot that knows none of it.
With Lore
Each client's decisions and rules are entries you wrote once, with the date you last checked them. Ask answers from them, with a model on your own computer or one you choose, or hands the question and those entries to your own ChatGPT or Claude.
Why it matters · TimeYou stop re-reading old threads before every call, and nothing about your clients leaves your computer unless you send it.
Just meA solo project
The project only you remember
One developer with several assistants · Claude Code in the morning, Cursor in the afternoon
Without Lore
Every assistant keeps its own notes, or none. What you explained to one, you explain again to the next.
With Lore
Lore Local is one app on your computer that every assistant shares. What an assistant learns, it proposes back for you to approve.
Why it matters · SimplicityOne memory for all your assistants, kept on your own computer.
Just meA few peopleWriting
A world's rules, kept straight
A writer building a world across several books · Drafting chapter twelve with an assistant's help
Without Lore
Who knows what, which city burned in which year, what magic can't do. The assistant helping you draft has read none of it and contradicts book one on page three.
With Lore
The world's facts, rules and decisions are entries, linked to each other, a contradiction flagged as one. The assistant asks Lore before it writes, and cites the entry it followed.
Why it matters · ConsistencyCanon stays canon, and you check the assistant's work against a source instead of your memory.
A few peopleA game
The game everyone remembers differently
Four friends making a game in their spare time · Evenings and weekends, each with an assistant writing code
Without Lore
One of you decided enemies never respawn; another's assistant just added respawning. The design lives in a chat, half of it from before you changed engines.
With Lore
Design decisions, the engine's conventions and the world's lore are entries with an owner. Each friend's assistant reads the ones its task touches, and what it proposes waits for the owner's yes.
Why it matters · AlignmentFewer evenings undoing each other's work, and a newcomer who joins in month six can read why things are the way they are.
A few peopleA small businessA channel
How the channel does things
A small team running a video channel · A new editor's first week, and every sponsor deal
Without Lore
The intro's length, the sponsor rules, which topics were covered and how the thumbnails are made: all in the founder's head and a few old messages.
With Lore
Each is an entry with its owner. Ask answers the new editor in the app or in Slack, citing the entry, and what nobody could answer goes to the person who can.
Why it matters · OnboardingThe founder answers each question once, and every video follows the same rules.
A few peopleAn app
Decisions made at midnight, explained at noon
Three people building an app on the side · One codes at night, another reviews at lunch
Without Lore
Why the login works that way, which payment provider you chose and why: the reasons stay with whoever was awake.
With Lore
Each decision is an entry, approved before it counts, linked to what it depends on; every assistant reads the ones its task needs and cites them in its answer.
Why it matters · AlignmentThree people and their assistants work from the same decisions, without a meeting to sync them.
A small businessAn advisory office
The procedure only one colleague knows
A small tax and accounting office · Filing season, and every time a rule changes
Without Lore
How each form is filed, the exceptions for certain clients, last year's rule change: written in a document that may be out of date, or known by the one person who is on holiday.
With Lore
Each procedure is an entry with an owner, verified on a date, and marked as needing a re-check when it gets old. Colleagues ask Lore in the app and get the approved answer with its source. It runs on the office's own computer or server.
Why it matters · RiskNobody follows last year's procedure by mistake, and the office's knowledge stays inside the office.
A small businessA growing companyCustomer support
The question everyone answers differently
A support team · The same question, the tenth time this week
Without Lore
Each agent answers from memory or an old document. Customers get three versions of the refund rule, and nobody notices which questions have no answer at all.
With Lore
Ask answers in the app or in Slack from approved entries only, each cited. A question nothing answers goes, grouped with others like it, to someone who can answer, and the answer comes back to whoever asked.
Why it matters · ConsistencyOne approved answer, with its owner, instead of three remembered ones; and a list of what the team still has to write down.
A small businessAn agency
Each client's brand, without the guesswork
A design or marketing agency · A freelancer joins a client's account for a month
Without Lore
Colours, words to avoid, what the client rejected last time: scattered over decks and inboxes, learned again by every new person on the account.
With Lore
Each client is an area with its own entries and its own access, so a freelancer reads only the clients they work on, and the client's owner approves what changes.
Why it matters · AccessA newcomer is useful on day one, and one client's material never shows up in another's work.
A growing companyA large organisationEngineering
The assistant that re-decides what the team decided
A developer working with Claude Code, Codex or Cursor · Every task, all day
Without Lore
Each session starts from nothing. The assistant searches the repository, reads files, guesses at conventions, and spends tokens finding what a colleague would have said in one line.
With Lore
Lore answers the task first: the brief brings the decisions and rules that apply, cited. In Claude Code the hook says nothing on prompts that don't need it.
Why it matters · Quality and costMeasured: 24/24 right answers for Claude with Lore, against 16/24 from the same knowledge as a docs folder, and −36% tokens per run.
A growing companyEngineering
The new developer who doesn't know why
A developer in their first week · Their first ticket, with an assistant beside them
Without Lore
The assistant reads the code and suggests the obvious change, the one the team ruled out last year for a reason nobody wrote down. Three days in, a senior colleague explains it in review.
With Lore
The decision is an entry with its owner. Before the assistant opens a file, Lore hands it the few entries the task touches, so the first suggestion already respects it and cites where that came from. The project page says who to ask.
Why it matters · SpeedWeeks of learning the unwritten rules become a first day of reading them, and the people who know are asked less often.
A growing companyA large organisationOperations
The incident nobody remembers fixing
The engineer on call · An alert at two in the morning
Without Lore
It happened before. The fix is in a chat thread from March, or in the head of someone asleep. The runbook in the wiki describes a setup that changed twice since.
With Lore
The incident is an entry linked to what fixed it, and the runbook says whether it was verified, by whom and when, or that it needs a re-check because the code it rests on moved.
Why it matters · RiskA stale runbook is marked as stale before anyone trusts it at the worst moment.
A small businessA growing companyA large organisationAny team
The expert who is about to leave
A team lead · The person who knows the billing system hands in their notice
Without Lore
A frantic month of handover documents nobody reads, written into a wiki with no owner, going quietly out of date the week after.
With Lore
Their knowledge becomes entries with a new owner each, reviewed before they count. Freshness keeps asking whether they still hold; links show what depends on what.
Why it matters · ContinuityWhat one person knew stays true after they go, with someone named who vouches for it.
A small businessA growing companyA large organisationRegulated work
Everything kept in-house
An organisation that cannot send its knowledge out · Security asks where the data goes
Without Lore
Either no AI help with the organisation's own knowledge, or a hosted tool that indexes everything somewhere else.
With Lore
Lore runs on your servers or one computer. Search runs on its own local models. Ask can answer with a model on your own machine, and access per area holds for every assistant.
Why it matters · PrivacyMeasured: a small open model (Qwen3 8B on a GTX 1070 Ti) answered 0 of 14 questions about the project alone, and 14 of 14 through Lore's Ask.
A large organisationMany departments
Many teams, many places to look
An organisation with many teams · Knowledge spread over departments and tools
Without Lore
Each team searches its own wiki, Slack and tickets, and nobody can see across them without copying everything into one place.
With Lore
Connectors mirror Slack, Jira, Confluence, Google Drive, Notion and Linear read-only, under each source's access. Several Lores can be searched as one, each answer marked with where it came from, nothing copied.
Why it matters · ScaleOne search across what a person may see, without one giant store everyone can read.
No case for that pair yet.
Why it holds in every case
Four things the cases have in common.
Someone vouches for it
Every entry has an owner and is approved before it counts, so what an assistant repeats is what a person stands behind.
It says how fresh it is
Verified, needs a re-check, or unverified, with the reason, so an old answer is marked before it misleads.
It arrives before the search
Assistants get the few entries that matter at the start of a task, within a budget, or nothing at all; people ask in the app or in Slack.
It stays where you put it
On your computer or your organisation's server, read under each area's access, by people and assistants alike.
When you don't need it
Where Lore is the wrong tool.
Lore pays back when knowledge has owners, goes stale, lives in several places, or is needed by more than one person or assistant. These cases are better served by something else, and saying so is part of the point.
A short project with a good README
If everything you and your assistants need fits in one file that stays true, and nobody else works on it, a README or an instructions file does the job.
Numbers that change every hour
Prices, stock, metrics and live status belong in a database or a dashboard. Lore is for what stays true for weeks: decisions, rules, how things are done.
Passwords, keys and secrets
Use a password manager or a secrets vault. Lore is built for knowledge many people and assistants read, the opposite of a secret.
Documents read whole
A contract, a manual or a novel you need to read from start to end is a file. Lore hands over the passages that answer a question, not whole documents.
What any assistant already knows
How a language works, what a library's function does, general facts: your assistant knows these. Lore is for what only your team knows.
Notes nobody will ever look after
Lore works because someone owns and approves each entry. If no one will, it becomes one more folder that goes stale; a shared document is cheaper.
