> ## Documentation Index
> Fetch the complete documentation index at: https://project-brain.rocheaiops.net/llms.txt
> Use this file to discover all available pages before exploring further.

# About PROJECT B.R.A.I.N.

> Project ownership, purpose, current maturity, and collaboration context.

PROJECT B.R.A.I.N. is created and maintained by **Scott Roche**.

It is a private, single-user cognitive architecture designed to keep durable
memory, document knowledge, provenance, and correction history under user
control rather than inside a model-provider session. This public documentation
explains the system’s boundaries, evidence, current capabilities, and limits
for collaborators, reviewers, and prospective infrastructure partners.

## Current maturity

The core text Learning Spine, Gemini Live integration, and document knowledge
capabilities are accepted. Phase 7 is in progress: its technical prerequisites
passed, and the required three-day genuine-use window is ready to begin. The
system is not yet operational.

## Principles

* B.R.A.I.N., not an AI provider, keeps the long-term record.
* Important information can show where it came from and why it is trusted.
* Corrections keep the old record as history instead of silently erasing it.
* The application is private, and its AI providers can be changed later.

## What makes B.R.A.I.N. different

Most AI tools are excellent at a particular part of the problem. Some remember
preferences so a chatbot feels more personal. Some keep chats, files, and
instructions together for a project. Some search across documents and work
apps to find an answer.

PROJECT B.R.A.I.N. is built to bring those useful ideas together while keeping
the long-term record under the owner's control.

| Familiar tool                                                                                   | What it is mainly built to do                                                     | What B.R.A.I.N. adds                                                                                                   |
| ----------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| [ChatGPT Memory and Projects](https://help.openai.com/en/articles/10169521-projects-in-chatgpt) | Help ChatGPT remember useful context and keep work together in a ChatGPT project. | Keeps the important record in a separate, portable system rather than inside one provider's workspace.                 |
| [Gemini memory and saved info](https://support.google.com/gemini/answer/16598469?hl=en-IN)      | Help Gemini personalize its answers using saved information and earlier chats.    | Uses Gemini for helpful reasoning and voice interaction, while B.R.A.I.N. decides what is kept as long-term knowledge. |
| [Notion AI Enterprise Search](https://www.notion.com/help/enterprise-search)                    | Find information across a workspace and connected tools, with citations.          | Keeps the original source, shows the citation, and also handles personal teachings and later corrections.              |

For example, if you tell B.R.A.I.N. that a preference is important, it can
remember that preference for a later conversation and show that you were the
source. If you later correct it, the new answer becomes current while the old
answer stays available as history. If an answer comes from a document instead,
the system can point back to that document instead of treating it as a personal
fact.

Gemini is useful inside this design, but it is not the owner of the system.
B.R.A.I.N. keeps the memory, documents, sources, and correction history. That
makes it easier to understand what the system knows, why it believes an answer,
and how it changed over time—even if the AI provider or server changes later.

## Contact and collaboration

For project or infrastructure inquiries, contact
[Scott Roche](mailto:scott@rocheaiops.net). Technical collaborators should read
the [current state](/getting-started/current-state), [security and privacy](/architecture/security-and-privacy),
and [validation overview](/validation/overview) before proposing changes.