Timmy_Foundation/the-nexus
15
1
Fork 2
Code Issues 108 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

[Mnemosyne] Implement Spatial Memory Schema JSON #1149

New Issue
Closed
opened 2026-04-10 03:09:05 +00:00 by Rockachopa · 2 comments
Rockachopa commented 2026-04-10 03:09:05 +00:00
Owner
Copy Link

Overview

Create the spatial-memory-schema.json file that maps memory categories to Nexus spatial zones, as described in DESIGN.md.

Requirements

  1. Room Mapping: Map memory categories (user_pref, project, conversation, skill, fact, etc.) to specific Nexus rooms
  2. Visual Themes: Define visual properties for each room (lighting, colors, particle effects)
  3. Spatial Coordinates: Define 3D positions for memory orbs within each room
  4. Connection Paths: Define how memory orbs connect across rooms (holographic threads)
  5. RAG Integration: Schema must support the RAG retrieval system for memory orb placement

Implementation Details

  • File: spatial-memory-schema.json in the-nexus root
  • Format: JSON with categories, rooms, coordinates, and visual properties
  • Must be compatible with the existing memory orb system in app.js
  • Should follow the DESIGN.md specifications

Priority

This is the foundation for all Mnemosyne spatial memory features. Must be implemented before other spatial features.

Acceptance Criteria

  • spatial-memory-schema.json exists in the-nexus root
  • All memory categories from DESIGN.md are mapped
  • Visual themes are defined with Three.js compatible values
  • Spatial coordinates are valid 3D positions
  • Schema is referenced by the memory orb system
## Overview Create the `spatial-memory-schema.json` file that maps memory categories to Nexus spatial zones, as described in DESIGN.md. ## Requirements 1. **Room Mapping**: Map memory categories (`user_pref`, `project`, `conversation`, `skill`, `fact`, etc.) to specific Nexus rooms 2. **Visual Themes**: Define visual properties for each room (lighting, colors, particle effects) 3. **Spatial Coordinates**: Define 3D positions for memory orbs within each room 4. **Connection Paths**: Define how memory orbs connect across rooms (holographic threads) 5. **RAG Integration**: Schema must support the RAG retrieval system for memory orb placement ## Implementation Details - File: `spatial-memory-schema.json` in the-nexus root - Format: JSON with categories, rooms, coordinates, and visual properties - Must be compatible with the existing memory orb system in `app.js` - Should follow the DESIGN.md specifications ## Priority This is the foundation for all Mnemosyne spatial memory features. Must be implemented before other spatial features. ## Acceptance Criteria - [ ] `spatial-memory-schema.json` exists in the-nexus root - [ ] All memory categories from DESIGN.md are mapped - [ ] Visual themes are defined with Three.js compatible values - [ ] Spatial coordinates are valid 3D positions - [ ] Schema is referenced by the memory orb system
Timmy was assigned by Rockachopa 2026-04-10 03:09:06 +00:00
Rockachopa commented 2026-04-10 03:09:18 +00:00
Author
Owner
Copy Link

Claiming this issue. I'll implement the spatial memory schema based on the DESIGN.md specifications.

Claiming this issue. I'll implement the spatial memory schema based on the DESIGN.md specifications.
Rockachopa commented 2026-04-10 03:11:46 +00:00
Author
Owner
Copy Link

PR submitted: #1150

The spatial memory schema has been implemented with:

  • 4 memory rooms (Library, Workshop, Armory, Commons)
  • 8 object types with visual properties
  • Lifecycle event animations
  • Holographic thread connections
  • RAG integration visualization parameters

Ready for review and integration with the memory orb system.

PR submitted: #1150 The spatial memory schema has been implemented with: - 4 memory rooms (Library, Workshop, Armory, Commons) - 8 object types with visual properties - Lifecycle event animations - Holographic thread connections - RAG integration visualization parameters Ready for review and integration with the memory orb system.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
3d-world
CI
Continuous integration, runners, workflow issues
 QA
Quality assurance, testing, and production audit
 actionable
agent-presence
aistudio-ready
assigned-aistudio
assigned-claude
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-gemini
assigned-groq
assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-kimi
assigned-perplexity
assigned-sonnet
blocked
Blocked by external dependency or merge conflict
 claude-ready
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 deprioritized
duplicate
epic
Epic / umbrella issue
 gemini-api
Gemini API integration
 gemini-review
google-ai-ultra
Google AI Ultra integration work
 groq-ready
harness
identity
Timmy identity and branding
 infrastructure
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 kimi-ready
lazzyPit
Lazarus Pit — automated agent resurrection and health recovery
 media-gen
AI media generation (image/video/audio)
 mnemosyne
Project Mnemosyne — The Living Holographic Archive
 modularization
needs-design
nostr
p0-critical
p1-important
p2-backlog
performance
perplexity-ready
portal
research
Deep research and planning tasks
 security
Security hardening, vulnerability fixes, access control
 sonnet-ready
sovereignty
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok hermes kimi manus perplexity sonnet
No Assignees Timmy
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#1149
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?