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	12217
title	Refactor tickets index emitter → chunked-by-folder + path de-duplication
state	Closed
labels	enhancementaiperformancebuild
assignees	neo-gpt
createdAt	May 30, 2026, 7:27 PM
updatedAt	May 31, 2026, 10:51 PM
githubUrl	https://github.com/neomjs/neo/issues/12217
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 12220 Correct tickets.mjs module JSDoc to the chunked-index reality, [x] 12218 Opt-in load-on-folder-expand for the shared portal TreeList
closedAt	May 31, 2026, 10:51 PM

Refactor tickets index emitter → chunked-by-folder + path de-duplication

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaiperformancebuild

neo-opus-ada commented on May 30, 2026, 7:27 PM

Context

Part of epic #12207 (Track B; realizes #11372 Phase 2). apps/portal/resources/data/tickets.json is ~1.5 MB / ~8,772 rows eager-loaded (autoLoad:true); measured path = 34 % of the file and is redundant (duplicates id + version). No body is inlined (already lazy).

The Fix

Change buildScripts/docs/index/tickets.mjs to emit (i) a small ROOT group-index and (ii) one per-chunk leaf file under apps/portal/resources/data/tickets/<chunk>.json, mirroring the on-disk chunk-N/ folders — the chunk IS the lazy unit. De-duplicate path (drop + reconstruct from parentId+id+chunk, or shared-prefix+tail). Add a crawler manifest so SEO ingestion still discovers all groups. Use the same chunked shape as the pulls/discussions generators (sub 6) — decide it once. Fold the JSDoc correction (sub 15) in here.

Acceptance Criteria

tickets index emitted as root group-index + per-chunk leaf files; path de-duplicated; crawler manifest added.
Leaf shape identical to pulls/discussions output.

Epic #12207; #11372 Phase 2. Unblocks the lazy folder-load (sub 13). Subsumes sub 15.

tobiu closed this issue on May 31, 2026, 10:51 PM

tobiu referenced in commit 3315515 - "feat(portal): emit chunked ticket indexes (#12217) (#12271) on May 31, 2026, 10:51 PM

Refactor tickets index emitter → chunked-by-folder + path de-duplication

Context

The Fix

Acceptance Criteria

Related