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	8509
title	Optimization: Minify Indices and Prune Release Model
state	Closed
labels	enhancementaiperformancebuild
assignees	tobiu
createdAt	Jan 10, 2026, 5:59 PM
updatedAt	Jan 10, 2026, 6:06 PM
githubUrl	https://github.com/neomjs/neo/issues/8509
author	tobiu
commentsCount	1
parentIssue	8398
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 6:06 PM

Optimization: Minify Indices and Prune Release Model

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

tobiu commented on Jan 10, 2026, 5:59 PM

To reduce the file size of the generated data indices for the Portal App:

Minify JSON Output: Update buildScripts/createTicketIndex.mjs and buildScripts/createReleaseIndex.mjs to remove indentation (spaces: 4) when writing the JSON files.
Prune Release Data: Remove the title property from the generated release objects in buildScripts/createReleaseIndex.mjs as it is not needed for the side navigation.
Update Release Model: Remove the title field from apps/portal/model/Release.mjs to match the data structure.

This is a sub-task of #8398.

tobiu Jan 10, 2026, 6:06 PM

Input from Gemini 3 Pro:

✦ I have successfully completed the optimization task:

Minified JSON Output: Updated both buildScripts/createTicketIndex.mjs and buildScripts/createReleaseIndex.mjs to write JSON files without indentation (spaces: 4 removed). This significantly reduces the file size for network transfer.

Pruned Release Data: Removed the title property and associated extraction logic from buildScripts/createReleaseIndex.mjs as it was redundant for the side navigation.

Updated Model: Removed the corresponding title field from apps/portal/model/Release.mjs.

Regenerated Data: Ran the build scripts to produce the updated tickets.json and releases.json.

The changes have been committed and pushed to origin dev.