The Brain: context with a trail back
The Brain is the connective layer in this architecture. It helps an agent find relevant context across workspaces and return a compact set of references, instead of treating a conversation as the whole record. It is a retrieval system built around a graph, not a claim of consciousness or infallible memory. See the system map for the surrounding workspaces.
Anatomy: the sources and their index
Scroll diagram to explore.
The inspected source includes extractors that turn documents into records with titles, paths, summaries, timestamps and content hashes, and can derive typed relationships from metadata and links. A graph builder admits and indexes records; its SQLite schema includes nodes, edges, aliases, a full-text index, and storage for embeddings. An index is a derived view of sources, not the source itself.
Physiology: a question becomes context
Scroll diagram to explore.
The retrieval path reads the index built above. For a question, the retrieval code can combine exact identifiers, aliases, titles, full-text search and a vector channel, then expand selected graph relationships and assemble a context pack within a budget. Which channels contribute depends on configuration and availability. Scope and coverage are part of the result: an empty or narrow result does not prove that no relevant information exists.
The output helps someone decide where to look next. A source pointer, a relationship, or a relevance score does not authenticate a claim. Important decisions still call for checking the current owning source, its context and any conflicting evidence.
Recall and change are different paths
Reading context should not silently turn a suggestion into accepted knowledge. The inspected MCP interface includes proposal paths for nodes and relationships: it checks proposal fields, applies a secret-pattern scan to relevant text, and stages proposals for review. The broader system also has write-validation and risk-check interfaces. These are separate mechanisms; their presence does not establish universal coverage, automatic approval, or that every caller invokes them.
Scroll diagram to explore.
What has been checked
This is a source-grounded tour of a private working system, not a release of the Brain or proof of every integration. A prior isolated check exercised seven invented lookup cases against a copied resolver with local dependencies stubbed. It did not test indexing, graph expansion, policy enforcement or the running service. The diagrams describe intended relationships between the inspected components; actual freshness, permissions and results require separate checks in the environment where they run.
Explore and contribute
Arcturion Memory is a separate public project for auditing, indexing and searching document-based agent memory. Arcturion Evals offers synthetic tasks for examining agent behavior over time. Neither is the private Brain; each has its own setup, scope and issues for questions or contributions.