# Use cases

Examples show how the same API fits different products. Named companies are examples unless stated
otherwise. Their source systems remain authoritative; Brain returns the records that apply, with
citations.

| Workload | Brain `self` | Records | Application authority | Returned records |
|---|---|---|---|---|
| **Brain Mac** | person | messages, events, documents, facts | explicit corrections | sourced personal recall |
| **Woof / BookWoof** | business | bookings, messages, policies, customer events | prices and policy Objects | front-desk action |
| **AiCMO / future GTM** | client organization | research, calls, campaigns, experiments | approved claims and offers | planning and review |
| **Pinnie Health** | person or care program | observations, documents, care-plan events | clinical system remains authoritative | sourced care history |
| **Highbeam-like finance** | business or account | transactions, statements, decisions | ledger/account system remains authoritative | reconciliation and explanation |
| **Conversational / video agent** | user, character, or account | turns, sessions, preferences, unresolved questions | product-owned profile fields | session history |

## What stays the same

Each product:

1. keeps raw input as a Record with provenance and time;
2. lets Brain derive versioned Memories;
3. uses Objects only for structure the application accepts;
4. requests task-specific Context and preserves its citations, gaps, conflicts, abstention,
   processing state, budget, and cost.

Brain complements the warehouse, source system, clinical system, or ledger. It does not replace
their authority.