Normalized for Mintlify from
knowledge-base/neurigraph-memory-architecture/legacy-brain-z-axis-spec.mdx.Brain Memory Architecture: Z-Axis Specification
Match Specificity Dimension
Product: Brain by aiConnectedVersion: 1.0
Date: January 20, 2026
Author: Bob / Claude
Status: Architecture Specification
Executive Summary
This specification introduces the Z-Axis (Match Specificity) as the third dimension of Brain’s memory retrieval architecture, complementing the existing X-Axis (Knowledge Graph) and Y-Axis (Vector Database). The Z-Axis represents a continuous spectrum from exact lexical matching to broad semantic similarity, enabling retrieval intent awareness—the ability to distinguish between “find that specific thing” and “help me think about this topic.” This architectural enhancement maps directly to how human memory actually works, differentiating between episodic recall (specific memories) and semantic recall (conceptual understanding), providing Brain with a significant competitive advantage over systems that collapse this distinction into a single similarity score.Current Architecture Review
X-Axis: Knowledge Graph Navigation
- Represents relational connections between concepts, entities, and contexts
- Enables traversal between related nodes (e.g., “aiConnected” → “Brain” → “Memory Architecture”)
- Provides structural organization of the user’s cognitive landscape
- Navigation is explicit and deterministic
Y-Axis: Vector Database (Per Node)
- Each Knowledge Graph node contains its own vector store
- Stores embeddings of conversations, documents, and insights within that node’s context
- Enables semantic similarity search within a specific domain
- Results ranked by cosine similarity to query embedding
Current Limitation
The Y-Axis retrieval returns results based solely on semantic similarity, without distinguishing between:- A user wanting the exact conversation where they mentioned “53% equity”
- A user wanting to explore their thinking about equity structures generally
Z-Axis: Match Specificity
Definition
The Z-Axis represents a continuous spectrum of match precision:Z-Value Interpretation
Technical Implementation
3.1 Dual-Score Retrieval
Every retrieval operation returns results with two independent scores:Lexical Precision Score (Z-Anchor)
Computed using BM25 or TF-IDF against the original query terms:Z-Position Calculation
3.2 Query Intent Detection
Before retrieval, the system analyzes the query to determine the target Z-range:3.3 Z-Aware Retrieval Pipeline
3.4 Tiered Retrieval Mode
For applications requiring explicit separation, Brain supports tiered retrieval:API Design
4.1 MCP Tool Definition
4.2 Response Schema
User Experience
5.1 Transparent vs. Hidden Operation
Default Mode: Hidden- Z-axis operates automatically via intent detection
- Users see only relevant results without technical details
- No additional cognitive load
- Optional UI control: “Match Precision” slider (Exact ↔ Broad)
- Results display Z-position indicator
- Tiered view available
5.2 Natural Language Z-Targeting
Users can implicitly control Z through natural phrasing:5.3 Result Presentation
For tiered mode, results can be presented with visual Z-indicators:Competitive Advantage
6.1 What Competitors Do
6.2 Brain’s 3D Advantage
Brain is the only system that provides:- Structural Navigation (X-Axis): “Show me memories about Brain, not aiConnected generally”
- Semantic Depth (Y-Axis): “Find relevant context within this domain”
- Retrieval Intent (Z-Axis): “I want the exact quote, not the general theme”
- X-Axis = Categorical organization (where in your mental filing cabinet)
- Y-Axis = Associative retrieval (what reminds you of what)
- Z-Axis = Episodic vs. semantic recall (specific memory vs. general knowledge)
6.3 Defensibility
The Z-Axis is:- Architecturally integrated (not a bolt-on feature)
- Patent-eligible (novel combination of retrieval strategies with intent detection)
- Hard to replicate (requires rethinking core retrieval infrastructure)
- Competitively invisible (users experience it as “it just works better”)
Implementation Roadmap
Phase 1: Foundation (Week 1-2)
- Implement BM25 lexical scoring alongside existing vector search
- Add
z_positioncalculation to retrieval results - Create query intent detection heuristics
- Unit tests for Z-scoring accuracy
Phase 2: Integration (Week 3-4)
- Modify retrieval pipeline to accept Z-targeting parameters
- Implement merged result ranking with Z-awareness
- Add tiered retrieval mode
- Integration tests across X/Y/Z dimensions
Phase 3: API & MCP (Week 5)
- Extend MCP tool schema with Z-axis parameters
- Implement response schema with scoring breakdown
- Documentation and examples
Phase 4: Refinement (Week 6)
- Tune intent detection patterns based on real queries
- A/B test Z-aware vs. Z-naive retrieval quality
- Performance optimization (caching, parallel retrieval)
Technical Considerations
7.1 Performance
Concern: Dual retrieval (lexical + semantic) doubles query time. Mitigation:- Parallel execution of BM25 and vector search
- Lexical index is extremely fast (inverted index)
- Cache query intent analysis for conversation context
- Precompute lexical precision during ingestion for common terms
7.2 Storage
Additional Requirements:- Inverted index for lexical search (BM25): ~10-20% overhead
- No additional per-memory storage (Z is computed at query time)
7.3 Index Updates
When new memories are ingested:- Generate and store embedding (existing)
- Update inverted index with tokenized content (new)
- Both indexes updated atomically
Success Metrics
Appendix A: Query Intent Patterns
Exact Match Indicators (Z → 0)
Broad Match Indicators (Z → 1)
Appendix B: Z-Axis Visualization
Document Control
This document is proprietary to aiConnected, LLC. The Z-Axis architecture represents a trade secret and competitive advantage.