Brain · The Brain Platform
Consult approved company documents through compatible AI clients, inspect source evidence and keep the original owners responsible for the guidance.
What is the approved refund-review process for an annual plan?
The fictional support reference says an annual-plan refund request goes to the billing reviewer with the account context and original invoice reference. It describes a routing process, not an automatic refund entitlement. Open the source and involve the responsible reviewer before acting. This example contains no real customer or payment details.
Source excerpt · Annual-plan support referenceRoute annual-plan refund requests to the billing reviewer with account context and the original invoice reference.
An AI knowledge base organizes information so an AI tool can find context relevant to a question. Brain connects approved knowledge for compatible clients, keeping source evidence available for review.
An internal wiki can be well organized and still leave a teammate asking where the current answer lives. The wiki entry describes an older process, the approved document contains a later exception and a decision note explains why it changed. Brain is an internal knowledge workflow for that problem: consult approved team references, explain what supports the answer and let the reader return to the evidence.
Begin with documents the team already maintains rather than creating an article for every possible question. Connect an approved collection, preserve its owners and distinguish current guidance from an archive. A source-backed answer can locate the relevant passage across connected knowledge. It cannot resolve an unmarked conflict between two authoritative-looking policies without the responsible owner deciding which reference applies.
A maintained collection still needs care. Someone must update a changed policy, remove a superseded instruction or mark a historical decision clearly. Source processing and refresh behavior determine when a connected answer reflects that work. Test a known change in the pilot and inspect the resulting source rather than assuming an answer is current because the original file remains in a familiar shared folder.
The audience also matters. An internal team knowledge layer is different from a public customer help centre. Employees and scoped agents may need approved operating context, while customers need published support articles and an intentional delivery channel. Choose the collection and asker identities for the internal task, then test a restricted source before adding confidential information. Useful retrieval should not collapse every audience into one answerable archive.
Connect. Ask. Govern.
Choose the approved support guide, process pages and reference index. Name the owners and label historical material so the collection explains which document the team should use now.
Ask how to route a refund-review request or where a process step is recorded. Open the cited source and use the established owner for decisions or exceptions the reference does not settle.
Review employee and agent scope separately from a customer help centre. Test a private source with synthetic material and repeat a question after a known policy update to check the connected behavior.
See the idea in action
Fictional examples. These interactions do not query your Brain or test real permissions.
The fictional support reference says an annual-plan refund request goes to the billing reviewer with the account context and original invoice reference. It describes a routing process, not an automatic refund entitlement. Open the source and involve the responsible reviewer before acting. This example contains no real customer or payment details.
Route annual-plan refund requests to the billing reviewer with account context and the original invoice reference.
The fictional historical wiki v1 routes annual-plan refund requests to the support lead. The maintained operating guide v3 explicitly supersedes that route and assigns the billing reviewer, with the invoice reference. Open both passages to inspect the difference and stated authority. This is a routing example, not a refund entitlement; unresolved conflicts still go to the source owner.
Status: historical, superseded by operating guide v3. Old annual-plan refund route: support lead.
Current approved route, maintained by the operations owner: billing reviewer, with account context and original invoice reference. This replaces the annual-plan routing summary in wiki v1.
The fictional Notion page explains the supplier-review stages. A Drive checklist records which reference the reviewer should inspect at each stage. Together they clarify the procedure and evidence to gather. A cross-source answer should show those separate contributions, not treat either collection as authority for unrelated private records.
Process stages: intake, review and the responsible owner’s decision.
For each review stage, inspect the approved reference and record the responsible owner.
The fictional employee-case note sits outside the ordinary operating collection. Limited access withholds its answer and excerpt. A team handbook can be broadly useful without granting the same audience access to personal records. Test the intended boundary with synthetic sources in the actual workspace before importing sensitive employee material.
Private case note: individual circumstances and investigation discussion, restricted to its designated review group.
Open a question, then inspect its source excerpts.
Brain is a knowledge layer reached through MCP, the Model Context Protocol. Claude, Cursor and Codex are examples of compatible clients in the existing product. Client support and setup differ, so check the current connection instructions rather than assuming every assistant has the same capabilities.
The current public setup describes Google Drive and Notion as connected sources, alongside documents you choose to add. Start with a focused collection and inspect the actual connection screen for availability. A tool appearing in a roadmap or illustration does not mean its connector is ready for your account.
Connect the documents your workspace needs.
Bring approved pages into a shared knowledge layer.
Add a focused set of knowledge you own.
Keep access intentional
An internal knowledge base can serve several teams while respecting different source audiences. Decide which operating references belong in the ordinary collection and which cases require a narrower group. Review the actual connected identities and processing terms before adding sensitive material. Source evidence explains the process; it does not authorize a refund, employment action or other separate business decision.
Fictional metadata only. No document content is shown, and this is not a record from your account or proof of live enforcement.
An intake-process question may need the current clause and its exception, not every page of the company wiki. Compare the source-backed answer with the approved full reference and measure actual context usage. Retain necessary definitions and include retrieval, model outputs and Brain charges when evaluating cost; a maintained source collection is valuable only when the answer remains suitable for the work.
Compare current plans and limits| Approach | What to consider |
|---|---|
| An internal wiki | A useful place to structure and maintain guidance. Owners still need to keep it current and make the accepted reference clear. Brain can consult approved wiki knowledge without claiming that every existing wiki should be replaced. |
| Customer help-centre software | Designed for publishing support information to customers and managing that audience. Evaluate it for public support delivery. An internal knowledge workflow needs different collections, identities and confidential-source boundaries. |
| Search the shared drive | Helps locate files and inspect originals. It may leave the teammate responsible for comparing several passages or deciding which version applies. Clear names, owners and status remain useful whichever retrieval approach you choose. |
| Brain source-backed consultation | Lets compatible clients ask about approved connected references and inspect the supporting evidence. Keep the collection maintained and test source changes and access. It adds an internal question workflow rather than automatically publishing a customer portal. |
An AI knowledge base organizes information an assistant can consult for a specific question. Brain applies that idea to approved connected documents and source-backed answers through compatible clients. This page concerns internal team references. Source owners, current guidance and intended access still need to be maintained; retrieval alone does not make every document authoritative.
Knowledge base software can help publish and organize articles for employees or customers. An AI consultation layer helps a compatible client locate and explain relevant information from approved references. The approaches can work together. Choose based on your audience, maintenance responsibilities and access requirements rather than assuming every article system or AI tool serves the same purpose.
Start by connecting approved sources the team already maintains and testing a useful question. A complete rewrite into new articles may not be necessary, but connection can involve processing, indexing and storage. Review the source setup and privacy terms. Keep the original owners responsible for version status, accuracy and changes to the maintained references.
The source owner updates the reference, and the connection’s processing and refresh behavior determine when that change becomes available to an answer. Test a known update and inspect the source in your pilot. Mark superseded guidance clearly. This page does not promise instantaneous synchronization or that retrieval can resolve every conflict between poorly maintained documents.
Brain’s published source list includes Google Drive and Notion, so an approved collection can include references from both. Choose a process question supported by both references and check what each contributes. Verify readiness and access for the actual connections. A broader source list does not make every roadmap connector available or eliminate differences between source formats.
The intended answer depends on the asker’s identity, workspace and permitted source scope. Brain’s published model uses source-aware access for people and agents. Verify that behavior with an approved and restricted identity using synthetic documents, then repeat after an access change. An internal collection should not make private personnel or commercial records broadly answerable.
An internal team collection is not automatically a public customer help centre. Customer access needs an intentional product channel, approved published content and its own authorization decisions. This page does not promise a customer portal or public chatbot. Start with the internal task and keep private operating knowledge separate from information the organization has approved for external use.
Connect its approved references, ask a question your team can verify and inspect the evidence. Keep the original owner in charge of updates as the collection grows.
