AMNI is built from a small set of recurring structural units:
Node (Graph Unit)
A compressed semantic object (sentence/paragraph/module/person/institution). It is a stable anchor in both graph and embedding space.
Edge (Relational Carrier)
A typed relationship (causal, contextual, inferential, hierarchical, transition). Edges are not pointers but semantic transformations between states.
Vector Space (Embedding Field)
A continuous similarity landscape enabling perceptual navigation and proximity-based discovery.
Narrative Path
A traversable sequence of nodes forming a readable or executable storyline through the graph.
Graph Expansion Operator
A mechanism that selectively reveals or grows local subgraphs based on relevance, uncertainty, or user intent.
LLM Generation Layer
A controlled inference system that fills missing nodes or edges, explicitly marked as inferred or probabilistic.
Gap Signal
A structural indicator of missing dependencies, weak connectivity, or underdeveloped conceptual regions.
Knowledge Loop
Every interaction acts simultaneously as query, update, training signal, and structural mutation event.
Context Injector (Modular Unit)
A runtime assembly mechanism that inserts prerequisite or missing knowledge directly into ongoing interaction flow.
Control-State Layer (Implicit across extracts)
Tracks system conditions, user exposure history, and graph evolution state over time.
HOW THE CONCEPT WORKS
AMNI operates as a four-layer coupled system:
1. Embedding Layer (Discovery Space)
- All knowledge is embedded in a continuous vector field
- Users begin with similarity-based “semantic proximity”
- Navigation is exploratory, not categorical
→ Function: find relevant regions of meaning
2. Graph Layer (Structural Reality)
- Embeddings are compressed into nodes
- Nodes are connected by typed edges
- The system continuously merges, splits, and refactors nodes
→ Function: define what meaning actually is structurally
3. Narrative Layer (Interpretation Engine)
- Graph paths are linearized into readable/executable narratives
- “Stories” are not outputs—they are views of structure
- Multiple narrative projections can exist over the same graph
→ Function: make structure cognitively accessible
4. Generative + Feedback Layer (Evolution Engine)
- LLMs detect gaps and generate missing structure
- User interaction modifies graph topology
- Every query reshapes future retrieval and organization
→ Function: ensure continuous evolution of the system
Interaction Cycle
- User issues query or takes action
- System maps intent into embedding space
- Local graph neighborhood is activated (focused view)
- Narrative projection is generated
- Gaps are detected and optionally filled (LLM expansion)
- Interaction is logged as structural update signal
- Graph + embeddings update
- Future queries are influenced by this new topology
This forms a self-perpetuating knowledge loop.