[Feature] Unified Persistent Memory & Spatial Agentic Loop Visualization #69
Reference in New Issue
Block a user
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?
Executive Summary
The current architecture of the Timmy ecosystem features two sophisticated but disconnected environments: the Timmy Tower (3D Workshop), which serves as the primary production interface, and the Timmy Dashboard (Mission Control), which houses the advanced autonomous reasoning and memory subsystems. While the Dashboard possesses a robust multi-step Agentic Loop for planning and execution, as well as a Persistent Memory system for long-term data retention, the Tower experience remains largely stateless and reactive.
The highest leverage improvement identified for the project is the integration of these two systems. By bridging the reasoning and memory layers of the Dashboard with the spatial visualization of the Tower, we can transform the 3D environment into a tangible, persistent workspace for a sovereign AI worker. This integration directly addresses user retention, trust through transparency, and the overall value proposition of the sovereign AI economy.
Strategic Impact and Value
replit/timmy-towerandrockachopa/Timmy-time-dashboardcodebases, creating a single, coherent product suite rather than a collection of experimental silos.Technical Implementation Framework
Persistent Memory Integration
The integration of persistent memory requires a synchronization layer between the Tower's identity service and the Dashboard's memory subsystem. When a user initiates a session in the Tower, the system must authenticate their Nostr pubkey and retrieve relevant "Semantic Memory" fragments from the backend. These fragments are then injected into the agent's current context, allowing for a "Welcome back" experience that references specific past projects or preferences.
At the interface level, the 3D scene should be enhanced to display "Memory Fragments" as floating holographic elements. These visual cues appear when the agent performs a retrieval operation, signaling to the user that the AI is actively drawing upon their shared history.
Spatial Agentic Loop Visualization
The Agentic Loop—comprising planning, execution, and adaptation phases—should be mapped to physical "Action Zones" within the 3D Tower. By subscribing to
agentic.*WebSocket events emitted by the backend, the 3D frontend can trigger movement and state changes for the Timmy avatar.Cross-Project Connectivity
To achieve this, the
artifacts/api-server/src/routes/sessions.tsin the Tower repository must be updated to invoke therun_agentic_loop()function from the Dashboard backend upon receiving complex user requests. Furthermore, the WebSocket bridge inthe-matrix/js/websocket.jsmust be extended to parse and broadcast theagenticevent payload to the 3D scene controller.Success Criteria and Roadmap
The successful implementation of this feature will be measured by the following milestones:
This integration represents the transition from a "chatbot in a box" to a Sovereign AI Employee that lives and works within a persistent, observable world.