What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	10017
title	Migration & Backward Compatibility for Multi-Tenant Schema
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-ada
createdAt	Apr 14, 2026, 6:43 PM
updatedAt	Apr 24, 2026, 12:06 AM
githubUrl	https://github.com/neomjs/neo/issues/10017
author	tobiu
commentsCount	1
parentIssue	10016
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 10000 Hardened Identity Ingestion & Tenant Isolation
blocking	[]
closedAt	Apr 24, 2026, 12:06 AM

Migration & Backward Compatibility for Multi-Tenant Schema

Closed v13.0.0/archive-v13-0-0-chunk-4 enhancementaiarchitecture

tobiu commented on Apr 14, 2026, 6:43 PM

Objective

Ensure existing single-tenant deployments can upgrade seamlessly to the multi-tenant schema without data loss or manual intervention.

Tasks

Create a migration script that backfills userId: 'default' on all existing ChromaDB metadata records (memories, sessions, summaries) that lack a userId field.
If #10011 is implemented, perform the equivalent ALTER TABLE migration for SQLite graph tables.
Ensure NEO_CHROMA_UNIFIED=true + single-user remains the zero-config default (no .env changes required for solo devs upgrading).
Document the migration path in a MIGRATION.md or the existing setup guide.

Acceptance Criteria

Existing solo deployments continue to function with zero configuration changes after upgrade
Migration script is idempotent (safe to run multiple times)
All existing memories remain queryable after migration

Parent Sub-Epic: Multi-Tenant Identity Origin Session ID: 69b726ca-97c8-406c-9106-c63b6642c4c0

tobiu added the enhancement label on Apr 14, 2026, 6:43 PM

tobiu added the ai label on Apr 14, 2026, 6:43 PM

tobiu added the architecture label on Apr 14, 2026, 6:43 PM

tobiu added parent issue #10016 on Apr 14, 2026, 6:44 PM

tobiu marked this issue as being blocked by #10000 on Apr 14, 2026, 6:44 PM

tobiu cross-referenced by PR #10130 on Apr 20, 2026, 5:26 PM

tobiu cross-referenced by #10016 on Apr 21, 2026, 4:28 PM