[Mnemosyne] Spatial Memory Schema — persistent memory locations in 3D world #1154

Closed
opened 2026-04-10 05:40:19 +00:00 by Rockachopa · 2 comments
Owner

Goal

Define and implement a Spatial Memory Schema that maps memories to persistent locations in the 3D Nexus world. Currently, memory orbs are temporary (30s fade). This schema gives memories permanent spatial homes organized by semantic category.

Requirements

1. Memory Region Map

Define named zones in the Nexus world, each corresponding to a semantic category:

  • Code & Engineering — East quadrant
  • Conversations & Social — West quadrant
  • Documents & Knowledge — North quadrant
  • Projects & Tasks — South quadrant
  • Archive (cold storage) — Underground/below

2. Schema Structure

{
  "regions": {
    "engineering": {
      "center": [10, 2, 0],
      "radius": 8,
      "color": 0x4af0c0,
      "icon": "code",
      "memories": []
    }
  },
  "memory": {
    "id": "mem_<hash>",
    "content": "...",
    "category": "engineering",
    "position": [x, y, z],
    "source": "session|mem_palace|manual",
    "timestamp": "ISO8601",
    "strength": 0.0-1.0,
    "connections": ["mem_<other_id>"]
  }
}

3. Persistence

  • Memory positions persist across sessions (stored in ~/.hermes/mnemosyne/spatial_index.json)
  • On Nexus load, existing memories are restored at their saved positions
  • New memories are assigned positions within their category region

4. Visual Indicators

  • Each region has a subtle ground marker (colored ring/particle field)
  • Persistent memories use a different visual style than temporary orbs (e.g., crystal instead of sphere)
  • Memory strength affects opacity/glow intensity

Priority

This is the foundation — all other Mnemosyne features depend on having memories in fixed, meaningful locations.

Target Files

  • app.js — new spatial memory system section
  • nexus/components/spatial-memory.js — schema and region definitions
## Goal Define and implement a **Spatial Memory Schema** that maps memories to persistent locations in the 3D Nexus world. Currently, memory orbs are temporary (30s fade). This schema gives memories permanent spatial homes organized by semantic category. ## Requirements ### 1. Memory Region Map Define named zones in the Nexus world, each corresponding to a semantic category: - **Code & Engineering** — East quadrant - **Conversations & Social** — West quadrant - **Documents & Knowledge** — North quadrant - **Projects & Tasks** — South quadrant - **Archive (cold storage)** — Underground/below ### 2. Schema Structure ```json { "regions": { "engineering": { "center": [10, 2, 0], "radius": 8, "color": 0x4af0c0, "icon": "code", "memories": [] } }, "memory": { "id": "mem_<hash>", "content": "...", "category": "engineering", "position": [x, y, z], "source": "session|mem_palace|manual", "timestamp": "ISO8601", "strength": 0.0-1.0, "connections": ["mem_<other_id>"] } } ``` ### 3. Persistence - Memory positions persist across sessions (stored in `~/.hermes/mnemosyne/spatial_index.json`) - On Nexus load, existing memories are restored at their saved positions - New memories are assigned positions within their category region ### 4. Visual Indicators - Each region has a subtle ground marker (colored ring/particle field) - Persistent memories use a different visual style than temporary orbs (e.g., crystal instead of sphere) - Memory strength affects opacity/glow intensity ## Priority This is the foundation — all other Mnemosyne features depend on having memories in fixed, meaningful locations. ## Target Files - `app.js` — new spatial memory system section - `nexus/components/spatial-memory.js` — schema and region definitions
Author
Owner

Claiming this issue

Claiming this issue
Rockachopa self-assigned this 2026-04-10 05:40:32 +00:00
Author
Owner

Implemented in PR #1155 — Spatial Memory Schema with 5 semantic regions, crystal geometry, deterministic placement, and connection lines.

Implemented in PR #1155 — Spatial Memory Schema with 5 semantic regions, crystal geometry, deterministic placement, and connection lines.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#1154