[Mnemosyne] Spatial Memory Schema — holographic coordinate system for memory in the Nexus #1152

New Issue

Rockachopa · 2026-04-10T04:43:28Z

Rockachopa commented

2026-04-10 04:43:28 +00:00

Context

Project Mnemosyne transforms the Nexus 3D world into a real-time visual representation of the AI's holographic memory. The memory orbs system (spawnMemoryOrb, spawnRetrievalOrbs) exists but memories spawn in arbitrary positions. We need a Spatial Memory Schema — a coordinate system that maps memory categories to persistent world regions.

Requirements

Define memory zones — map memory categories to Nexus regions:
- conversations → Workshop area (near the chat/workshop terminals)
- skills/procedures → Archive region
- facts/environment → Central hub
- corrections/preferences → Player's home base
- sessions/transient → Outer ring (fades quickly)
Spatial Memory Schema class — SpatialMemorySchema in app.js:
- registerZone(name, center, radius, color, metadata)
- assignMemory(memoryObj) → zone — route a memory to its zone based on type
- getZonePosition(type) → THREE.Vector3 — get spawn position within zone
- listZones() — debug/visualization
Integration with spawnMemoryOrb — when spawning orbs, use the schema to place them in their correct zone instead of spiral patterns
Zone visualization — subtle ground rings/particles at each zone boundary so players can see memory "neighborhoods"
Persistence — save zone assignments to localStorage so the spatial layout survives page reloads

Acceptance Criteria

SpatialMemorySchema class defined and instantiated in app.js
Memory orbs spawn in their assigned zone
Zone boundaries visible as subtle ground markers
Zone assignments persist across page reloads
Existing spawnRetrievalOrbs uses schema for positioning
No regression in existing portal/vision/agent systems

## Context Project Mnemosyne transforms the Nexus 3D world into a real-time visual representation of the AI's holographic memory. The memory orbs system (`spawnMemoryOrb`, `spawnRetrievalOrbs`) exists but memories spawn in arbitrary positions. We need a **Spatial Memory Schema** — a coordinate system that maps memory categories to persistent world regions. ## Requirements 1. **Define memory zones** — map memory categories to Nexus regions: - `conversations` → Workshop area (near the chat/workshop terminals) - `skills/procedures` → Archive region - `facts/environment` → Central hub - `corrections/preferences` → Player's home base - `sessions/transient` → Outer ring (fades quickly) 2. **Spatial Memory Schema class** — `SpatialMemorySchema` in app.js: - `registerZone(name, center, radius, color, metadata)` - `assignMemory(memoryObj) → zone` — route a memory to its zone based on type - `getZonePosition(type) → THREE.Vector3` — get spawn position within zone - `listZones()` — debug/visualization 3. **Integration with spawnMemoryOrb** — when spawning orbs, use the schema to place them in their correct zone instead of spiral patterns 4. **Zone visualization** — subtle ground rings/particles at each zone boundary so players can see memory "neighborhoods" 5. **Persistence** — save zone assignments to localStorage so the spatial layout survives page reloads ## Acceptance Criteria - [ ] `SpatialMemorySchema` class defined and instantiated in app.js - [ ] Memory orbs spawn in their assigned zone - [ ] Zone boundaries visible as subtle ground markers - [ ] Zone assignments persist across page reloads - [ ] Existing `spawnRetrievalOrbs` uses schema for positioning - [ ] No regression in existing portal/vision/agent systems

Rockachopa commented

2026-04-10 04:43:39 +00:00

Claiming this issue — implementing the Spatial Memory Schema for Project Mnemosyne.

Rockachopa self-assigned this 2026-04-10 04:43:40 +00:00

ezra was assigned by Timmy

2026-04-10 04:45:12 +00:00

Rockachopa referenced this issue from a commit

2026-04-10 04:45:33 +00:00

feat(mnemosyne): add Spatial Memory Schema

Rockachopa referenced this issue

2026-04-10 04:45:53 +00:00

[Mnemosyne] Spatial Memory Schema — holographic coordinate system #1153

Rockachopa commented

2026-04-10 04:46:06 +00:00

Implementation complete — see PR #1153 for the Spatial Memory Schema.

The Nexus now has 6 memory zones with ground ring visualization, and memory orbs route to their assigned zone based on type.

Implementation complete — see PR #1153 for the Spatial Memory Schema. The Nexus now has 6 memory zones with ground ring visualization, and memory orbs route to their assigned zone based on type.

Rockachopa closed this issue

2026-04-10 04:46:06 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#1152