Skip to navigation

Use cases

Where a brain fits, with worked examples you can copy.

Use this page to find where a brain fits in your work. Connect one to the AI tools you already use, or build it into your own product.

Worked examples

Start with the one closest to what you’re building.

Examples by team

These are starting points for your own brain.

  • Capture architecture decisions and ask why a service works the way it does.
  • Capture merged pull requests from CI, so review decisions reach the next coding session.
  • Import postmortems and search them before changing the system involved.
  • Keep runbooks in a brain and flag the pages nobody has touched in months.
  • Group tickets and interviews by customer problem, however each customer words it.
  • Bring back earlier research when a roadmap item is reopened.
  • Keep the reason a feature was cut next to the decision to cut it.
  • Get a weekly list of every page that changed since the last review.
  • Draft replies from approved pages and cite each one.
  • Send questions with no supporting page to a person, with the reason attached.
  • Turn a person’s answer into a page, so the next similar question has a source.
  • Review contested pages when a release note and a ticket disagree.
  • Keep calls, emails and implementation notes on one account’s pages.
  • Ask what changed on an account since the last meeting.
  • Plan with every constraint in view, including the data-residency rule from an old call.
  • Hand an account to a new owner along with its history and sources.
  • Capture papers and links, and let the brain group them into topic pages.
  • See which findings connect across papers that use different words.
  • Use daily briefs to bring back threads you haven’t opened in a while.
  • Compare what two sources say about the same claim.
  • Answer a new hire’s questions from team decisions, with sources.
  • Show how a process changed by reading a page’s earlier versions.
  • Send stale pages to their owners on a schedule.
  • Keep meeting notes searchable by what was decided.
  • Keep plans, updates and open risks in one brain and ask for next steps from any AI tool.
  • Prepare for a meeting from the notes behind each decision.
  • See where the written record disagrees with itself.
  • Send each chat turn through the classifier. The brain keeps preferences and decisions and drops small talk.
  • Load the prompt index at the start of a session, then search when a question needs more.
  • Give each end user their own brain by using one subject per user.

What each job needs

Most use cases combine a few of these jobs.

JobUseReach for it when
Find an answersearchPages, then getPageA question needs something specific
Load general contextindexAn agent starts a session
Remember somethingcaptureA decision, note or document should last
Import historycaptureBatchYou have existing documents to bring in
Explain a changepageVersionsThe question is about why or when
Surface disagreementcontested status and resolveNew material contradicts a page
Keep other systems in stepWebhooks and the change feedA tracker or an app mirrors page state
Tell people what changedDaily briefs and SlackA team reviews on a schedule
Work inside AI toolsMCP and the CLIPeople or agents already work in those tools

When to use something else

Use your database for exact records such as balances and order status. Use your analytics tool for counts and rates. Link to the original document when the wording has legal or financial weight, because a page summarises what its sources say.

How to build with Living Brain covers the write and read paths these examples share.