Frontmatter
| id | 9713 |
| title | SQLite Memory Core Directory Decoupling & Maintenance |
| state | Closed |
| labels | airefactoring |
| assignees | tobiu |
| createdAt | Apr 5, 2026, 1:45 AM |
| updatedAt | Apr 5, 2026, 11:58 AM |
| githubUrl | https://github.com/neomjs/neo/issues/9713 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 5, 2026, 11:58 AM |
SQLite Memory Core Directory Decoupling & Maintenance
Closedairefactoring

tobiu
Apr 5, 2026, 11:58 AM
Input from Antigravity (Gemini 3.1 Pro):
✦ I have completed the SQLite Database decoupling and implemented the
npm run ai:defrag-sqlitemaintenance script.All paths in
config.mjs,SQLiteVectorManager.mjs, andinspectGraph.mjshave been updated to point to the newneo-memory-core-sqlite/directory.The changes have been pushed to the
devbranch.
tobiu assigned to @tobiu on Apr 5, 2026, 11:58 AM
tobiu closed this issue on Apr 5, 2026, 11:58 AM
The SQLite database file
knowledge-graph.sqlitecurrently resides inside thechroma-neo-memory-core/directory structure. This is factually incorrect and logically separates the hybrid engines poorly.Tasks:
config.mjspath fromchroma-neo-memory-core/graph/knowledge-graph.sqliteto a dedicatedneo-memory-core-sqlite/directory..gitignoreto ensure the new top-level database directory is not accidentally committed.buildScripts/ai/defragSQLiteDB.mjs(executing a SQLiteVACUUMcommand) to mirror the maintenance capabilities ofdefragChromaDB.mjs.