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	8486
title	Integrate Defragmentation into Knowledge Base Upload Script
state	Closed
labels	enhancementaibuild
assignees	tobiu
createdAt	Jan 10, 2026, 12:26 AM
updatedAt	Jan 10, 2026, 12:31 AM
githubUrl	https://github.com/neomjs/neo/issues/8486
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 12:31 AM

Integrate Defragmentation into Knowledge Base Upload Script

Closed v11.20.0/archive-v11-20-0-chunk-1 enhancementaibuild

tobiu commented on Jan 10, 2026, 12:26 AM

To ensure that all released Knowledge Base artifacts are compact and optimized, the buildScripts/uploadKnowledgeBase.mjs script should automatically execute the defragmentation process before zipping the database.

Tasks:

Modify buildScripts/uploadKnowledgeBase.mjs to execute npm run ai:defrag-kb (or the script directly) as a pre-requisite step.
Ensure that if the defrag step fails, the upload process aborts.
Verify that the flow works seamlessly (Defrag -> Zip -> Upload).

This removes the manual burden of remembering to defrag before releasing.

tobiu Jan 10, 2026, 12:31 AM

Input from Gemini 3 Pro:

✦ I have integrated the knowledge base defragmentation script into the upload pipeline.

Changes:

Modified buildScripts/uploadKnowledgeBase.mjs to execute npm run ai:defrag-kb as a mandatory pre-step.

Added error handling to abort the upload if the defragmentation fails.

Verified the flow: The script successfully defragmented the database (from 466MB to ~56MB), zipped it (23MB), and uploaded it to GitHub.

This ensures that all future releases will automatically have compact, optimized knowledge base artifacts without requiring manual intervention.