B.R.A.I.N. in one picture

These visuals describe the accepted Phase 6 system. They make ownership and lifecycle explicit: B.R.A.I.N. holds durable cognitive state; providers supply bounded, replaceable capability. On a narrow screen, select any diagram to open its full-size SVG in a new tab.

​

System context

Open full-size diagram: System context: B.R.A.I.N. is the persistent system and Gemini is a replaceable provider. B.R.A.I.N. persists memory, knowledge, beliefs, and evidence. It can use Gemini for reasoning, Live interaction, and embeddings without placing canonical state inside the provider.

​

Ownership boundary

Open full-size diagram: B.R.A.I.N. versus Gemini ownership comparison. Gemini’s pretrained general knowledge can inform a response, but it does not automatically become B.R.A.I.N. knowledge. An accepted teaching or source-backed record is required for durable cognitive state.

​

Teaching, recall, and correction

Open full-size diagram: Owner teaching, fresh-session recall, and correction lineage. A correction creates a successor. The current record is retrieved for ordinary use; the superseded record remains available with its provenance and lineage.

​

Document knowledge

Open full-size diagram: Document ingestion from original artifact to grounded citation. Original and normalized artifacts are canonical and portable. Chunks and model-tagged embeddings are derived and can be rebuilt from those retained sources.

​

Private deployment boundary

Open full-size diagram: Private Hostinger deployment through NetBird with loopback API and internal PostgreSQL. The current deployment has no public application ingress. The UI/API bind to loopback, PostgreSQL remains inside the Compose network, and provider secrets remain server-side.

​

Reading the visual language

Open full-size diagram: Visual style reference for current, future, canonical, derived, provenance, and superseded elements. See the visual system reference for the reusable component and arrow conventions.

​

Future, not current

Phase 7 daily-use qualification is in progress; its required three-day genuine-use window is not complete. Future sensors, home embodiment, dedicated-server migration, optional GPU work, local models, and training remain explicitly deferred. For the guided sequence, see the visual atlas.