Agent Memory Architecture and Knowledge Boundaries
In Nimi's cognitive framework, long-term memory lifecycle and synthesis are governed by Cognition. Local Runtime manages LocalAgent operational identities, conversation turn staging, and acts as the secure mediation broker between agent sessions and memory stores.
Memory Isolation and Ownership Principles
- Independent Memory Banks: Each LocalAgent maintains a dedicated, isolated Memory Bank. Distinct instances spawned from the same base Character maintain separate experiential memories.
- World Invariance: The authoritative history and lore of a digital world are anchored in Realm; an agent's personal memory cannot unilaterally mutate shared world lore or global states.
- Session-Scoped Access: All read/write operations targeting memory pass through Runtime's authorization gates. Client applications interact via structured SDK APIs, prevented by design from cross-tenant snooping.
Context Assembly and Recall Mechanics
When a user initiates a conversation turn, the system stages context through clear phases:
- Context Capture: Runtime extracts recent turn history and active conversation anchors.
- Semantic Recall: Runtime requests relevant memories from Cognition matching the user's intent.
- Resilient Degradation: Memory recall functions as an enhancement. Pending, unavailable and no-match outcomes remain distinct. Runtime uses zero optional memory hits when recall cannot contribute and continues from the other admitted context; it does not report a failed read as a successful empty result.
- Memory Consolidation: As meaningful interactions conclude, Cognition evaluates conversation milestones and commits consolidated memories in the background.
Memory Lifecycle Controls
- Per-Agent Memory Toggle: Each LocalAgent has an independent memory switch. Disabling it halts new ingestion and recall while safely preserving stored historical memories.
- Memory Deletion: Users can clear an agent's memory bank at any time; this removes all stored memories from recall while leaving raw conversation history and base character persona intact.
- Account Deletion Cleanup: Upon an observed typed Realm
ACCOUNT_DELETEDresult, associated local memory stores for that account namespace are cleaned up locally on the current device.